Repository navigation
Description
Observed controller bug
Hive's readiness receipts report these PRs as ready for a human merge and "blocked only by role/untrusted" even though required native check contexts are absent. GitHub strict branch protection correctly prevents landing. Author trust is therefore not the only remaining gate.
Reproducible exact-head evidence
projectbluefin/utah#1074
- PR: chore(baselines): refresh Bluefin, Dakota and Utah image baselines utah#1074
- Source head:
0c56fd61ca6b341fc2ee7105e2e2850d3d3981bf - Native merge state:
BEHIND - Present check-run names:
transfer,label-sync,authorize,prow / prow - Missing required contexts:
contract,build_main / Check all testing builds successful - Hive receipt:
Ready for a human merge: verdict approved @0c56fd6, 4/4 checks green, soak 30m0s elapsed. Blocked only by
role/untrusted(no verified hive claim or registry tier).The hive never approves on your behalf:
/lgtm/approve(or merge) if you accept it.
projectbluefin/utah#1072
- PR: ci(extensions): bump pinned GNOME extensions utah#1072
- Source head:
b3bbb2c87581df86406c676a3c15497b455933dd - Native merge state:
BEHIND - Present check-run names:
build_kernel,dispatch-iso,review_vm,kernel_cache,build_main,contract - Missing required contexts:
build_main / Check all testing builds successful - Hive receipt:
Ready for a human merge: verdict approved @b3bbb2c, 6/6 checks green, soak 30m0s elapsed. Blocked only by
role/untrusted(no verified hive claim or registry tier).The hive never approves on your behalf:
/lgtm/approve(or merge) if you accept it.
projectbluefin/utah-packages#873
- PR: chore(buildroot): move the build root to 44-20261102-d68cae918577 utah-packages#873
- Source head:
bf88694fddee89dad21b192442283a21b0552fcc - Native merge state:
BEHIND - Present check-run names:
report,validate - Missing required contexts:
Canary,Unit tests,Runtime contract - Hive receipt:
Ready for a human merge: verdict approved @bf88694, 2/2 checks green, soak 30m0s elapsed. Blocked only by
role/untrusted(no verified hive claim or registry tier).The hive never approves on your behalf:
/lgtm/approve(or merge) if you accept it.
Owning component and fix
This is a Hive readiness/admission diagnostic bug, not a request to relax Utah's rules or manufacture success statuses. The implementation lives in Hive's controller/readiness logic; common's operator should route/link the concrete upstream fix and deployment. A documentation-only PR does not implement this behavior and must not close this issue.
Resolve effective branch requirements from applicable rulesets/classic policy, match them against the exact candidate head and expected check producer, and keep absent/pending/unreadable evidence explicit. Do not equate "all discovered checks passed" with "all required checks exist and passed". Strict freshness, internal review, author trust and holds are separate gates and must be reported as such.
Acceptance
- The three exact examples above report missing required checks and BEHIND, not "blocked only by role/untrusted".
- Deterministic regressions cover no required contexts emitted; partial required contexts; same-name wrong producer; pending/unavailable policy evidence; and complete required evidence with a separate author-trust hold.
- Preserve native check names/producer bindings and existing protections. No synthetic success checks or blanket trust of github-actions-authored PRs.
- Verify live behavior in both Utah repositories after deploying the actual Hive fix; link the source PR, deployed version and receipt.
- Only an actual eligible head may be presented as ready, and resolving author trust must not imply CI has been supplied.
Related producer repairs
projectbluefin/utah#1078 / projectbluefin/utah#1073 and projectbluefin/utah-packages#878 / projectbluefin/utah-packages#874 address future App-authenticated proposal events. They do not retroactively create checks on these old heads or change the immutable author of an existing github-actions PR. Baseline proposal projectbluefin/utah#1074 is another affected producer case and needs its own correct CI handoff.
Tracking umbrella: #1615. Owner policy is approved in projectbluefin/utah#1082; capability and privileged-handoff decisions remain separate in #1611 and #1612. No hold release, merge approval or wider App grant is requested here.
Activity
github-actions commentedon Nov 2, 2026
Issue triage
Next action: a triager or maintainer reviews this issue.
Reporter or contributor
kind/*label is set, categorize the issue with one of:/kind bug,/kind regression,/kind security,/kind feature,/kind documentationor/kind cleanup./area <area>:desktop,flatpak,gaming,hardware,installerordx.Triager or maintainer
/triage accepted. Only triagers and maintainers can do this; acceptance does not assign an implementer.needs-kindclears when a kind is set.needs-triageand this post clear when triage is accepted.See Triage & Prow Commands for all available commands.
🐛 fix(stage): the 090 comment names a base that requires up-to-date b…
Danathar commentedon Nov 20, 2026
Closing as completed: both parts of this bug are fixed in the hive, and the fixes are in the build projectbluefin's hive runs (Danathar, maintainer, 11-19).
060instead of090-ready-for-human-merge.role/untrusted" on a PR GitHub reported as BEHIND: fixed by 🐛 fix(stage): the 090 comment names a base that requires up-to-date branches instead of "Blocked only by" trust hivecommons/hive#17551 (merged 2026-11-10), which cites this issue. The 090 comment now says the base requires up-to-date branches instead of blaming author trust.c371496(v6, upgraded 2026-11-19), and both fix commits are in its history.Reopen this with the PR link if a PR is labelled ready while a required check is missing.