Repository navigation
Closed as not planned
Description
- 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
- 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
created_date: "2026-09-24"
document_status: draft
closed_date: nullFeature: 20260924190738-28eb0070-utah-release-readiness
Overview
Utah reaches releasable image and ISO quality with independently traceable package, desktop, upgrade and recovery evidence while preserving its Hummingbird bootc/RPM design. The linked Utah and Utah-packages issues remain the concrete audit slices rather than a second hidden backlog. Source: utah#71.
Requirements
- Resolve linked release blockers
Every linked P0/P1 Utah and Utah-packages slice is resolved or has an explicit maintainer-approved exception. - Gate the image on real behavior
One immutable Utah image digest passes package, desktop, VM, installer, upgrade and rollback checks. - Prove offline installation
A checksummed production ISO completes offline plain and encrypted installs. - Trace publication
Testing/stable tags and ISO releases resolve to the exact tested image digest and originating workflow run.
Constraints
- Utah retains Hummingbird bootc/RPM architecture; Dakota is reference for evidence/promotion practices, not a mandated stack change.
- The source body contains literal escaped newlines; preserve and normalize all 21 task-list links when rewriting the issue.
- Do not claim a linked issue completed merely because a label or old tracker text changed.
Acceptance Criteria
- Resolve linked release blockers
Each of the 21 linked issue URLs is accounted for as closed with evidence or an approved, documented exception. - Gate the image on real behavior
Test results name the same digest and show each required lane completed. - Prove offline installation
Both installation variants boot from the published ISO and match its published checksum. - Trace publication
A reviewer follows image digest and workflow identity from passing gates through published tags and ISO artifacts.
Technical Approach
- Audit slices: utah-packages#22–chore(deps): update ghcr.io/projectbluefin/common docker digest to 0f58c6d #25, desktop: validate Bluefin first-boot services and hooks at runtime #19–supply-chain: attest GNOME versions and final repository policy #21 and utah#10–docs: describe Utah's current architecture, parity, and installer status #23 (21 URLs in the original); link their exact issue URLs at the top of the rewritten body.
- Keep the existing Hive Agent attribution as issue metadata; do not interpret the literal escaped formatting as missing tasks.
Success Metrics
- One tested digest can be traced across image, ISO and publication gates without inconsistent source refs.
Non-Goals
- No replatform to Dakota BuildStream, unapproved exception or placeholder release proof.
[You have received this identical output 5 times. Re-reading 'specs/speks/20260924190738-28eb0070-utah-release-readiness.md:raw' will not change it — use a narrower selector (path:A-B), or proceed with the edit.]
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- StatusShow more project fieldsDone
Activity
mendezr commentedon Sep 21, 2026
This is a tracking/umbrella issue: every acceptance criterion is the resolution of a linked sub-issue, which are tracked and worked individually across repo projectbluefin/utah and projectbluefin/utah-packages. There is no independent code deliverable attributable to issue #71 itself, so there is no PR to open against this issue. The actionable work lives in the sub-issues it links (utah #10–#23; utah-packages #19–#25), the large majority of which remain OPEN.
Closed so far: utah #20, #22; utah-packages #20, #21, #22. Remaining open work must land via those sub-issues, not this tracking issue.
— hive: backend=goose model=deepseek/deepseek-v4-flash-0731
🐝 Hive Agent:
contributor| SHA:636b48erepires commentedon Sep 22, 2026
This is an umbrella tracking issue for Utah release-readiness against Dakota. Every acceptance criterion is tracked through dedicated child issues and PRs across
projectbluefin/utahandprojectbluefin/utah-packages. There is no direct code deliverable or standalone PR attributable to issue #71 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,projectbluefin/utah#16,projectbluefin/utah#18projectbluefin/utah-packages#19,projectbluefin/utah-packages#23,projectbluefin/utah-packages#24,projectbluefin/utah-packages#25Actionable work is handled in these individual child issues and PRs rather than on this tracking issue.
— hive: backend=agy
🐝 Hive Agent:
contributor| SHA:unknownhivecommons-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 6, 2026
Consolidated into #24: both umbrellas contain the same 21 linked audit slices and release acceptance criteria. #24 now has refreshed linked-issue checkboxes and remains open for the image/VM/installer/lifecycle/publication gates. This closes only the duplicate tracker, not any child issue or runtime acceptance requirement.