Summary
The latest CI run for the open TypeScript 6 Dependabot PR fails during npm ci because openapi-typescript@7.13.0 still declares a typescript@^5.x peer dependency.
Why this is useful
Keeping dependency update PRs either green or intentionally deferred makes it easier to merge routine security and maintenance updates without guessing whether a red CI run is expected.
Proposed small change
- Decide whether to hold TypeScript on the latest 5.x line until
openapi-typescript supports TypeScript 6, or update the generator dependency if a compatible release is available.
- Add a short note in the PR or dependency policy so future TypeScript-major bumps are handled consistently.
Evidence checked
Validation gate
Stitch should not work on this until Adrien explicitly approves this issue or asks Stitch to implement it.
Suggested acceptance check
- The affected dependency update PR is either closed/deferred with a clear reason or has a green
npm ci/CI run after updating compatible dependencies.
Summary
The latest CI run for the open TypeScript 6 Dependabot PR fails during
npm cibecauseopenapi-typescript@7.13.0still declares atypescript@^5.xpeer dependency.Why this is useful
Keeping dependency update PRs either green or intentionally deferred makes it easier to merge routine security and maintenance updates without guessing whether a red CI run is expected.
Proposed small change
openapi-typescriptsupports TypeScript 6, or update the generator dependency if a compatible release is available.Evidence checked
27480370901for PR chore(deps-dev): bump typescript from 5.9.3 to 6.0.3 #5 failed in theInstall dependenciesstep with an npm peer dependency conflict between TypeScript 6.0.3 andopenapi-typescript@7.13.0.Validation gate
Stitch should not work on this until Adrien explicitly approves this issue or asks Stitch to implement it.
Suggested acceptance check
npm ci/CI run after updating compatible dependencies.