Skip to content

ci(extensions): bump pinned GNOME extensions - #1290

Open
mergeraptor[bot] wants to merge 2 commits into
mainfrom
automation/gnome-extension-bumps
Open

mergeraptor[bot] wants to merge 2 commits into
mainfrom
automation/gnome-extension-bumps

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

GNOME extension bumps

Valid tracked-branch heads are proposed; missing or invalid metadata keeps the existing pin and does not block other extensions.
The proposal uses the repository-scoped App so normal pull-request contract and image-build CI run on its exact head.
Hive review, required checks and the normal merge policy still apply. Source metadata alone does not prove GNOME 51 runtime compatibility.

Heads

extension pinned upstream head GNOME shell-version result
system_files/shared/usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com fbc758a467d8 fbc758a467d8 — unchanged
system_files/shared/usr/share/gnome-shell/extensions/tmp/bazaar-integration@kolunmi.github.io 131388eff9d2 131388eff9d2 — unchanged
system_files/shared/usr/share/gnome-shell/extensions/blur-my-shell@aunetx 840caaa957e0 0df9022b242d 46, 47, 48, 49, 50, 51 proposed
system_files/shared/usr/share/gnome-shell/extensions/tmp/caffeine ba58454d90dd ba58454d90dd — unchanged
system_files/shared/usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com 2dfae3474d69 2dfae3474d69 — unchanged
system_files/shared/usr/share/gnome-shell/extensions/gradia-integration@alexandervanhee.github.io f79aa8239fdf f79aa8239fdf — unchanged
system_files/shared/usr/share/gnome-shell/extensions/gsconnect@andyholmes.github.io 61cc76b966f9 61cc76b966f9 — unchanged
system_files/shared/usr/share/gnome-shell/extensions/custom-command-list@storageb.github.com c6e6bdbd3bab c6e6bdbd3bab — unchanged
system_files/shared/usr/share/gnome-shell/extensions/tmp/tilingshell@ferrarodomenico.com aabe5d5806ef aabe5d5806ef — unchanged
system_files/shared/usr/share/gnome-shell/extensions/BudsLink-Companion@maniacx.github.com c11b6cf5626e f76e8665c2c6 46, 47, 48, 49, 50 skipped (invalid upstream metadata)
system_files/shared/usr/share/gnome-shell/extensions/fuzzy-application-search@mkhl.codeberg.page ab335a4542d2 6f8185b86963 48, 49, 50, 51 proposed
system_files/shared/usr/share/gnome-shell/extensions/tmp/quick-settings-audio-panel df490bff1aef df490bff1aef — unchanged
system_files/shared/usr/share/gnome-shell/extensions/tmp/quicksettings-audio-devices-hider 4db155654f1d 4db155654f1d — unchanged
system_files/shared/usr/share/gnome-shell/extensions/tmp/quicksettings-audio-devices-renamer fac597a0c0ff fac597a0c0ff — unchanged
system_files/shared/usr/share/gnome-shell/extensions/tmp/tailscale-gnome-qs 5307ed116d9b 5307ed116d9b — unchanged
system_files/shared/usr/share/gnome-shell/extensions/tmp/bluefin-bling ca24a3fd2c2b 7c615d7b8189 light-style@projectbluefin.io: 45, 46, 47, 48, 49, 50, 51; power-status-color@projectbluefin.io: 45, 46, 47, 48, 49, 50, 51; syncthing-toggle@projectbluefin.io: 45, 46, 47, 48, 49, 50, 51 proposed
system_files/shared/usr/share/gnome-shell/extensions/tmp/copyous 21ad86435b0f d31a4c7fc405 48, 49, 50, 51 proposed
system_files/shared/usr/share/gnome-shell/extensions/tmp/syncthing-toggle-rehhouari b28698d48842 b28698d48842 — unchanged

@github-actions
github-actions Bot requested review from Danathar and hanthor November 16, 2026 04:40
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danathar

The full list of commands accepted by this bot can be found here.

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 no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 16, 2026

@Danathar Danathar 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.

Stand-in review (the hive's reviewers are out of quota). Approving. All four submodule bumps are fast-forwards of their tracked branches from the current pins: blur-my-shell +20, bluefin-bling +28, copyous +31 and fuzzy-application-search +4, with nothing rewritten or behind. As the PR itself says, shell-version metadata doesn't prove GNOME 51 runtime behaviour, so the smoke suite's extension scenarios on the next image are the real check. copyous in particular has its own stress feature in the testsuite.

@github-actions github-actions Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 16, 2026
@hivecommons-hive hivecommons-hive Bot added stage/100-merge-queue Lane admitted: soaking, merge-eligible or waiting for tide / the merge window stage/stalled In its current stage longer than expected and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels 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 automated update moves four add-ons for the desktop (GNOME extensions) to newer upstream versions. Three of them really do change what gets built into the system. The fourth, the Copyous clipboard manager, does not: the system installs Copyous from a fixed, checksum-verified release file, so this bump only changes the version the build records as the Copyous source. That record now names code that is not what users get, and the Copyous fixes listed in the PR description will not reach users.

What I need from you: Decide whether to merge with the Copyous line as it is, or revert the Copyous pin on main until a matching Copyous release can be pinned with it.


correctness (medium, in-scope)

The Copyous bump is recorded but does not ship, so the build's provenance record (the file that lists which source each shipped extension came from) becomes wrong.

  • scripts/build-gnome-extensions.sh:133-139 installs Copyous from the pinned v2.1.2 release zip, checked by sha256. It never reads the tmp/copyous submodule.
  • scripts/verify-gnome-extensions.py:107-110 ("The gitlink is reference source; the verified archive is what ships") writes the submodule commit into provenance as source_commit, next to the v2.1.2 archive.
  • Upstream tag v2.1.2 resolves to 21ad86435b0f…, which is exactly the old pin (compare v2.1.2...21ad864 → identical). The new pin d31a4c7fc405 is 31 commits past it, and no newer release exists. After merge, /usr/share/utah/provenance.json would pair the source commit d31a4c7 with an archive built from 21ad864. Shell-version checks also read metadata from tmp/copyous/resources/metadata.json (verify-gnome-extensions.py:33), which is no longer the metadata that ships.
  • The PR body lists Copyous as "proposed". Its upstream range includes GNOME Shell freeze fixes (#186, #191), but none of them reach the image.

Fix on main (the bot will regenerate this PR from it): keep the Copyous gitlink at 21ad86435b0f05a0e5e576c6fbf971a1124d99d6 until upstream cuts a release, then bump the gitlink, copyous_sha256 and the release URL together. A longer-term fix is to make the bump bot skip any extension listed in ARCHIVES (verify-gnome-extensions.py:70-76), or bump it only together with its archive. Alternatively, a maintainer can accept the mismatch, because the gitlink is documented as reference only.

Other three bumps: blur-my-shell (built from source, build-gnome-extensions.sh:19-21) and bluefin-bling (upstream changed only a CI workflow file) look fine. All image builds and the contract check passed on this head (run 43805518442, head_sha 796d83e). I could not diff fuzzy-application-search, which is hosted on Codeberg. Its review relies on the passing contract check and build.

No findings from: security, intent-alignment, style, docs-currency.

Confidence: 3/5 (needs attention) — 1 medium finding; 1 perspective requires a human decision

— hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.325

@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 automated update moves four GNOME desktop add-ons (small programs that extend the desktop) to newer upstream versions. Three of them will really be built from the new version. The fourth, the Copyous clipboard manager, is listed as updated, but the system image still downloads the older release, so the record of what ships would be wrong. The newest change here only merged in work from the main branch and did not fix that.

What I need from you: Fix the Copyous issue on the main branch, either by keeping its old version pin or by updating its download to match.


Re-reviewed at head cd14b505. Changes since the last review at 796d83ed: the bot merged main into this branch (the Merge branch 'main' commit). The PR's own change is still the same four gitlink bumps. None of the merged files change how those four extensions are built, except one comment wording in scripts/build-gnome-extensions.sh:132.

Previous finding: still present.

correctness

  • The Copyous version bump is recorded but never shipped (scripts/build-gnome-extensions.sh:136). The image does not build Copyous from the tmp/copyous submodule. It downloads the fixed release zip v2.1.2/copyous@boerdereinar.dev.zip and checks it against a hard-coded sha256 (lines 133–140). Then rm -rf /usr/share/gnome-shell/extensions/tmp at line 142 deletes the submodule. The old pin 21ad86435b0f is the upstream v2.1.2 tag. The new pin d31a4c7fc405 is 31 commits after v2.1.2 and has no release. After merge, the repo would claim one Copyous version and ship a different one, and the PR table's "proposed" row for Copyous would be misleading. The fix belongs in the bump bot on main because the bot regenerates this branch. In .github/scripts/prepare-gnome-extension-bumps.py prepare() (around line 102), skip submodules whose shipped artifact is a pinned release:

    RELEASE_PINNED = {"system_files/shared/usr/share/gnome-shell/extensions/tmp/copyous"}
    ...
        for name, path in submodules(root):
            if path in RELEASE_PINNED:
                pinned = run_git(root, "-C", path, "rev-parse", "HEAD").stdout.strip()
                bumps.append(Bump(path, pinned, pinned, "—", "skipped (shipped from pinned release zip)"))
                continue

    The other option is to update the release URL and sha256 in build-gnome-extensions.sh whenever the gitlink moves. That only works once upstream tags a release that matches the new head. The next bot run will then drop the Copyous gitlink from this PR, and the other three bumps can land.

No findings from: security, intent-alignment, style, docs-currency.

Confidence: 3/5 (needs attention) — 1 medium finding; 1 perspective requested changes

— hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.325

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

@hanthor hanthor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maintainer decision on the Copyous question: don't accept the mismatch. Copyous ships from the pinned v2.1.2 zip, so moving its gitlink to d31a4c7 makes provenance.json name source that isn't what ships. The other three bumps (blur-my-shell, fuzzy-application-search, bluefin-bling) are fine.

Fix on main, not here, since the bot regenerates this branch: make .github/scripts/prepare-gnome-extension-bumps.py skip extensions that ship from a pinned archive (the ARCHIVES set in verify-gnome-extensions.py), or bump them only together with their URL and sha256. The next bot run then drops Copyous from this PR and the rest can land. (#1296 removes the Copyous submodule anyway when the RPM extensions land.)

Reviewed on behalf of @hanthor with Claude Code

@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/100-merge-queue Lane admitted: soaking, merge-eligible or waiting for tide / the merge window 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 100-merge-queue → 070-fixing: human-changes-requested

@hivecommons-hive hivecommons-hive Bot added stage/stalled In its current stage longer than expected and removed stage/stalled In its current stage longer than expected labels Nov 18, 2026
@hanthor

hanthor commented Nov 19, 2026

Copy link
Copy Markdown
Member

The main-side fix is #1344 (archive-shipped extensions are never bumped alone). Once it lands, the next bot run drops Copyous from this PR.

@hivecommons-hive hivecommons-hive Bot added stage/stalled In its current stage longer than expected and removed stage/stalled In its current stage longer than expected labels Nov 19, 2026
@hivecommons-hive hivecommons-hive Bot added stage/stalled In its current stage longer than expected and removed stage/stalled In its current stage longer than expected labels Nov 19, 2026
@hanthor

hanthor commented Nov 20, 2026

Copy link
Copy Markdown
Member

Heads-up: #1358 (closes #1235) removes the tmp/copyous submodule (and tmp/quick-settings-audio-panel) and repins tmp/bluefin-bling to Dakota's f43fc6d. This PR bumps both tmp/copyous and tmp/bluefin-bling, so it will conflict once #1358 lands. The extension-bump automation should regenerate it from the new main; the Copyous bump should then disappear.

@hivecommons-hive hivecommons-hive Bot added stage/stalled In its current stage longer than expected and removed stage/stalled In its current stage longer than expected labels Nov 20, 2026

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

approved Indicates a PR has been approved by an approver from all required OWNERS files. no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/stalled In its current stage longer than expected stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants