メニュー
Promotion criteria, monthly release cadence, hotfix procedure, and artifact verification for projectbluefin/common. Use when cutting a release, understanding the promotion pipeline, or verifying release artifacts.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/projectbluefin/common --skill release-promotionコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Manage OS-managed Homebrew packages. Use when adding/removing default brew packages, moving tools between RPM and brew, or auditing image-vs-brew placement.
OEM hardware first-boot setup hooks in projectbluefin/common. Use when adding hardware-specific setup, understanding hook directories and versioning contract, or applying shellcheck requirements.
CI policy and tooling — SHA pinning, pre-commit guards, Renovate digest tracking, and workflow config. Use when editing .github/workflows/ files.
| name | release-promotion |
| version | 1.1 |
| last_updated | 2026-08-08 |
| id | release-promotion |
| one_line_purpose | Cut releases and verify promotion/hotfix artifacts. |
| entry_point | docs/skills/release-promotion/SKILL.md |
| category | ci-ops |
| mcp_compliance_level | partial |
| optimization_status | draft |
| status | active |
| dependencies | [] |
| tags | ["release","promotion","staging"] |
| description | Promotion criteria, monthly release cadence, hotfix procedure, and artifact verification for projectbluefin/common. Use when cutting a release, understanding the promotion pipeline, or verifying release artifacts. |
| metadata | {"type":"reference"} |
Load this when cutting a release, evaluating whether a monthly tag is safe to create, doing a hotfix, or verifying signed artifacts.
:testing buildsci-tooling.mdstartup_failure → ci-pitfalls.mdA common release is safe when all of the following are true:
| Criterion | How to verify |
|---|---|
| Post-merge E2E is green | Check .github/workflows/e2e.yml run on latest main commit |
No PRs on hold targeting main | gh pr list --repo projectbluefin/common --search "label:hold" --base main |
| No open P0 issues | ~/src/hive-status — zero 🔴 blockers |
| Promotion-candidate E2E passed this week | Check .github/workflows/promotion-candidate-e2e.yml (runs Tuesdays) — no open blocker issue from it |
If any criterion fails, do not tag a release. File or escalate the blocker issue and wait.
Planned gate (common#513): The monthly
release.ymlwill be updated to run the promotion-candidate E2E as a required prerequisite job before creating the GitHub Release. Until that ships, the check above is manual.
release.yml cron)v<YEAR>.<MONTH>v2026.06main HEAD:latest is always the most recent merge to mainWhen a critical fix needs a versioned tag outside the monthly window:
main via normal PR processrelease.yml manually via workflow_dispatch — it will tag the current main with the current month's tag (or create a patch tag manually with gh release create)| Rationalization | Reality |
|---|---|
| "E2E is green, so we can tag." | Check all four criteria — E2E alone is not sufficient. |
| "The promotion PR will auto-merge once CI passes." | Merge queue enqueue can fail due to required status checks not completing; verify after squash branch rebuild. |
| "The squash conflict is from someone else's PR." | You can still fix the squash branch — see troubleshooting. |
"The ci(promote): PR title is what triggers execute-release." | execute-release.yml matches the commit message that lands on the target branch (chore: promote ...), not the PR title. |
release/blocked with no E2E evidence → check post-testing-e2e.yml branches: filterpromote-testing-to-main.yml fails with UD conflicts → file deletions on testing haven't reached mainPublish workflow stuck in_progress > 30 min → zombie run holding concurrency queueexecute-release.yml not triggering after promotion PR merges → check commit subject matchgh attestation verify (keyless, post-2026-06-11), not just cosign verifyPR Validation — testsuite to complete before enqueuing| File | Description |
|---|---|
| references/supply-chain.md | Supply chain current state (signing, SBOM, SLSA, CVE), required permissions, and artifact verification commands. |
| references/downstream-propagation.md | How common updates reach bluefin, bluefin-lts, and dakota :testing builds (Renovate + BST). |
| references/pr-based-release.md | PR-based squash promotion model, schedule, commit title rules, repo variants, E2E gate model, and reusable workflow patterns. |
| references/troubleshooting.md | Troubleshooting the testing→main squash promotion: gate stuck, UD conflicts, merge queue blocked, branch divergence, zombie publish runs, actions branch policy. |