Repository navigation
Add release-tag workflow for tagging from CI - #71
Merged
Merged
Conversation
Environments that cannot push tags directly can dispatch this workflow to tag a master commit (after checking the CMake version and that the tag is new) and start package.yml on the tag ref. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GWrEYUASNh3BnMktJQ7F9J
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-tag.yml, a manually dispatched workflow that creates a release tag from CI. Use it in environments that can't push tags directly.Inputs:
version(without the leadingv) and an optionalsha(defaults to the master head).The workflow checks these before it tags:
CMakeLists.txtat that commit declares the same versionv<version>does not already existIf they all pass, it pushes an annotated
v<version>tag using the workflow token. Tags pushed with that token don't fire push workflows, so it then runsgh workflow run package.yml --ref v<version>.package.ymlkeys its release path offgithub.ref, so the result matches a manually pushed tag. The release gate is unchanged: publication still waits for the tagged commit'stest.ymlpush run on master.I ran the tag script locally against a scratch bare remote. It rejected an invalid version, a version mismatch, an off-master commit, an unknown SHA and an existing tag, and it created an annotated tag on the given commit.
CLAUDE.mdgets a short note on the workflow.First use: tag
1a581cf5(#70 merge, version 0.9.25) asv0.9.25.🤖 Generated with Claude Code
https://claude.ai/code/session_01GWrEYUASNh3BnMktJQ7F9J
Generated by Claude Code