Type generation broken

[wolfy1339]

Due to the update of openapi-typescript in #100, the type generation broke

To remedy this, I propose we dry-run the type generation process whenever there's an update to openapi-typescript

See the logs:

file:///home/runner/work/octokit-next.js/octokit-next.js/node_modules/openapi-typescript/dist/load.js:141
    walk(options.schemas[schemaID].schema, (rawNode, nodePath) => {
                                   ^

TypeError: Cannot read properties of undefined (reading 'schema')
    at load (file:///home/runner/work/octokit-next.js/octokit-next.js/node_modules/openapi-typescript/dist/load.js:141:36)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)
    at async load (file:///home/runner/work/octokit-next.js/octokit-next.js/node_modules/openapi-typescript/dist/load.js:187:5)
    at async openapiTS (file:///home/runner/work/octokit-next.js/octokit-next.js/node_modules/openapi-typescript/dist/index.js:37:5)
    at async run (file:///home/runner/work/octokit-next.js/octokit-next.js/scripts/types-openapi/update.js:91:7)

https://github.com/octokit/octokit-next.js/actions/runs/3430908885/jobs/5718425041

[wolfy1339]

There seems to be other users that are having the same issue.
openapi-ts/openapi-typescript#975

[wolfy1339]

It seems that the OpenAPI Update workflow should already cover this, as it is triggered by renovate branches.

The workflow was skipped: https://github.com/octokit/octokit-next.js/actions/runs/3425540945

There really should be a better way to make sure this doesn't happen again.

[kfcampbell]

Oh no! I'm sorry, what a hassle.

• Should we revert chore(deps): update dependency openapi-typescript to v6 #100?
• I wonder if the build was skipped because of this line in the workflow. Perhaps we should consider broadening those conditions?

[wolfy1339]

No worries, it happens to the best of us 😆

• It seems wise to revert chore(deps): update dependency openapi-typescript to v6 #100 in the meantime
• From what I can work out, those conditions shouldn't be necessary.

On another note, the labels seem out of date in the workflow

[wolfy1339]

This will be fixed in openapi-ts/openapi-typescript#977

[wolfy1339]

I've run into another issue, it doesn't seem to respect "nullable": true anymore

[wolfy1339]

The previous issue, was fixed. openapi-ts/openapi-typescript#983
Current blocker: openapi-ts/openapi-typescript#984

[github-actions]

🎉 This issue has been resolved in version 2.7.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀