Repository navigation
ci: allow running the release workflow manually - #40
Merged
Merged
Conversation
Add a workflow_dispatch trigger with a version input to release.yml. A manual run validates that the tag does not exist yet, runs the same checks and NuGet publishing, and lets softprops/action-gh-release create tag v<version> on the selected commit. Useful when tags cannot be pushed from the release environment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JWng6Vbuo8rweWS5x8PX56
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.
Summary
Adds a
workflow_dispatchtrigger (with a requiredversioninput) to.github/workflows/release.yml, so a release can be started from Actions → Release → Run workflow when pushing a tag is not possible from the release environment.v*→ version from the tag name).version(e.g.0.7.0-alpha), fails if tagv<version>already exists, runs the same format/analyzers/build/test/metadata checks and NuGet publishing, andsoftprops/action-gh-releasecreates tagv<version>on the selected commit together with the GitHub Release.env(no script injection) and still validated by the existing SemVer / csproj / CHANGELOG checks.RELEASING.mddocuments the manual path.Needed to publish v0.7.0-alpha (merged in #39): this session can push only its own branch, tag pushes are rejected with 403.
Test plan
release.ymlparses as valid YAMLversion=0.7.0-alphaonmain🤖 Generated with Claude Code
https://claude.ai/code/session_01JWng6Vbuo8rweWS5x8PX56
Generated by Claude Code