Skip to content

docs: align release flow with trusted publishing #35

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 #35

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
4 changes: 2 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,8 +164,8 @@ For an authorized release:
`validate (ubuntu-latest)` checks. Do not bypass those rules.
7. After the pull request is merged, create an annotated `vX.Y.Z` tag on the
merged commit and push it.
8. Create the GitHub Release with the VSIX attached, then verify the remote asset
digest and all CI/CodeQL checks.
8. The tag push runs the Release workflow, which creates the GitHub Release with
the VSIX attached. Verify the remote asset digest and all CI/CodeQL checks.

Visual Studio Marketplace and Open VSX publication is performed by the repository
owner. After the GitHub Release exists, dispatch the Release workflow with that
Expand Down
Loading