extension-release
Release or pre-release the VS Code extension for Dataform tools to Visual Studio Marketplace and Open VSX using justfile recipes. Use when the user asks to release, pre-release, bump version, publish extension, or cut a release.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 95
- Forks
- 15
01 前言 Front Matter
- name
- extension-release
- description
- Release or pre-release the VS Code extension for Dataform tools to Visual Studio Marketplace and Open VSX using justfile recipes. Use when the user asks to release, pre-release, bump version, publish extension, or cut a release.
03 SKILL.md 正文
Release workflow for the VS Code extension (dataform-lsp-vscode). Monorepo sub-packages in packages/* are handled independently by Release Please on main.
Channel & Version Conventions
VS Code marketplace extensions use minor version parity for release channels:
- Odd minor (e.g.
1.13.x,1.15.x) = pre-release. - Even minor (e.g.
1.12.x,1.14.x) = stable release.
When asked to release:
- Check current version:
just version. - Determine bump target:
- Pre-release requested:
- If current minor is odd (e.g.
1.13.5): patch bump (1.13.6). - If current minor is even (e.g.
1.12.13): bump minor to the next odd minor (e.g.1.13.0).
- If current minor is odd (e.g.
- Stable release requested:
- If current minor is odd (e.g.
1.13.5): bump minor to the next even minor (1.14.0). - If current minor is even (e.g.
1.14.2): patch bump (1.14.3).
- If current minor is odd (e.g.
- Pre-release requested:
Release Lifecycle
Releases are semi-autonomous: prepare and validate locally, stop for user confirmation, then push and monitor deployment.
Phase 1: Local Verification & Bump
- Verify working directory and upstream sync:
just preflight - Inspect unreleased changes and preview version:
just changes just preview <bump> - Run test and build checks:
just check - Cut the release locally:
This updatesjust release <bump>package.json, generatesCHANGELOG.md, commitschore(release): X.Y.Z, and creates the local tagvX.Y.Z.
Phase 2: User Approval Gate
STOP HERE. Do not push to remote origin without explicit user consent. Show:
- The new version and channel (pre-release or stable).
- Summary of changes (
git show --stat HEAD). - Ask the user to confirm pushing and publishing to the marketplaces.
(If the user requests changes or aborts: run NON_INTERACTIVE=1 just undo-release to cleanly drop the tag and reset the commit).
Phase 3: Publish & Watch Deploy
Once confirmed by the user, execute:
- Push release commit and tag:
NON_INTERACTIVE=1 just push-release - Follow GitHub Actions marketplace deploy:
just watch-deploy - Create GitHub Release with auto-generated release notes:
NON_INTERACTIVE=1 just github-release