ci: publish release candidates manually via workflow_dispatch - #77
Merged
Conversation
- Exclude v*-rc* tags from the push trigger. RCs are now published by triggering the Release workflow manually with the tag as input: the workflow validates the -rc suffix, runs CI against the tag, and marks the GitHub release as a pre-release. - Pause the nightly pre-release schedule (workflow_dispatch only). - Document the AI-assisted contributions policy in CONTRIBUTING.md.
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
v*-rc*tag does nothing; theReleaseworkflow gains aworkflow_dispatchtrigger that takes the RC tag as input, validates the-rcsuffix, runs CI against that tag (viacheckout_ref), and publishes it as a GitHub pre-release. Stable tag pushes keep the fully automatic flow.workflow_dispatch.CONTRIBUTING.md, mirroring the images repo.