Update dorny/paths-filter action to v4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
dorny/paths-filter	action	major	v3 → v4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

dorny/paths-filter (dorny/paths-filter)

v4

Compare Source

• Update action runtime to node24

---

Configuration

📅 Schedule: Branch creation - "after 2am and before 8am on monday" in timezone America/New_York, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[github-actions]

dorny/paths-filter v3 -> v4

Risk: 🟢 Safe | CI: failing | Confidence: high

The Deep Dive

Update Scope

Single package update: dorny/paths-filter from v3 (de90cc6fb38fc0963ad72b210f1f284cd68cea36) to v4 (fbd0ab8f3e69293af611ebaee6363fc25e6d187d). The change is applied across 6 GitHub Actions workflow files, each a one-line pin update.

The v4 tag and v4.0.1 tag both resolve to the same commit SHA (fbd0ab8f3e69293af611ebaee6363fc25e6d187d), so this PR includes all v4.x changes to date.

Performance & Stability

No performance or stability changes. The v4.0.0 release is purely a runtime update with no functional changes to the action's behavior.

Features & UX

• Merge queue support (pull/255): Adds automatic base/ref detection for merge_group events, eliminating false-positive path detection when multiple PRs are queued. This repo does not currently use merge queues (no merge_group triggers found in any workflow), so this has no immediate effect but is available if merge queues are adopted later.

Security

No CVEs or security advisories found for dorny/paths-filter in this version range. The Node.js runtime update from Node 20 to Node 24 is itself a security improvement, as Node 20 reaches EOL in April 2026.

Key Fixes

• Node 24 runtime (pull/294): Updates the action runtime from node20 to node24. GitHub is deprecating Node 20 runners with Node 24 becoming default on June 2, 2026. No functional changes — all inputs, outputs, and behavior remain identical.

Newer Versions

The v4 major tag currently points to v4.0.1 (fbd0ab8f3e69293af611ebaee6363fc25e6d187d), which is the same commit SHA used in this PR. There are no newer versions beyond what this PR proposes.

Hazards & Risks

None identified. The v3-to-v4 change is a Node runtime bump (20→24) with no breaking changes to the action's API, inputs, outputs, or behavior. The merge queue feature is additive and only activates for merge_group events, which this repo does not use.

CI note: The rpi-image-test job fails, but this is unrelated to paths-filter. The failure occurs in QEMU RPi emulation (qemu-system-aarch64 errors). The test was triggered because the workflow file .github/workflows/rpi-image-test.yaml itself changed (the paths-filter pin update), causing paths-filter to correctly detect the change and run the RPi test. This test passes on main and the failure appears to be a flaky infrastructure issue with the ARM QEMU emulator.

Sources

• v4.0.0 release notes
• v4.0.1 release notes
• Update action runtime to node24 (PR)
• Support merge queue (PR)
• v3...v4 comparison

---

🟢 Verdict: Safe

Runtime-only update from Node 20 to Node 24 with no functional changes. Proactively addresses the upcoming Node 20 deprecation on GitHub Actions runners (June 2026). The rpi-image-test CI failure is unrelated to this change.