Skip to content

jsr-publish: create the vX.Y.Z release when publishing - #398

Merged
lann merged 1 commit into
mainfrom
jsr-publish-release
Aug 23, 2026
Merged

jsr-publish: create the vX.Y.Z release when publishing#398
lann merged 1 commit into
mainfrom
jsr-publish-release

Conversation

@lannbot

@lannbot lannbot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

After a successful deno publish, the workflow now creates the
vX.Y.Z tag + GitHub release at the run's commit (title
" vX.Y.Z", body per the release-notes convention), replacing the
manual release-first step. A pre-created release is left alone; a bare
tag without a release fails loudly rather than letting
gh release create bind the release to the old tag's commit. Requires
contents: write.

After a successful `deno publish`, the workflow now creates the
`vX.Y.Z` tag + GitHub release at the run's commit (title
"<repo> vX.Y.Z", body per the release-notes convention), replacing the
manual release-first step. A pre-created release is left alone; a bare
tag without a release fails loudly rather than letting
`gh release create` bind the release to the old tag's commit. Requires
contents: write.
@lann
lann merged commit 2bdaaa4 into main Aug 23, 2026
10 checks passed
@lann
lann deleted the jsr-publish-release branch August 23, 2026 16:51
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.

2 participants