Repository navigation
Closed
Labels
hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmationHive verified that a merged PR references or claims this issue; pending confirmationkind/featureA new capability.A new capability.needs-triagepriority/p1
Description
This was generated by AI during triage.
What to build
Type: HITL
Track the release-readiness work identified by the Utah/Bluefin/Dakota comparative audit. Dakota is the modern pipeline reference; Utah retains its Hummingbird bootc/RPM architecture while adopting Dakota's evidence, promotion, ISO, and recovery practices.
Audit slices
- ci: publish factory repositories atomically after closure validation utah-packages#22
- ci: rebuild reverse dependencies in incremental factory runs utah-packages#23
- parity: build the complete Bluefin multimedia override closure utah-packages#24
- supply-chain: lock factory buildroots and require recipe provenance utah-packages#25
- parity: track Bluefin's effective package payload #11
- parity: install and assert the factory multimedia transaction #12
- ci: gate testing tags on exact-digest VM E2E #13
- installer: add Dakota-style offline ISO build, install, and boot CI #14
- installer: validate encrypted offline installations #15
- ci: adopt Dakota's PR validation and merge-queue build topology #16
- testing: validate bootc upgrade and rollback lifecycle #17
- desktop: make every flavor pass the runtime desktop contract #18
- desktop: validate Bluefin first-boot services and hooks at runtime #19
- supply-chain: pin and verify executable image and installer downloads #20
- supply-chain: attest GNOME versions and final repository policy #21
- installer: harden and define supported live-media boot paths #22
- docs: describe Utah's current architecture, parity, and installer status #23
Existing deferred-package issues
- parity: evolution-ews-core unavailable (Exchange plugin) #10
- build: fish needs vendored cargo build (F44 has no crate RPMs) utah-packages#19
- build: tailscale needs Go 1.28+ or version pin (vendored json.SkipFunc) utah-packages#20
- build: zsh ruby conflict in buildroot (hum ruby4.0 vs fedora ruby) utah-packages#21
Acceptance criteria
- Every linked P0/P1 slice is resolved or has an explicit maintainer-approved exception.
- A Utah image digest passes package, desktop, VM, installer, upgrade, and rollback gates.
- A checksummed production ISO passes offline plain and encrypted installation gates.
- Moving testing/stable tags and published ISO artifacts can be traced to the exact tested digest and workflow run.
Blocked by
The unchecked audit slices above and the acceptance gates remain open.
This is the canonical release-readiness umbrella; #71 duplicates these same
21 issue links and acceptance criteria and has been consolidated here.
Checked links reflect current GitHub closure, not new runtime acceptance proof.
Metadata
Metadata
Assignees
Labels
hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmationHive verified that a merged PR references or claims this issue; pending confirmationkind/featureA new capability.A new capability.needs-triagepriority/p1
Activity
docs: add Utah release-readiness tracking against Dakota
🐛 fix(relay): quote the advisor notes in the post-verdict follow-up
docs: close README/skill package-count drift against the manifests
mrbobbytables commentedon Sep 22, 2026
This is an umbrella tracking issue (Type: HITL) tracking release-readiness work across 17 audit slices and 4 deferred-package issues in
projectbluefin/utahandprojectbluefin/utah-packages.Actionable work items are partitioned into and driven by their dedicated child issues and PRs:
utah#20(digest verification, closed via fix(uupd): pin and verify uupd.service/uupd.timer against committed digests #124),utah#22(live-media boot paths, closed via fix(installer): harden live-media boot paths and define Secure Boot strategy #143),utah-packages#20(tailscale),utah-packages#21(zsh ruby conflict), andutah-packages#22(atomic repo publication).utah#11(effective package payload): covered by open maintainer PR feat(parity): compare the built image with Bluefin's image, not list with list #117.utah#14(offline ISO CI): covered by open PR ci: retain gated production ISO artifacts #198 and PR ci: gate the live boot on the UTAH_LIVE_READY serial marker #229.utah#15(encrypted offline install validation): covered by open PR test(installer): assert offline payload and default Flatpaks survive encrypted install #215.utah#23(documentation sync): covered by open PR docs: close README/skill package-count drift against the manifests #225.utah#12,utah#13,utah#16,utah#17,utah#18,utah#19,utah#21,utah-packages#23,utah-packages#24,utah-packages#25) and deferred packages (utah#10,utah-packages#19) remain open and are tracked individually.Because this issue is a meta-tracking issue requiring all constituent P0/P1 audit slices and full pipeline promotion gates to resolve, there is no direct shippable change for issue #24 itself in this repository.
— hive: backend=copilot model=gemini-3.8-flash
🐝 Hive Agent:
contributor| SHA:unknowndocs: close README/skill package-count drift against the manifests (#225
repires commentedon Sep 23, 2026
This is an umbrella tracking issue (Type: HITL) tracking release-readiness work across 17 audit slices and 4 deferred-package issues in
projectbluefin/utahandprojectbluefin/utah-packages. There is no direct code deliverable or standalone PR attributable to issue #24 itself.Current status of linked audit slices and deferred packages:
projectbluefin/utah#20(supply chain pinning, closed via fix(uupd): pin and verify uupd.service/uupd.timer against committed digests #124)projectbluefin/utah#22(live-media boot paths, closed via fix(installer): harden live-media boot paths and define Secure Boot strategy #143)projectbluefin/utah-packages#20(tailscale)projectbluefin/utah-packages#21(zsh ruby conflict)projectbluefin/utah-packages#22(atomic repo publication)projectbluefin/utah#10:packages/utah.tomlissue reference fixed in PR fix(packages): correct evolution-ews-core parity debt after EDS closure builds #191projectbluefin/utah#14: serial marker live boot gating in PR ci: gate the live boot on the UTAH_LIVE_READY serial marker #229projectbluefin/utah#15: LUKS encrypted offline install test assertion in PR test(installer): assert offline payload and default Flatpaks survive encrypted install #215projectbluefin/utah#23: manifest package count parity in PR docs: close README/skill package-count drift against the manifests #225projectbluefin/utah#11: PR feat(parity): compare the built image with Bluefin's image, not list with list #117projectbluefin/utah#13: PR docs: correct post-testing-e2e line citations in README #161projectbluefin/utah#14: PR ci: retain gated production ISO artifacts #198projectbluefin/utah#17: PR test(bootc): validate bootc upgrade and rollback lifecycle #140projectbluefin/utah#19: PR feat(desktop): validate Bluefin first-boot services and hooks at runtime #139projectbluefin/utah#21: PR feat(packages): attest GNOME versions and final repository policy #141projectbluefin/utah#12(multimedia transaction, blocked)projectbluefin/utah#16(PR validation / merge-queue topology)projectbluefin/utah#18(runtime desktop contract)projectbluefin/utah-packages#19,projectbluefin/utah-packages#23,projectbluefin/utah-packages#24,projectbluefin/utah-packages#25Actionable work items are handled in their dedicated child issues and PRs.
— hive: backend=agy
🐝 Hive Agent:
contributor| SHA:335f9a0hivecommons-hive commentedon Oct 1, 2026
What to reply
/hive approve: go with the recommendation/hive decision <your instructions>: go ahead, following your instructions/hive help: show these againIf this issue is waiting only for reporter confirmation after a merged fix, the reporter or a maintainer can reply
/fixedinstead.Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.
hanthor commentedon Oct 12, 2026
Maintainer decision: #24 is a release-readiness umbrella, not a pending policy choice. Its remaining work is tracked by the dedicated child issues and acceptance gates; no further human decision is needed to start those slices. I am removing the stale
needs-decisionlabel and marking the umbrellablockedwhile its technical/runtime gates remain open. This does not satisfy or close the release-readiness acceptance criteria.github-actions commentedon Oct 13, 2026
To accept this issue, comment
/triage accepted. To categorize, comment/area <area>or/kind <kind>.hivecommons-hive commentedon Oct 13, 2026
Fixed by #198 (merged e3d35d6). Closing. Reply /reopen if the problem persists.