Skip to content

docs: align release flow with trusted publishing #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TheStreamCode merged 1 commit into from
Nov 1, 2026
Merged

docs: align release flow with trusted publishing #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,8 @@ Releases are maintainer-only and should start from a clean, up-to-date `main` br
1. Commit the release metadata and merge it through the protected branch workflow.
2. Update the local `main` branch to the merge commit, then rerun `npm ci`, `npm run check`, `npm run audit`, and `npm run package` from that clean commit.
3. Create a signed annotated tag with `git tag -s vX.Y.Z -m "vX.Y.Z"`, then verify it with `git tag -v vX.Y.Z` before pushing it.
4. Publish that exact verified VSIX through the maintainer's Visual Studio Marketplace and Open VSX release channels, then attach the same artifact to a GitHub release with concise notes.
5. Confirm the Marketplace, Open VSX, README badges, GitHub release, and repository default branch all report the same version.
4. The tag push runs the Release workflow, which creates the GitHub Release with the verified VSIX and its SHA-256 checksum.
5. Dispatch the Release workflow with that release tag. It verifies the released VSIX against the asset digest and packaged identity, then publishes it to the Visual Studio Marketplace and Open VSX through OIDC trusted publishing.
6. Confirm the Marketplace, Open VSX, README badges, GitHub release, and repository default branch all report the same version.

Never place marketplace tokens or credentials in the repository, issue comments, workflow output, or release notes.
Loading