Skip to content

ci: run the staging version job on staging only - #8

Open
bryanfawcett wants to merge 2 commits into
stagingfrom
fix/staging-version-guard
Open

bryanfawcett wants to merge 2 commits into
stagingfrom
fix/staging-version-guard

Conversation

@bryanfawcett

Copy link
Copy Markdown
Contributor

staging-version.yml's workflow_dispatch had no branch guard. Once the file is on main (the default branch the Run workflow form preselects), a manual run from main would tag main's HEAD as a staging version with a "(beta)" pre-release. The version job now runs only when github.ref is refs/heads/staging; pushes to staging are unaffected.

Found by /code-review on the staging -> main release PR. actionlint clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq

workflow_dispatch had no branch guard, so a manual run from main would
tag main's HEAD as a staging beta pre-release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq
Signed-off-by: Bryan Fawcett <bryan@nyuchi.com>
@bryanfawcett bryanfawcett changed the title ci: run the staging version job only on staging ci: run the staging version job on staging only Oct 6, 2026
Match the org-wide guard exactly: the if line directly under the job id.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq
Signed-off-by: Bryan Fawcett <bryan@nyuchi.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant