Repository navigation
ci(release): create the GitHub release after tagging - #188
Merged
Merged
Conversation
The release workflow published to npm and pushed the tag but never created a GitHub release. The cli-docs documentation release check compares GitHub's latest stable release with npm, so it failed after every zoom release until someone created the release by hand (0.29.0, 0.30.0). The tag job now creates the release right after pushing the tag, the same way tg-cli, max-cli and drive-cli do: title is the bare version, notes are that version's CHANGELOG.md section. It reuses the job's existing contents: write permission; no new action or permission is added. docs/dev/RELEASING.md drops the manual "publish the GitHub release" step and keeps only the recovery path for a failed tag job. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The release workflow publishes to npm and pushes the tag, but never creates a GitHub release. The cli-docs "Documentation release check" compares GitHub's latest stable release with npm, so it failed after every zoom release until the release was made by hand (v0.29.0, v0.30.0).
What
.github/workflows/release.yml: thetagjob gets a step after the tag push that creates the release, copied from tg-cli, max-cli and drive-cli.awkcuts the## <version>section fromCHANGELOG.mdand pipes it togh release create "v$VERSION" --title "$VERSION" --notes-file -. The title is the bare version, as in the existing releases ("0.30.0"). It uses thecontents: writepermission the job already has; no new action, no new permission.docs/dev/RELEASING.md: drops the manual "create the GitHub release" step; keeps a recovery note for when the tag job fails.Testing
awkextraction run locally onCHANGELOG.mdfor 0.30.0 prints exactly that section.pnpm standards:check,pnpm lint,pnpm docs:lint,pnpm docs:checkpass.🤖 Generated with Claude Code