chore(release): 0.9.1 - #87
Merged
Merged
Conversation
Cuts 0.9.1: renames the Unreleased section, bumps the manifest and lockfile with npm version, and adds the compare link. The section also records the switch of the release workflow to Microsoft Entra ID and vsce 4.0.0, since both touch how the package reaches the Marketplace. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts 0.9.1. Renames the
Unreleasedsection to0.9.1, bumps the manifest andlockfile with
npm version, and adds the compare link.Why patch
The release carries one fix and nothing a user configures changes. No
command, setting or default moves, and
engines.vscodestays at^1.138.0, sono installation is cut off.
The fix is the workspace containment check from #85. For a path whose parent
folder already exists — every save after the first, and the first save into the
default
.clipshotfolder — it reaches the same verdict as 0.9.0, because bothresolve the parent and append the file name. The verdict can only change when
two or more levels are still missing and the existing part of the path resolves
to something other than its spelling: a link, or an 8.3 short name on Windows.
What ships
@vscode/vsce4.0.0. The runtime dependencies are unchanged: no productionpackage in the lockfile differs from
v0.9.0, andsharp,@kkdev92/vscode-ext-kitandesbuildare at the versions 0.9.0 shipped.Verification
0.9.1section cut with the sameawkrange therelease uses:
### Changedand### Fixedonce each, and nothing from 0.9.0.package.json,package-lock.jsonand the lockfile root all read0.9.1.npm run verifyon this branch, exit 0: lint, compile, test typecheck,495 unit tests across 20 files with the coverage gate (89.76% statements,
78.3% branches), and 13 e2e tests in a real Extension Host (VS Code
1.139.1).
vsce package --target win32-arm64with vsce 4.0.0, thenscripts/verify-vsix.mjs win32-arm64: passed, andsharploads from thepackage. The archive holds the same 116 entries as the 0.8.0 package built
with vsce 3.9.2; the only entries whose size differs are the bundle, the
README and the changelog.
🤖 Generated with Claude Code