Repository navigation
ci: release workflow on merge to master - #7
Merged
Merged
Conversation
Creates the vX.Y.Z GitHub release (marked latest, generated notes) after tests, lint and knip pass. Reuses an existing tag; pushes that keep the version are no-ops. Co-Authored-By: Claude Opus 5.5 <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
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.
Adds
.github/workflows/release.yml: on every push to master (a merged PR), ifpackage.jsonversionX.Y.Zhas no GitHub release yet, run tests/lint/knip and publish releasevX.Y.Zmarked latest with generated notes. Existing tags are reused (so merging this releases the already-taggedv0.2.0); pushes that keep the version (e.g. benchmark refreshes) are no-ops.To cut a release: bump
versioninpackage.jsonin the PR and merge.🤖 Generated with Claude Code