Repository navigation
release: allow publishing from the Actions tab - #2
Merged
Merged
Conversation
A manual run tags the commit with the version in Cargo.toml and publishes the release, so a release doesn't need a tag push. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KLubvhoPRuPfGsAcdikJjN
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 a
workflow_dispatchtrigger to the Release workflow. A manual run tags the commit it runs on with the version fromCargo.toml(v0.2.0now) and publishes the release with the same signed tarballs, macOS app zip and AppImages. It refuses to run if that tag already exists.Tag pushes keep working as before. This exists so v0.2.0 can be cut without a tag push from the cloud session, which isn't allowed to push tags.
Generated by Claude Code