Skip to content

chore(deps): update extractions/setup-just action to v4 - #30

Closed
mergeraptor[bot] wants to merge 3 commits into
mainfrom
renovate/extractions-setup-just-4.x
Closed

mergeraptor[bot] wants to merge 3 commits into
mainfrom
renovate/extractions-setup-just-4.x

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
extractions/setup-just action major v3 → v4

Release Notes

extractions/setup-just (extractions/setup-just)

v4.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@mergeraptor
mergeraptor Bot force-pushed the renovate/extractions-setup-just-4.x branch from c7fdccb to 0fc3e90 Compare September 2, 2026 03:21
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🛑 Fix loop escalated — human attention needed

This PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it.

Failing checks: contract

Raw failure evidence (from check-run annotations):

contract: Process completed with exit code 1.

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

sec-check[bot] and others added 2 commits September 6, 2026 02:40
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
@mergeraptor

mergeraptor Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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

Same stray packages/utah.toml hunk as #29 and #36 — needs a rebase

The PR claims one change: extractions/setup-just v3 → v4. The diff is 2 files, and the second is a package-manifest change unrelated to it:

--- a/packages/utah.toml
+++ b/packages/utah.toml
@@ -102,7 +102,10 @@ packages = [
 packages = [
     "evolution-ews-core",
+    "firefox",
     "fish",
+    "grub2-efi-x64-cdboot",
+    "pipewire-libs-extra",
     "tailscale",
     "zsh",
 ]

Byte-identical to the hunk in #29 and #36 — it comes from the stale branch base (3d1761e3), not from the update. main is at 636b48e3 and already has those three entries, but no longer lists tailscale:

$ python3 -c "import tomllib;print(tomllib.load(open('packages/utah.toml','rb'))['unavailable']['packages'])"
['evolution-ews-core', 'firefox', 'fish', 'grub2-efi-x64-cdboot', 'pipewire-libs-extra', 'zsh']

Merging as-is re-adds tailscale to [unavailable], dropping it from the image while system_files/shared/usr/share/ublue-os/privileged-setup.hooks.d/10-tailscale.sh still expects it. That is why mergeable_state is dirty. A rebase onto 636b48e3 should make the hunk disappear.

The v4 bump itself is unreviewable as presented

The release notes section in the body is empty — just a compare link for v3.1.0...v4.0.0 with no content under it. A major version with no stated breaking changes is not something to merge on faith, particularly for this action.

extractions/setup-just installs just, and just is load-bearing in this repo well beyond convenience:

  • build.yml contract job runs just check, just check-parity, just check-repos — the entire preflight gate
  • build_main / build_kernel "Preflight checks" run just syntax validation
  • the image build itself goes through just build-ghcr

Several open PRs also extend the check recipe (#40, #44, #64), so a just behaviour change lands on a moving target. Worth confirming from the v4 release what actually changed — input names, default just version, Node runtime — before bumping.

Also please confirm the digest pin and the # v3 trailing comment move together. build.yml currently has:

uses: extractions/setup-just@f8a3cce218d9f83db3a2ecd90e41ac3de6cdfd9b # v3

A new digest with a stale comment is a trap for the next reader.

Status

CI cannot confirm anything here yet — main@636b48e is red at Containerfile:81 (install: cannot create regular file '/usr/local/libexec/utah-install-packages', run 34654001732). #56 needs to land first. The contract job would be the meaningful signal for this bump specifically, since that is where just actually gets exercised.

Rebase first so the manifest hunk drops out, then this should be a small and easy merge once the v4 changes are understood.


Generated by Claude Code

@mergeraptor

mergeraptor Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@mergeraptor
mergeraptor Bot deleted the renovate/extractions-setup-just-4.x branch September 18, 2026 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant