You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Refresh extension pins to upstream fixes without breaking GNOME 51 #993
Utah has 16 GNOME extension submodule trees and the source verifier checks 18 extension metadata records for GNOME 51. The upstream-main audit found these gaps: Blur my Shell was pinned to v76 (f019cd1f) while upstream master is v77 (b973ec8f); Bluefin Bling was pinned to f9e68e20 while its main branch is d357a1e1. This change updates both pins.
Other checked refs are current: AppIndicator v66-6, Dash to Dock v110, GSConnect v74, and the remaining branch pins match their configured upstream heads. Fuzzy Application Search uses upstream HEAD, which matches its pin. BudsLink upstream tip f76e866 removes the extension source and metadata (leaving only README.md), so Utah retains the last source-bearing pin c11b6cf rather than adopting a broken extension tree.
The updated source contract passes all 18 GNOME 51 metadata checks. Runtime compatibility still requires a booted image.
changed the title [-]Refresh stale GNOME extension pins and verify GNOME 51 compatibility[/-][+]Refresh extension pins to upstream fixes without breaking GNOME 51[/+]on Oct 28, 2026
Audit/update is in local commit 2404c01: Blur My Shell to upstream master v77, Bluefin Bling to its current main head. BudsLink remains on the last source-bearing commit because its latest branch tip deletes the extension and makes the GNOME source contract fail. GNOME source verification passes all 18 metadata records; full just check and pre-commit pass. The local branch is not pushed or merged.
Update: PR #998 contains the refreshed Blur my Shell and Bluefin Bling pins plus the documented BudsLink exception. CI is pending; keep this issue open until merge.
Prepared in local branch fix/blur-my-shell-latest-fixes, commit 71ca681 (not pushed or deployed). Blur my Shell moved to upstream v77; Bluefin Bling moved to its current upstream head; BudsLink remains at its last source-bearing commit because the upstream head removes its implementation. GNOME 51 metadata verification and required repository checks pass. Package-build smoke against the GNOME 51.1 host could not connect over SSH; this issue remains open pending PR/image validation.
Update: PR #998 is open with the extension pin refresh, rebased onto current main at cc55708a909cfe21c3c69ec67ef7544c8e3d3bae. Local required checks passed; remote contract check is pending. This remains open until the PR merges.
Follow-up: PR #1001 changes the extension bump workflow so a head with missing or invalid metadata (such as BudsLink upstream) keeps the existing gitlink, appears as skipped in the report, and does not block other valid bumps. This does not change the current BudsLink pin. PR #1001 is open; its contract check is pending.
@hanthor this looks done: #998 merged on 2026-10-29 with both extension pin refreshes, which is the condition this issue gave for closing. OK to close it? The remaining CPU/rendering question is tracked in #997.
Activity
github-actions commentedon Oct 28, 2026
To accept this issue, comment
/triage accepted. To categorize, comment/area <area>or/kind <kind>.hanthor commentedon Oct 28, 2026
/kind cleanup
[-]Refresh stale GNOME extension pins and verify GNOME 51 compatibility[/-][+]Refresh extension pins to upstream fixes without breaking GNOME 51[/+]hanthor commentedon Oct 28, 2026
Audit/update is in local commit
2404c01: Blur My Shell to upstream master v77, Bluefin Bling to its current main head. BudsLink remains on the last source-bearing commit because its latest branch tip deletes the extension and makes the GNOME source contract fail. GNOME source verification passes all 18 metadata records; fulljust checkand pre-commit pass. The local branch is not pushed or merged.hanthor commentedon Oct 28, 2026
Update: PR #998 contains the refreshed Blur my Shell and Bluefin Bling pins plus the documented BudsLink exception. CI is pending; keep this issue open until merge.
hanthor commentedon Oct 28, 2026
Prepared in local branch
fix/blur-my-shell-latest-fixes, commit71ca681(not pushed or deployed). Blur my Shell moved to upstream v77; Bluefin Bling moved to its current upstream head; BudsLink remains at its last source-bearing commit because the upstream head removes its implementation. GNOME 51 metadata verification and required repository checks pass. Package-build smoke against the GNOME 51.1 host could not connect over SSH; this issue remains open pending PR/image validation.hanthor commentedon Oct 28, 2026
Update: PR #998 is open with the extension pin refresh, rebased onto current main at
cc55708a909cfe21c3c69ec67ef7544c8e3d3bae. Local required checks passed; remotecontractcheck is pending. This remains open until the PR merges.hanthor commentedon Oct 28, 2026
Follow-up: PR #1001 changes the extension bump workflow so a head with missing or invalid metadata (such as BudsLink upstream) keeps the existing gitlink, appears as skipped in the report, and does not block other valid bumps. This does not change the current BudsLink pin. PR #1001 is open; its contract check is pending.
Danathar commentedon Nov 5, 2026
@hanthor this looks done: #998 merged on 2026-10-29 with both extension pin refreshes, which is the condition this issue gave for closing. OK to close it? The remaining CPU/rendering question is tracked in #997.
hanthor commentedon Nov 7, 2026
Resolved by #998 (merged 10-29), which refreshed the extension pins to the upstream fixes.