Skip to content

ci(promote): utah testing → main 2026-11-18 - #1277

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
auto/promote-testing-to-main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
auto/promote-testing-to-main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

🦕 Utah testing → main · 2026-11-18

Auto-maintained by promote-testing-to-main.yml · Updated 2026-11-18T04:17:51Z · Run ↗

Release checklist

✅ All checks passed

Check Status Details
Digest resolution ✅ passed Resolved 4 digest(s) from testing.
Cosign signatures ✅ passed All resolved digests passed cosign verification.
E2E ⏭️ skipped E2E check disabled by caller. Caller disabled the E2E gate.

Variants being promoted

Variant Tag
utah :testing
utah-nvidia :testing
utah-gaming :testing
utah-nvidia-gaming :testing

Changes in this promotion

4 files changed (+6 / −6) against the current main tip · Compare main…testing ↗

Changed files (4)
File + −
.github/workflows/build.yml 3 3
.github/workflows/execute-release.yml 1 1
.github/workflows/promote-testing-to-main.yml 1 1
.github/workflows/sync-main-to-testing.yml 1 1

Follow this repository's branch-protection requirements before merging. Force: gh pr merge <pr-number> --repo projectbluefin/utah --merge --admin

Caution

Auto-merge scheduled for Tuesday 04:00 UTC (bluefin/dakota).
To block this release: add the do-not-merge label to this PR before that time.
Remove the label when the issue is resolved -- the next weekly window will pick it up automatically.

@github-actions github-actions Bot added the release/ready Release gate checks passed label Nov 16, 2026
@hivecommons-hive hivecommons-hive Bot added no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/untrusted Author has no registry profile or verified hive claim (or is revoked); never auto-merged stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 16, 2026
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor Author

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign ahmedadan after the PR has been reviewed.
You can assign the PR to them by writing /assign @ahmedadan in a comment when ready.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hivecommons-hive hivecommons-hive Bot added the stage/stalled In its current stage longer than expected label Nov 16, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 from e0ab176 (LUKS test for b0484919808a, run 43771896520, created 2026-11-15) back to 107d6b8 (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's README.md:4-6 is 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:
    -[![Verified ISO desktop](https://github.com/projectbluefin/utah/raw/107d6b8035d2a3437f9af3a7eebf6ee6d36150a9/screenshots/installed-fastfetch.png)](https://github.com/projectbluefin/utah/blob/107d6b8035d2a3437f9af3a7eebf6ee6d36150a9/README.md)
    +[![Verified ISO desktop](https://github.com/projectbluefin/utah/raw/e0ab176b910920b468b0384912bc53f94c373fd5/screenshots/installed-fastfetch.png)](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, and main and testing now 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

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Review follow-ups (below review.backlog.min_severity: P2)

Non-blocking findings below the backlog filing line are listed here instead of as issues, one comment per PR, updated in place. Tick them off as they are fixed; set review.backlog.min_severity: P3 to file every finding.

@hivecommons-hive hivecommons-hive Bot added stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 18, 2026
@github-actions
github-actions Bot force-pushed the auto/promote-testing-to-main branch from 05edc0f to 39788ee Compare November 18, 2026 04:17
@github-actions github-actions Bot changed the title ci(promote): utah testing → main 2026-11-16 ci(promote): utah testing → main 2026-11-18 Nov 18, 2026
@hivecommons-hive hivecommons-hive Bot added sentinel-alert and removed stage/stalled In its current stage longer than expected labels Nov 18, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor
39788ee

⚠️ Sentinel alert — maintainer review required

Hive flagged this PR (author @github-actions[bot], head 39788ee0359d) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 4 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • .github/workflows/build.yml
    • .github/workflows/execute-release.yml
    • .github/workflows/promote-testing-to-main.yml
    • .github/workflows/sync-main-to-testing.yml

Hive added the sentinel-alert label. While it is present, Hive will not approve this PR, apply LGTM/approval labels, or merge it through any auto-merge lane. Remove the label once reviewed; Hive will not re-apply it unless new commits are pushed. Tune paths and behaviors under sentinel in hive.yaml or the dashboard Security tab.

@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) labels Nov 18, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

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

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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, so main's refreshed record from #1312 stands.
  • [intent-alignment] Promotion is stale: still present. main (1b3bb9bd) is testing (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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@hivecommons-hive hivecommons-hive Bot added stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 18, 2026
@hanthor

hanthor commented Nov 18, 2026

Copy link
Copy Markdown
Member

Closing: stale promotion. Merging it would put an older ISO record back in the README, and #1312 replaces it. The next promotion is generated fresh.

Decided by @hanthor (posted with Claude Code)

@hanthor hanthor closed this Nov 18, 2026
@hanthor hanthor reopened this Nov 18, 2026
@hanthor

hanthor commented Nov 18, 2026

Copy link
Copy Markdown
Member

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

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-dco A commit is missing Signed-off-by — run `git rebase --signoff` release/ready Release gate checks passed role/untrusted Author has no registry profile or verified hive claim (or is revoked); never auto-merged sentinel-alert stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant