Enable public releases from versioned release branches#11
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7877f11863
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| release: | ||
| name: Publish GitHub Release | ||
| if: github.ref_type == 'tag' | ||
| if: github.ref_type == 'tag' || startsWith(github.ref, 'refs/heads/release/v') |
There was a problem hiding this comment.
When a workflow_dispatch run is started from a release/vX.Y.Z branch, github.ref is still refs/heads/release/vX.Y.Z, so this condition is true even though the event is manual. That turns a manual artifact build from such a branch into a public GitHub Release, and the version step above also resolves the branch name before honoring inputs.version; require the release-branch path to be a push event so manual runs remain artifact-only.
Useful? React with 👍 / 👎.
|
Public release request completed through
The |
1 participant
Purpose
Enable an authenticated release request through a
release/vX.Y.Zbranch. This is useful when a tag cannot be created directly from the current integration while preserving the same validated release pipeline.Behavior
release/v0.3.0resolves to version0.3.0and tagv0.3.0.After this PR is merged, a
release/v0.3.0branch will be created frommainto publish the first hardened public release.