Skip to content

chore(deps): update actions (major)#2

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-actions
Open

chore(deps): update actions (major)#2
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-actions

Conversation

@renovate

@renovate renovate Bot commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v4v7
actions/download-artifact action major v4v8
actions/setup-node action major v4v7
docker/build-push-action action major v5v7
docker/build-push-action action major v6v7
docker/login-action action major v3v4
docker/metadata-action action major v5v6
docker/setup-buildx-action action major v3v4

Release Notes

actions/checkout (actions/checkout)

v7.0.0

Compare Source

v7

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v6

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

v5

Compare Source

actions/download-artifact (actions/download-artifact)

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

v8

Compare Source

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

v7

Compare Source

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

v6

Compare Source

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

v5

Compare Source

actions/setup-node (actions/setup-node)

v7.0.0

Compare Source

v7

Compare Source

v6.5.0

Compare Source

v6.4.0

Compare Source

What's Changed

Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v6...v6.4.0

v6.3.0

Compare Source

What's Changed

Enhancements:

When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node.

Dependency updates:
Bug fixes:

New Contributors

Full Changelog: actions/setup-node@v6...v6.3.0

v6.2.0

Compare Source

What's Changed

Documentation
Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v6...v6.2.0

v6.1.0

Compare Source

What's Changed

Enhancement:
Dependency updates:
Documentation update:

Full Changelog: actions/setup-node@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Breaking Changes

Dependency Upgrades

Full Changelog: actions/setup-node@v5...v6.0.0

v6

Compare Source

v5.0.0

Compare Source

What's Changed

Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless.
To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
  with:
    package-manager-cache: false

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Dependency Upgrades

New Contributors

Full Changelog: actions/setup-node@v4...v5.0.0

v5

Compare Source

docker/build-push-action (docker/build-push-action)

v7.3.0

Compare Source

v7.2.0

Compare Source

Full Changelog: docker/build-push-action@v7.1.0...v7.2.0

v7.1.0

Compare Source

Full Changelog: docker/build-push-action@v7.0.0...v7.1.0

v7.0.0

Compare Source

Full Changelog: docker/build-push-action@v6.19.2...v7.0.0

v7

Compare Source

v6.19.2

Compare Source

Full Changelog: docker/build-push-action@v6.19.1...v6.19.2

v6.19.1

Compare Source

Full Changelog: docker/build-push-action@v6.19.0...v6.19.1

v6.19.0

Compare Source

  • Scope default git auth token to github.com by @​crazy-max in #​1451
  • Bump brace-expansion from 1.1.11 to 1.1.12 in #​1396
  • Bump form-data from 2.5.1 to 2.5.5 in #​1391
  • Bump js-yaml from 3.14.1 to 3.14.2 in #​1429
  • Bump lodash from 4.17.21 to 4.17.23 in #​1446
  • Bump tmp from 0.2.3 to 0.2.4 in #​1398
  • Bump undici from 5.28.4 to 5.29.0 in #​1397

Full Changelog: docker/build-push-action@v6.18.0...v6.19.0

v6.18.0

Compare Source

[!NOTE]
Build summary is now supported with Docker Build Cloud.

Full Changelog: docker/build-push-action@v6.17.0...v6.18.0

v6.17.0

Compare Source

[!NOTE]
Build record is now exported using the buildx history export command instead of the legacy export-build tool.

Full Changelog: docker/build-push-action@v6.16.0...v6.17.0

v6.16.0

Compare Source

Full Changelog: docker/build-push-action@v6.15.0...v6.16.0

v6.15.0

Compare Source

Full Changelog: docker/build-push-action@v6.14.0...v6.15.0

v6.14.0

Compare Source

Full Changelog: docker/build-push-action@v6.13.0...v6.14.0

v6.13.0

Compare Source

Full Changelog: docker/build-push-action@v6.12.0...v6.13.0

v6.12.0

Compare Source

Full Changelog: docker/build-push-action@v6.11.0...v6.12.0

v6.11.0

Compare Source

Full Changelog: docker/build-push-action@v6.10.0...v6.11.0

v6.10.0

Compare Source

Full Changelog: docker/build-push-action@v6.9.0...v6.10.0

v6.9.0

Compare Source

Full Changelog: docker/build-push-action@v6.8.0...v6.9.0

v6.8.0

Compare Source

Full Changelog: docker/build-push-action@v6.7.0...v6.8.0

v6.7.0

Compare Source

Full Changelog: docker/build-push-action@v6.6.1...v6.7.0

v6.6.1

Compare Source

Full Changelog: docker/build-push-action@v6.6.0...v6.6.1

v6.6.0

Compare Source

Full Changelog: docker/build-push-action@v6.5.0...v6.6.0

v6.5.0

Compare Source

Full Changelog: docker/build-push-action@v6.4.1...v6.5.0

v6.4.1

Compare Source

Full Changelog: docker/build-push-action@v6.4.0...v6.4.1

v6.4.0

Compare Source

Full Changelog: docker/build-push-action@v6.3.0...v6.4.0

v6.3.0

Compare Source

Full Changelog: docker/build-push-action@v6.2.0...v6.3.0

v6.2.0

Compare Source

Full Changelog: docker/build-push-action@v6.1.0...v6.2.0

v6.1.0

Compare Source

Full Changelog: docker/build-push-action@v6.0.2...v6.1.0

v6.0.2

Compare Source

Full Changelog: docker/build-push-action@v6.0.1...v6.0.2

v6.0.1

Compare Source

Full Changelog: docker/build-push-action@v6.0.0...v6.0.1

v6.0.0

Compare Source

[!NOTE]
This major release adds support for generating Build summary and exporting build record for your build. You can disable this feature by setting DOCKER_BUILD_SUMMARY: false environment variable in your workflow.

Full Changelog: docker/build-push-action@v5.4.0...v6.0.0

v6

Compare Source

docker/login-action (docker/login-action)

v4.4.0

Compare Source

v4.3.0

Compare Source

Full Changelog: docker/login-action@v4.2.0...v4.3.0

v4.2.0

Compare Source

Full Changelog: docker/login-action@v4.1.0...v4.2.0

v4.1.0

Compare Source

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every 4th week on Thursday before 10am"
  • 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/major-actions branch 2 times, most recently from 64c61a7 to 567d5d3 Compare February 3, 2026 19:54
@renovate
renovate Bot force-pushed the renovate/major-actions branch from 567d5d3 to bd97b55 Compare February 13, 2026 07:43
@jvansanten
jvansanten force-pushed the main branch 4 times, most recently from 95d5d94 to 0f2a772 Compare February 16, 2026 16:27
@renovate renovate Bot changed the title chore(deps): update actions to v6 (major) chore(deps): update actions (major) Feb 19, 2026
@renovate
renovate Bot force-pushed the renovate/major-actions branch 2 times, most recently from ee73e49 to 541e9ef Compare February 26, 2026 07:07
@renovate
renovate Bot force-pushed the renovate/major-actions branch 4 times, most recently from 2fafca8 to 2469850 Compare March 5, 2026 08:47
@renovate
renovate Bot force-pushed the renovate/major-actions branch 3 times, most recently from d89c02f to 796f613 Compare March 11, 2026 17:42
@renovate
renovate Bot force-pushed the renovate/major-actions branch from 796f613 to 3fcf766 Compare March 26, 2026 17:13
@renovate
renovate Bot force-pushed the renovate/major-actions branch from 3fcf766 to d45a651 Compare April 2, 2026 18:29
@renovate
renovate Bot force-pushed the renovate/major-actions branch from d45a651 to ce9f952 Compare April 10, 2026 14:07
@renovate
renovate Bot force-pushed the renovate/major-actions branch 2 times, most recently from de352d7 to 569830c Compare April 21, 2026 17:05
@renovate
renovate Bot force-pushed the renovate/major-actions branch from 569830c to 8fb1932 Compare April 29, 2026 09:42
@renovate
renovate Bot force-pushed the renovate/major-actions branch from 8fb1932 to 4ce4d55 Compare May 12, 2026 15:11
@renovate
renovate Bot force-pushed the renovate/major-actions branch 3 times, most recently from c16cf26 to a5e7c8a Compare May 22, 2026 20:42
@renovate
renovate Bot force-pushed the renovate/major-actions branch from a5e7c8a to 64ab2dd Compare June 2, 2026 16:09
@renovate
renovate Bot force-pushed the renovate/major-actions branch from 64ab2dd to e22c1cc Compare June 18, 2026 19:16
@renovate
renovate Bot force-pushed the renovate/major-actions branch 3 times, most recently from c220714 to 4f0e0f6 Compare July 3, 2026 16:47
@renovate
renovate Bot force-pushed the renovate/major-actions branch from 4f0e0f6 to 1d0c91d Compare July 14, 2026 06:03
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