Skip to content

Pin @types/vscode to match engines.vscode (fix VSIX packaging)#58

Merged
MelbourneDeveloper merged 1 commit into
mainfrom
tdbin
Jul 12, 2026
Merged

Pin @types/vscode to match engines.vscode (fix VSIX packaging)#58
MelbourneDeveloper merged 1 commit into
mainfrom
tdbin

Conversation

@MelbourneDeveloper

Copy link
Copy Markdown
Collaborator

Summary

The v0.12.0 Release passed the CodeQL gate and published typediagram-core@0.12.0 and typediagram@0.12.0 to npm, but the Package VSIX step failed:

@types/vscode ^1.125.0 greater than engines.vscode ^1.99.0

@types/vscode was bumped to ^1.125.0 (dependency update) while engines.vscode stayed ^1.99.0; vsce package rejects that mismatch. The extension only uses the 1.99-era API, so this pins @types/vscode back to ^1.99.0 — matching the engine floor and restoring the v0.11.0 config that packaged cleanly.

Verified locally: vscode typecheck passes and vsce package succeeds (18 files, ~1 MB VSIX).

npm publishes are idempotent (already live); after merge I'll re-point v0.12.0 and the re-run completes VSIX + Marketplace + GitHub Release.

🤖 Generated with Claude Code

vsce package rejects a release when @types/vscode (^1.125.0, bumped by a
dependency update) is newer than engines.vscode (^1.99.0). The extension only
uses the 1.99-era API, so pin @types/vscode back to ^1.99.0 to match the
declared engine floor — restoring the v0.11.0 configuration that packaged
cleanly. Verified: vscode typecheck passes and `vsce package` succeeds.
@MelbourneDeveloper
MelbourneDeveloper merged commit 3568adc into main Jul 12, 2026
6 checks passed
@MelbourneDeveloper
MelbourneDeveloper deleted the tdbin branch July 12, 2026 02:27
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.

1 participant