Skip to content

Update GH Actions - #1

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/gh-actions
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/gh-actions

Conversation

@renovate

@renovate renovate Bot commented Nov 19, 2025 •

Copy link
Copy Markdown

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
actions/cache action major v4 → v6
actions/checkout action major v4 → v7
actions/download-artifact action major v4 → v8
actions/upload-artifact action major v4 → v7
aws-actions/configure-aws-credentials action major v4 → v6
cachix/cachix-action action major v15 → v17
cachix/install-nix-action action major v30 → v31
crystal-lang/crystal uses-with minor 1.15.1 → 1.22.2
cygwin/cygwin-install-action action major v5 → v7
ilammy/setup-nasm action patch v1.5.1 → v1.5.2
korthout/backport-action action major v3.1.0 → v4.7.1
msys2/setup-msys2 action minor v2.26.0 → v2.33.0
mwilliamson/setup-wasmtime-action action major v2 → v3
ubuntu github-runner major 24.04 → 26.04
windows github-runner major 2022 → 2025

Release Notes

actions/cache

v6.1.0

Compare Source

What's Changed

Full Changelog: actions/cache@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v6.0.0

v5.1.0

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.1.0

v5.0.5

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.5

v5.0.4

Compare Source

What's Changed

New Contributors

Full Changelog: actions/cache@v5...v5.0.4

v5.0.3

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.3

v5.0.2: v.5.0.2

Compare Source

v5.0.2

What's Changed

When creating cache entries, 429s returned from the cache service will not be retried.

v5.0.1

Compare Source

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


v5.0.1

What's Changed

v5.0.0

What's Changed

Full Changelog: actions/cache@v5...v5.0.1

v5.0.0

Compare Source

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


What's Changed

Full Changelog: actions/cache@v4.3.0...v5.0.0

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

v5.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@v5.0.1...v5.1.0

v5.0.1

Compare Source

v5.0.0

Compare Source

actions/download-artifact

v8.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v8.0.1...v8.0.2

v8.0.1

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v8...v8.0.1

v8.0.0

Compare Source

v8 - What's new

[!IMPORTANT]
actions/download-artifact@​v8 has been migrated to an ESM module. This should be transparent to the caller but forks might need to make significant changes.

[!IMPORTANT]
Hash mismatches will now error by default. Users can override this behavior with a setting change (see below).

Direct downloads

To support direct uploads in actions/upload-artifact, the action will no longer attempt to unzip all downloaded files. Instead, the action checks the Content-Type header ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the new skip-decompress parameter to true.

Enforced checks (breaking)

A previous release introduced digest checks on the download. If a download hash didn't match the expected hash from the server, the action would log a warning. Callers can now configure the behavior on mismatch with the digest-mismatch parameter. To be secure by default, we are now defaulting the behavior to error which will fail the workflow run.

ESM

To support new versions of the @​actions/* packages, we've upgraded the package to ESM.

What's Changed

Full Changelog: actions/download-artifact@v7...v8.0.0

v7.0.0

Compare Source

v7 - What's new

[!IMPORTANT]
actions/download-artifact@​v7 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v6 had preliminary support for Node 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v6.0.0...v7.0.0

v6.0.0

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/download-artifact@v5...v6.0.0

v5.0.0

Compare Source

What's Changed
v5.0.0
🚨 Breaking Change

This release fixes an inconsistency in path behavior for single artifact downloads by ID. If you're downloading single artifacts by ID, the output path may change.

What Changed

Previously, single artifact downloads behaved differently depending on how you specified the artifact:

  • By name: name: my-artifact → extracted to path/ (direct)
  • By ID: artifact-ids: 12345 → extracted to path/my-artifact/ (nested)

Now both methods are consistent:

  • By name: name: my-artifact → extracted to path/ (unchanged)
  • By ID: artifact-ids: 12345 → extracted to path/ (fixed - now direct)
Migration Guide
✅ No Action Needed If:
  • You download artifacts by name
  • You download multiple artifacts by ID
  • You already use merge-multiple: true as a workaround
⚠️ Action Required If:

You download single artifacts by ID and your workflows expect the nested directory structure.

Before v5 (nested structure):

- uses: actions/download-artifact@v4
  with:
    artifact-ids: 12345
    path: dist

# Files were in: dist/my-artifact/

Where my-artifact is the name of the artifact you previously uploaded

To maintain old behavior (if needed):

- uses: actions/download-artifact@v5
  with:
    artifact-ids: 12345
    path: dist/my-artifact  # Explicitly specify the nested path
New Contributors

Full Changelog: actions/download-artifact@v4...v5.0.0

actions/upload-artifact

v7.0.2

Compare Source

What's Changed

  • Improves artifact download retries when the service returns HTTP 429 (rate limiting), including honoring valid Retry-After headers.
  • Updates @​actions/artifact to v6.3.1.

New Contributors

Full Changelog: actions/upload-artifact@v7.0.1...v7.0.2

v7.0.1

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v7...v7.0.1

v7.0.0

Compare Source

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v6...v7.0.0

v6.0.0

Compare Source

v6 - What's new

[!IMPORTANT]
actions/upload-artifact@​v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

v5.0.0

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/upload-artifact@v4...v5.0.0

aws-actions/configure-aws-credentials

v6.3.0

Compare Source

Features

v6.2.4

Compare Source

Bug Fixes
  • account-ids handling, mask proxy as secret in logs (#​1943) (aa65264)
  • skip backoff sleep after the final retryAndBackoff attempt (#​1937) (3852440)

v6.2.3

Compare Source

Bug Fixes

v6.2.2

Compare Source

Miscellaneous Chores

v6.2.1

Compare Source

Bug Fixes

v6.2.0

Compare Source

Features
Bug Fixes

v6.1.3

Compare Source

Bug Fixes
  • fix: allow kubelet token symlink in #​1805

v6.1.2

Compare Source

Bug Fixes

v6.1.1

Compare Source

What's Changed

Full Changelog: aws-actions/configure-aws-credentials@v6...v6.1.1

v6.1.0

Compare Source

Features

v6.0.0

Compare Source

⚠ BREAKING CHANGES
  • Update action to use node24 Note this requires GitHub action runner version v2.327.1 or later (#​1632) (a7a2c11)
Features
Bug Fixes
  • properly output aws-account-id and authenticated-arn when using role-chaining (#​1633) (7ceaf96)

v5.1.1

Compare Source

Miscellaneous Chores
  • release 5.1.1 (56d6a58)
  • various dependency updates

v5.1.0

Compare Source

Features
Bug Fixes

v5.0.0

Compare Source

⚠ BREAKING CHANGES
  • Cleanup input handling. Changes invalid boolean input behavior (see #​1445)
Features
cachix/cachix-action

v17

Compare Source

What's Changed
Breaking changes
B

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "after 5am and before 8am on Wednesday"
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/gh-actions branch from a1400f8 to 917b335 Compare November 22, 2025 08:05
@renovate
renovate Bot force-pushed the renovate/gh-actions branch 4 times, most recently from 6abd280 to ee3956b Compare December 16, 2025 08:08
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from ee3956b to 6e689d2 Compare February 6, 2026 00:13
@renovate
renovate Bot force-pushed the renovate/gh-actions branch 2 times, most recently from 87460a4 to 42312c2 Compare February 16, 2026 23:13
@renovate
renovate Bot force-pushed the renovate/gh-actions branch 2 times, most recently from 183608b to 620991c Compare March 8, 2026 11:52
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from 620991c to e21bd4f Compare March 31, 2026 09:42
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from e21bd4f to b9e91e5 Compare April 19, 2026 05:09
@renovate
renovate Bot force-pushed the renovate/gh-actions branch 2 times, most recently from 8a949db to d071750 Compare May 6, 2026 23:50
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from d071750 to 8e9a93a Compare May 11, 2026 12:03
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from 8e9a93a to 767e911 Compare June 12, 2026 15:34
@renovate
renovate Bot force-pushed the renovate/gh-actions branch 2 times, most recently from 42787b4 to dd5ecc2 Compare June 24, 2026 20:10
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from dd5ecc2 to e67f55f Compare July 1, 2026 04:40
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from e67f55f to bb6db01 Compare September 20, 2026 03:26
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from bb6db01 to 0e97d01 Compare October 2, 2026 11:45
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from 0e97d01 to e77942e Compare October 15, 2026 00:43
@renovate
renovate Bot force-pushed the renovate/gh-actions branch 2 times, most recently from 8aa4812 to e8bf2bf Compare October 27, 2026 08:11
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from e8bf2bf to f7bd4c0 Compare October 31, 2026 03:47
@renovate
renovate Bot force-pushed the renovate/gh-actions branch from f7bd4c0 to d749fc2 Compare November 7, 2026 08:06
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.

0 participants