Skip to content

chore(deps): update actions/checkout action to v7 - #29

Closed
mergeraptor[bot] wants to merge 3 commits into
mainfrom
renovate/actions-checkout-7.x
Closed

mergeraptor[bot] wants to merge 3 commits into
mainfrom
renovate/actions-checkout-7.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
actions/checkout action major v5 → v7

Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

  • Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
  • Various dependency updates

v6.1.0

Compare Source

What's Changed

https://github.blog/changelog/2026-06-18-safer-pull_request_target-defaults-for-github-actions-checkout/ for more details about this breaking change

Full Changelog: actions/checkout@v6.0.3...v6.1.0

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.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/actions-checkout-7.x branch from 2eee735 to f8a0a57 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: Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners
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 #30 and #36 — needs a rebase

The PR claims one thing: actions/checkout v5 → v7. The diff is 4 files and includes a package-manifest change that has nothing to do with 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 #30 and #36, which is the tell that it comes from the stale branch base (3d1761e3) rather than from the update. main is now at 636b48e3 and already contains those three entries — but has dropped 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 would put tailscale back into [unavailable], dropping it from the image while system_files/shared/usr/share/ublue-os/privileged-setup.hooks.d/10-tailscale.sh still expects it. mergeable_state is dirty for this reason — it conflicts and cannot merge without a rebase. After rebasing onto 636b48e3 the hunk should disappear entirely.

The v5 → v7 jump needs a closer look than a normal bump

This is not a routine major. Two entries in the changelog quoted in the PR body are directly relevant to this repository:

v7.0.0 — "Block checking out fork PR for pull_request_target and workflow_run".
v6.1.0 — "[BREAKING] backport allow-unsafe-pr-checkout to v6".

.github/workflows/post-testing-e2e.yml is triggered by workflow_run:

on:
  workflow_run:
    workflows: ["Build Utah"]
    types: [completed]
    branches: [testing]

It has no checkout step on main today, so nothing breaks right now. But #64 adds one to that exact job:

- name: Checkout
  uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5
- name: Resolve the expected image count
  run: echo "count=$(python3 scripts/flavors.py count)" >> "$GITHUB_OUTPUT"

So if #64 lands and then this bump lands, that checkout runs under v7's new workflow_run restrictions. Worth confirming the interaction before merging either — and worth deciding the order deliberately rather than by whichever is ready first. (I've separately noted on #64 that its bare checkout resolves to the default branch rather than workflow_run.head_sha, which wants fixing regardless.)

Beyond the version pin, please confirm the corresponding SHA pins are updated consistently — this repo pins by digest with a # v5 comment, and a stale comment next to a new digest is worse than either alone.

Status

CI cannot validate this yet: main@636b48e is itself red at Containerfile:81 (install: cannot create regular file '/usr/local/libexec/utah-install-packages', run 34654001732). #56 needs to land first.

Suggested order: rebase this onto current main so the manifest hunk drops out, then decide the #64 interaction, then merge.


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 7.x releases. But if you manually upgrade to 7.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/actions-checkout-7.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