Repository navigation
Make releases manual and run only CI on pull requests - #21
Merged
Merged
Conversation
Pull requests and pushes now run CI only; they no longer build release binaries. Tagging and publishing run only when the workflow is started by hand (workflow_dispatch) on main. An existing tag is reused at its commit rather than failing, so a version tagged earlier (such as 0.90.0-55.2.0) can still be released from a later main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UeniBEAYTk8VRbWnNeSJ9F
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
main(workflow_dispatch). That run does CI → tag → build both platforms → publish.Cargo.lock(<vortex-version>-<df-version>). It is created at the currentmaincommit if missing. An existing tag is reused at its commit instead of failing, so builds always come from the tagged source.Cargo.lockbefore/after comparison, since tagging no longer happens on push.Releasing 0.90.0-55.2.0 after this merges
The tag
0.90.0-55.2.0already exists at1f59ff8(#20), but its binary release was never published: the macOS build in run 42631145031 was cancelled before a runner picked it up. Once this is onmain, run the workflow manually. It will reuse the tag, build from1f59ff8, and publish the release.Notes
macos-14runner keeps getting cancelled, it may need to move tomacos-15. That change is not in this PR.workflow_dispatchcan only be exercised once this is on the default branch.Generated by Claude Code