ci: unreleased changes check + tag safety in release workflow#66
Merged
Conversation
Warns when source commits accumulate on main without a version bump, preventing fixes from sitting unreleased like the v1.6.0 → v1.6.1 gap.
commit: |
Adds explicit git tag creation step before gh release create, so tags exist even if the release step fails partway. Also passes --verify-tag to gh release create for safety.
jpr5
changed the title
jpr5
added a commit
that referenced
this pull request
Apr 3, 2026
## Summary Two CI improvements to prevent the v1.6.0 → v1.6.1 gap from happening again. ### 1. Unreleased changes check (`unreleased-check.yml`) Runs on every push to main. Compares HEAD against the latest version tag and emits a `::warning` annotation when source commits exist without a version bump. Skips gracefully when the tag doesn't exist yet (i.e., the push IS the release). ### 2. Tag safety in release workflow (`publish-release.yml`) - Explicit `git tag` + `git push origin <tag>` step before `gh release create` - `--verify-tag` flag on `gh release create` for belt-and-suspenders safety - Outputs version for reuse across steps ### Also going forward Release commits must use `chore: release vX.Y.Z` format to pass commitlint. Always create a branch first, never commit directly to main.
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.
Summary
Two CI improvements to prevent the v1.6.0 → v1.6.1 gap from happening again.
1. Unreleased changes check (
unreleased-check.yml)Runs on every push to main. Compares HEAD against the latest version tag and emits a
::warningannotation when source commits exist without a version bump. Skips gracefully when the tag doesn't exist yet (i.e., the push IS the release).2. Tag safety in release workflow (
publish-release.yml)git tag+git push origin <tag>step beforegh release create--verify-tagflag ongh release createfor belt-and-suspenders safetyAlso going forward
Release commits must use
chore: release vX.Y.Zformat to pass commitlint. Always create a branch first, never commit directly to main.