Repository navigation
chore(release): 7.1.0 - #99
Merged
Merged
Conversation
Checks and services that extensions built on this package were writing by hand: `DeclaredContributions.engines` (#90), `filterLogger` (#91), `checkRelativePath` (#95) and the `Workspace` service (#96, #97). Two fixes: the command-line tool reads bundles that touch `vscode` while a module is being defined (#88), and hosted services that had started are stopped when activation ends early (#92). The VS Code floor stays at ^1.138.0. 7.0.1 was prepared (#89) but never tagged or published. Its changes -- the command-line fix and the documented change to how the floor moves (#86) -- ship here instead, so the changelog folds its section into this one and the 7.0.1 comparison link goes away. Against the published 7.0.0 tarball, nothing was removed: dist/ gains 16 files and src/ 4 (relative-path, workspace, the fake workspace and its VS Code adapter), and every changed file belongs to one of the pull requests above. The API was tried in quick-utils from a local tarball first, where its own code compiled and passed unchanged before any of it was adopted. 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
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.
Release 7.1.0: checks and services that extensions built on this package were writing by hand, and two fixes. The VS Code floor stays at
^1.138.0.What ships
DeclaredContributions.engines(feat(testing): check engines.vscode against the VS Code floor #90)filterLoggerandLogThreshold(feat(logging): add filterLogger for an extension's own log-level setting #91)checkRelativePathandRelativePathProblem(feat(workspace): add checkRelativePath for a setting that names a folder #95)Workspaceservice withcreateFakeWorkspace(feat(workspace): add a Workspace service for the open folders #96, refactor(workspace): give the Workspace service the fake's shape #97)vscodewhile a module is being defined (fix(cli): read bundles that touch vscode while their module is defined #88);ManifestMismatch['kind']gains'engine', and the changelog entry says so. Nothing was removed or narrowed.7.0.1
7.0.1 was prepared (#89) but never tagged or published. Its changes ship in this release instead. The changelog folds the 7.0.1 section into the 7.1.0 one and drops the 7.0.1 comparison link.
Against the published 7.0.0
A fresh
npm packof this branch was unpacked next to the published 7.0.0 tarball.dist/src/bin/Verified
npm run qualitypasses, with 1136 tests.npm run verify:packagepasses: 561 files, 613 KiB against the 650 KiB budget.package.jsonandpackage-lock.jsonboth say 7.1.0, and the changelog has a 7.1.0 section and comparison link.filterLogger,Workspaceandengines: true, it passed its unit and integration suites and its 13 checks in a real Extension Host;🤖 Generated with Claude Code