Skip to content

Switch main internal-release to the automated-bump guard (fixes #378 leftover) - #380

Open
Devesh-Skyflow wants to merge 1 commit into
mainfrom
devesh/sk-3023-guard-main-v2
Open

Switch main internal-release to the automated-bump guard (fixes #378 leftover)#380
Devesh-Skyflow wants to merge 1 commit into
mainfrom
devesh/sk-3023-guard-main-v2

Conversation

@Devesh-Skyflow

Copy link
Copy Markdown
Collaborator

#378 merged before it was converted from the skip-ci workaround to the scoped guard, so main is still on the bandage and inconsistent with the v3 line (which now uses the guard). This corrects main.

Change

  • internal-release.yml: add if: ${{ !contains(github.event.head_commit.message, '[AUTOMATED]') }} to the build-and-deploy job — the automated version-bump commit can no longer re-trigger the release (the loop), while PR CI and all other workflows still run.
  • shared-build-and-deploy.yml: drop the skip-ci suffix from the bump commit message (the guard replaces it).

Why the guard, not skip-ci

skip ci is global — it suppresses every workflow on the commit, including PR checks (that's the bug we hit on the release PR). The identity/marker guard is scoped to internal-release only.

Validated live on the v3 line: real commit → release ran; the automated bump it pushed was skipped (no loop), and PR CI ran normally.

🤖 Generated with Claude Code

#378 merged the earlier skip-ci version before it was converted to the guard,
so main is still on the bandage and inconsistent with the v3 line. This
switches main to the scoped guard: the release job is skipped when the
triggering push's head commit is an automated bump, so the PAT-authored
bump cannot re-trigger the release, without globally skipping CI.

- internal-release.yml: add the head-commit guard on the automated bump marker
- shared-build-and-deploy.yml: drop the skip-ci suffix from the bump commit
@github-actions

Copy link
Copy Markdown

Gitleaks Findings: No secrets detected. Safe to proceed!

@github-actions

Copy link
Copy Markdown

Semgrep Findings: Issues with Error level severity are found (Error is Highest severity in Semgrep), Please resolve the issues before merging.

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