Skip to content

chore(vscode-wcs): release 1.15.0 - #279

Merged
mogera551 merged 1 commit into
mainfrom
chore/vscode-wcs-1.15.0
Sep 14, 2026
Merged

mogera551 merged 1 commit into
mainfrom
chore/vscode-wcs-1.15.0

Conversation

@mogera551

Copy link
Copy Markdown
Contributor

Releases the VS Code extension 1.15.0. It bundles the @wcstack/state 2.4.0 dist, rebuilt by the 2.4.0 release, so it includes $scan.

Changes

  • packages/vscode-wcs/package.json and package-lock.json: 1.14.0 → 1.15.0, via npm version minor --no-git-tag-version.
  • packages/vscode-wcs/CHANGELOG.md: ## Unreleased## 1.15.0 — 2026-09-15, plus the bundled state version line. The file keeps its CRLF line endings.

The changelog entries cover the three vscode-wcs commits since vscode-wcs-v1.14.0, all about static $scan validation (#275). The generated builtin-tag catalog is unchanged since 1.14.0.

Verification

Check Result
npx vitest run 37 files / 897 tests, all passing
npx tsc --noEmit clean
npm run package 890 files, 4.31 MB (1.14.0 was 890 files, 4.29 MB)
vsix contents extension/package.json is 1.15.0, and the changelog opens with ## 1.15.0 — 2026-09-15
bundled validators server.cjs, schema-core.cjs and cli.cjs contain wcs/scan-declaration-invalid, wcs/scan-source-computed and wcs/scan-path-missing
packaging hygiene no @wcstack/* under extension/node_modules, README links use the packages/vscode-wcs base, and none point to blob/HEAD

The CI matrix skips vscode-wcs; the wcs-validate job is the gate for this package.

After merge

  • Tag the merge commit vscode-wcs-v1.15.0 (annotated).
  • Publish the vsix that was checked: npx @vscode/vsce@3.9.2 publish --packagePath <vsix>.
  • Confirm the result with vsce show wcstack.wcstack-intellisense --json.

🤖 Generated with Claude Code

Bundle the @wcstack/state 2.4.0 dist and close the changelog for the static \ validation.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mogera551
mogera551 merged commit 790594f into main Sep 14, 2026
5 checks passed
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