Skip to content

fix(deps): pin @typespec/openapi to 1.16.0 [NOTASK] - #1173

Merged
pditommaso merged 1 commit into
masterfrom
fix-typespec-openapi-pin
Oct 12, 2026
Merged

pditommaso merged 1 commit into
masterfrom
fix-typespec-openapi-pin

Conversation

@pditommaso

Copy link
Copy Markdown
Collaborator

Every build.yml run has failed at :installTypeSpec since 2026-10-08.

There is no package-lock.json, so npm resolves the @typespec/openapi peer of @typespec/openapi3@1.16.0 (^1.16.0) to the newest release. @typespec/openapi@1.17.0, published 2026-10-08, requires @typespec/compiler ^1.17.0. That conflicts with the pinned 1.16.0, and npm aborts with ERESOLVE.

This PR cherry-picks the fix from #1165 (756eb3c, by @cristianrcv), which pins @typespec/openapi to 1.16.0, so master is unblocked without waiting for that feature PR.

npm still prints a non-fatal ERESOLVE overriding peer dependency warning: @typespec/asset-emitter@0.79.3 (transitive via openapi3) asks for compiler ^1.17.0. A follow-up can move all @typespec/* packages to 1.17.0 and/or commit a lockfile with npm ci.

Verified locally: a clean npm install and tsp compile succeed.

🤖 Generated with Claude Code

There is no lockfile, so npm resolved the @typespec/openapi peer of
@typespec/openapi3 to 1.17.0, which requires @typespec/compiler ^1.17.0
and conflicts with the pinned 1.16.0. installTypeSpec failed on every
build. Pinning the peer to the same release as the rest of the
toolchain restores the install.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@pditommaso
pditommaso merged commit f6254fe into master Oct 12, 2026
5 checks passed
@pditommaso
pditommaso deleted the fix-typespec-openapi-pin branch October 12, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants