Repository navigation
ci(promote): utah testing → main 2026-11-18 - #1277
github-actions[bot] wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Needs approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Summary: This weekly release PR moves the project's "testing" build into the stable "main" branch. The only file it changes is the project's front page, and that change swaps the "latest verified install test" badge for an older one (November 14 instead of November 15). The main branch already shows that older badge, because a feature merge yesterday (#1248) rolled it back, so merging this PR changes nothing in practice. The stale badge should be fixed on main.
docs-currency (out of scope for this PR; the fix belongs on main)
README.md:4-6: the diff swaps the verification record frome0ab176(LUKS test forb0484919808a, run 43771896520, created 2026-11-15) back to107d6b8(d9ff787d873b, run 43616240548, created 2026-11-14). The newer record reached main in #1241 (cee0b7a, the merge base). The Dakota parity merge #1248 (86c861c2422b) then put the old block back, so main'sREADME.md:4-6is already identical to this head. The likely cause is that #1248 was based on a stale README. Restore the newer record on main, for example by re-running the "refresh verified ISO record" job or by reverting the block:-[](https://github.com/projectbluefin/utah/blob/107d6b8035d2a3437f9af3a7eebf6ee6d36150a9/README.md) +[](https://github.com/projectbluefin/utah/blob/e0ab176b910920b468b0384912bc53f94c373fd5/README.md) -*LUKS ISO test passed for commit `d9ff787d873b`. [CI run](https://github.com/projectbluefin/utah/actions/runs/43616240548) also runs ... [screenshots and provenance](https://github.com/projectbluefin/utah/tree/107d6b8035d2a3437f9af3a7eebf6ee6d36150a9).* +*LUKS ISO test passed for commit `b0484919808a`. [CI run](https://github.com/projectbluefin/utah/actions/runs/43771896520) also runs ... [screenshots and provenance](https://github.com/projectbluefin/utah/tree/e0ab176b910920b468b0384912bc53f94c373fd5).*
intent-alignment (info)
- The PR body says the README change is "against the current main tip". It isn't anymore. This head (
05edc0f) is 1 ahead of and 6 behind main, andmainandtestingnow point at the same commit (b4b5285), so the promotion is effectively empty. The bot's next run should refresh or close it.
No findings from: correctness, security, style.
Reviewed head 05edc0f721f45e3f20fa13bbedeb5f46a3ca77b4.
Confidence: 5/5 (safe)
— hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.325
Review follow-ups (below
|
05edc0f to
39788ee
Compare
39788ee
|
|
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor. stage 060-reviewed → 050-review-pending: contributor-lane:sentinel-blocked |
There was a problem hiding this comment.
Summary: This automatic release request is supposed to copy the tested branch onto the main branch. At this revision it copies nothing new from the tested branch. Its only real effect is to roll the shared build-and-release tooling back to a version from five days ago. That older version drops this week's stronger "hold this release" safeguard, so merging it as-is would weaken the release process instead of shipping anything.
What I need from you: Don't merge this revision; re-run the promotion job so the bot rebuilds it from the current tested branch.
correctness (details in the inline thread on .github/workflows/promote-testing-to-main.yml:35)
The head commit 39788ee has testing (d710ed7) as its parent, but it does not carry testing's files. gh api repos/projectbluefin/utah/compare/testing...39788ee… differs in exactly the 4 workflow files in this diff. Each one moves the projectbluefin/actions pin from 75348afb (on both testing and main, from #1208) back to 3adf1194, which is 5 commits older.
Re-check of the previous review (head 05edc0f):
- [docs-currency] README install-test badge rolled back: no longer applies. The PR diff no longer touches
README.md, somain's refreshed record from #1312 stands. - [intent-alignment] Promotion is stale: still present.
main(1b3bb9bd) istesting(d710ed7) plus one docs commit, so there is still no tested content to promote. The pin rollback above is the only change this PR makes.
Limits: I did not prove why the promotion job built this tree. It ran 38 s after #1208 landed on testing (04:17:11Z vs 04:17:49Z), so a stale snapshot of testing is likely, but I have not verified it.
No findings from: security, intent-alignment (beyond the still-present note), style, docs-currency.
Confidence: 3/5 (needs attention) — 1 high finding
— hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.326
| promote: | ||
| needs: variants | ||
| uses: projectbluefin/actions/.github/workflows/reusable-promote-squash.yml@75348afb3a34c6006a3d3da51e51c9a3818b2616 # v1 | ||
| uses: projectbluefin/actions/.github/workflows/reusable-promote-squash.yml@3adf1194c894fe7b1ae54e583c56306c6a2382ee # v1 |
There was a problem hiding this comment.
Promotion rolls shared CI tooling back 5 commits (high). This line and the other three changed uses: lines (build.yml:72,280,330, execute-release.yml:102, sync-main-to-testing.yml:19) move from 75348afb to 3adf1194. Both testing and main already pin 75348afb (#1208), so the change does not come from testing.
The 5 dropped projectbluefin/actions commits include #761 ("enforce merge holds"). At 75348afb, reusable-promote-squash.yml runs merge-label-guard again right before it enables auto-merge or enqueues the PR. At 3adf1194 it checks only do-not-merge, and only once, at upsert. Merging this head would therefore weaken release-hold enforcement on main.
Fix: nothing needs to change on testing, because it is already correct. Re-run promote-testing-to-main.yml so the branch is rebuilt from the current testing tip d710ed7. The result should be an empty diff against main. Do not merge 39788ee.
|
Reopened. I closed this by mistake, judging it from an older revision. The bot regenerated it on 2026-11-18, and it now carries current workflow changes, not the stale README record. Posted on behalf of @hanthor with Claude Code |
🦕 Utah testing → main · 2026-11-18
Release checklist
✅ All checks passed
Variants being promoted
utah:testingutah-nvidia:testingutah-gaming:testingutah-nvidia-gaming:testingChanges in this promotion
4 files changed (+6 / −6) against the current main tip · Compare main…testing ↗
Changed files (4)
.github/workflows/build.yml.github/workflows/execute-release.yml.github/workflows/promote-testing-to-main.yml.github/workflows/sync-main-to-testing.ymlFollow this repository's branch-protection requirements before merging. Force:
gh pr merge <pr-number> --repo projectbluefin/utah --merge --adminCaution
Auto-merge scheduled for Tuesday 04:00 UTC (bluefin/dakota).
To block this release: add the
do-not-mergelabel to this PR before that time.Remove the label when the issue is resolved -- the next weekly window will pick it up automatically.