docs: VS Code extension release roadmap#17
Conversation
Document the three release tiers for the VS Code extension (VSIX, Marketplace, CI automation) plus Swift CLI/library tagging and versioning. Cross-link from the architecture doc and the extension README. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 107dded0a2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Pull request overview
Adds a release & distribution roadmap documenting how to package/publish the VS Code extension and how to tag/release the Swift CLI/library, then cross-links it from existing docs/README locations.
Changes:
- Add
DOCS/Release.mddescribing VSIX packaging, Marketplace publishing, and a future CI tag-based release flow. - Link the release roadmap from
DOCS/Architecture.md(“Releasing” section). - Add a “Release” section to the VS Code extension README pointing to the roadmap.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| editors/vscode/README.md | Adds a “Release” section linking to the release roadmap. |
| DOCS/Release.md | New release/distribution roadmap for the Swift CLI/library and VS Code extension. |
| DOCS/Architecture.md | Adds a “Releasing” section linking to the new release documentation. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Tier 3: warn that version lives in package.json, not the vscode/v* tag; release must bump+commit package.json first (Codex P2). - Extension README: use an absolute GitHub URL so the link resolves in the packaged Marketplace README, not just on GitHub (Copilot). - Soften the PATH requirement (serverPath setting is an alternative) and clarify the full Marketplace identifier is 0al-spec.hypercode (Copilot). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
What
Adds
DOCS/Release.md— the release & distribution roadmap for both shipped artifacts:vsce package) for local install / GitHub Release assets0al-specpublisher + Azure DevOps PAT →vsce publish)vscode/v*tag (package → upload asset → publish viaVSCE_PATsecret)Cross-linked from
DOCS/Architecture.md("Releasing" section) and the extensionREADME.md.Why
The extension and CLI were build- and CI-verified but had no documented release path. This captures the manual prerequisites (publisher registration,
VSCE_PATsecret) and the eventualgit tag vscode/v*flow.Notes
Docs only — no code changes. The CI workflow described in Tier 3 is intentionally not added here; it depends on the manual
VSCE_PAT/ publisher setup that only the maintainer can do.🤖 Generated with Claude Code