build(deps): bump the dependencies group across 1 directory with 10 updates

[dependabot]

Bumps the dependencies group with 10 updates in the / directory:

Package	From	To
hendrikmuhs/ccache-action	1.2.20	1.2.21
github/codeql-action	4.32.3	4.33.0
anchore/sbom-action	0.22.2	0.23.1
actions/attest-build-provenance	3.2.0	4.1.0
actions/upload-artifact	6.0.0	7.0.0
release-drafter/release-drafter	6.2.0	7.1.1
cpp-linter/cpp-linter-action	2.16.7	2.17.0
astral-sh/setup-uv	7.3.0	7.6.0
actions/download-artifact	7.0.0	8.0.1
softprops/action-gh-release	2.5.0	2.6.1

Updates hendrikmuhs/ccache-action from 1.2.20 to 1.2.21

Release notes

Sourced from hendrikmuhs/ccache-action's releases.

v1.2.21

What's Changed

• Bump actions/checkout from 5 to 6 by @​dependabot[bot] in hendrikmuhs/ccache-action#396
• Bump @​types/node from 24.10.0 to 25.2.2 by @​dependabot[bot] in hendrikmuhs/ccache-action#417
• Bump @​actions/cache from 4.1.0 to 6.0.0 by @​dependabot[bot] in hendrikmuhs/ccache-action#412
• Bump @​actions/core from 1.11.1 to 3.0.0 by @​dependabot[bot] in hendrikmuhs/ccache-action#413
• Bump @​actions/exec from 1.1.1 to 3.0.0 by @​dependabot[bot] in hendrikmuhs/ccache-action#414
• Bump @​actions/io from 2.0.0 to 3.0.2 by @​dependabot[bot] in hendrikmuhs/ccache-action#416
• refactor: add Windows ARM and macOS binaries, use a single Package class, deduplicate some common install code by @​crueter in hendrikmuhs/ccache-action#403
• Bump @​types/node from 25.2.2 to 25.3.3 by @​dependabot[bot] in hendrikmuhs/ccache-action#421
• Bump jest from 30.2.0 to 30.3.0 by @​dependabot[bot] in hendrikmuhs/ccache-action#431
• Upgrade Node.js version from 20 to 24 by @​janisozaur in hendrikmuhs/ccache-action#427
• Bump @​types/node from 25.3.3 to 25.5.0 by @​dependabot[bot] in hendrikmuhs/ccache-action#430
• refactor: generate metadata json file by @​crueter in hendrikmuhs/ccache-action#422
• tests: add install matrix by @​crueter in hendrikmuhs/ccache-action#423
• Bump undici from 6.23.0 to 6.24.1 by @​dependabot[bot] in hendrikmuhs/ccache-action#429

New Contributors

• @​crueter made their first contribution in hendrikmuhs/ccache-action#403

Full Changelog: hendrikmuhs/ccache-action@v1.2...v1.2.21

Commits

• 1bbbcda update code
• ad1528e Bump undici from 6.23.0 to 6.24.1 (#429)
• b13e06b tests: add install matrix (#423)
• db942ad refactor: generate metadata json file (#422)
• 4f5619a Bump @​types/node from 25.3.3 to 25.5.0 (#430)
• cbca54b Upgrade Node.js version from 20 to 24 (#427)
• 4a6e0f0 Bump jest from 30.2.0 to 30.3.0 (#431)
• c56d71a Bump @​types/node from 25.2.2 to 25.3.3 (#421)
• ac5cc34 refactor: add Windows ARM and macOS binaries, use a single Package class, ded...
• a846541 fix tests
• Additional commits viewable in compare view

Updates github/codeql-action from 4.32.3 to 4.33.0

Release notes

Sourced from github/codeql-action's releases.

v4.33.0

• Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562

  To opt out of this change:

  • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.

• Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557

• The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #3559

• Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563

• Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564

• A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #3570

v4.32.6

• Update default CodeQL bundle version to 2.24.3. #3548

v4.32.5

• Repositories owned by an organization can now set up the github-codeql-disable-overlay custom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the name github-codeql-disable-overlay and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to true to disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #3507
• Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #3487
• The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #3515
• Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #3516
• Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #3498
• Added an experimental change which allows the start-proxy action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #3512
• The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #3503, #3504

v4.32.4

• Update default CodeQL bundle version to 2.24.2. #3493
• Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when private package registries are configured. This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. #3473
• When the CodeQL Action is run with debugging enabled in Default Setup and private package registries are configured, the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. #3486
• Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. #3485
• Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a nightly CodeQL CLI release instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. #3484

Changelog

Sourced from github/codeql-action's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

• Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #3569
• We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #3584
• Update default CodeQL bundle version to 2.25.0. #3585

4.33.0 - 16 Mar 2026

• Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562

  To opt out of this change:

  • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.

• Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557

• The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #3559

• Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563

• Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564

• A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #3570

4.32.6 - 05 Mar 2026

• Update default CodeQL bundle version to 2.24.3. #3548

4.32.5 - 02 Mar 2026

• Repositories owned by an organization can now set up the github-codeql-disable-overlay custom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the name github-codeql-disable-overlay and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to true to disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #3507
• Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #3487
• The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #3515
• Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #3516
• Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #3498
• Added an experimental change which allows the start-proxy action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #3512
• The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #3503, #3504

4.32.4 - 20 Feb 2026

• Update default CodeQL bundle version to 2.24.2. #3493
• Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when private package registries are configured. This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. #3473
• When the CodeQL Action is run with debugging enabled in Default Setup and private package registries are configured, the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. #3486
• Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. #3485
• Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a nightly CodeQL CLI release instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. #3484

4.32.3 - 13 Feb 2026

• Added experimental support for testing connections to private package registries. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for Default Setup. #3466

... (truncated)

Commits

• b1bff81 Merge pull request #3574 from github/update-v4.32.7-7dd76e6bf
• e682234 Add changelog entry for #3570
• 95be291 Bump minor version
• 59bcb60 Update changelog for v4.32.7
• 7dd76e6 Merge pull request #3572 from github/mbg/pr-checks/eslint
• e3200e3 Merge pull request #3563 from github/mbg/private-registry/oidc
• 4c356c7 Merge pull request #3570 from github/mbg/repo-props/warn-on-unexpected-props
• b4937c1 Only emit one message with accumulated property names
• 136b8ab Remove cache-dependency-path options as well
• a5aba59 Remove package-lock.json that's no longer needed
• Additional commits viewable in compare view

Updates anchore/sbom-action from 0.22.2 to 0.23.1

Release notes

Sourced from anchore/sbom-action's releases.

v0.23.1

⬆️ Dependencies

• chore(deps): update Syft to v1.42.2 (#607) [@anchore-actions-token-generator[bot]]
• chore(deps): bump fast-xml-parser and all other deps (#604) [@dependabot[bot]]

v0.23.0

• switch to single-file dist build with sub-action flags and update dependencies (#595) [@​kzantow]
• switch to esbuild (#590) [@​willmurphyscode]
• update Syft to v1.42.1 (#599) [@anchore-actions-token-generator[bot]]

Commits

• 57aae52 chore(deps): update Syft to v1.42.2 (#607)
• c29e913 chore(deps): bump fast-xml-parser and other deps (#604)
• 17ae174 chore(deps/test): move to es modules, node:test, single dist file (#595)
• 6d473d3 chore(deps): update Syft to v1.42.1 (#599)
• 60619e7 fix tests and bump fast-xml-parser (#598)
• e2bd58a chore(deps-dev): bump the dev-dependencies group with 3 updates (#592)
• d032d7d ci(syft auto update): npm ci, not npm install (#597)
• 2d09430 fix(dev): switch to esbuild (#590)
• 74c5ce9 chore(deps): update Syft to v1.42.0 (#589)
• 77fae5a chore(deps-dev): bump the dev-dependencies group with 4 updates (#583)
• Additional commits viewable in compare view

Updates actions/attest-build-provenance from 3.2.0 to 4.1.0

Release notes

Sourced from actions/attest-build-provenance's releases.

v4.1.0

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

• Update RELEASE.md docs by @​bdehamer in actions/attest-build-provenance#836
• Bump actions/attest from 4.0.0 to 4.1.0 by @​bdehamer in actions/attest-build-provenance#838
  • Bump @actions/attest from 3.0.0 to 3.1.0 by @​bdehamer in actions/attest#362
  • Bump @actions/attest from 3.1.0 to 3.2.0 by @​bdehamer in actions/attest#365
  • Add new subject-version input for inclusion in storage record by @​bdehamer in actions/attest#364
  • Add storage record content to README by @​bdehamer in actions/attest#366

Full Changelog: actions/attest-build-provenance@v4.0.0...v4.1.0

v4.0.0

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

• Prepare v4 release by @​bdehamer in actions/attest-build-provenance#835

Full Changelog: actions/attest-build-provenance@v3.2.0...v4.0.0

Commits

• a2bbfa2 bump actions/attest from 4.0.0 to 4.1.0 (#838)
• 0856891 update RELEASE.md docs (#836)
• e4d4f7c prepare v4 release (#835)
• 02a49bd Bump github/codeql-action in the actions-minor group (#824)
• 7c757df Bump the npm-development group with 2 updates (#825)
• c44148e Bump github/codeql-action in the actions-minor group (#818)
• 3234352 Bump @​types/node from 25.0.10 to 25.2.0 in the npm-development group (#819)
• 18db129 Bump tar from 7.5.6 to 7.5.7 (#816)
• 90fadfa Bump @​actions/core from 2.0.1 to 2.0.2 in the npm-production group (#799)
• 57db8ba Bump the npm-development group across 1 directory with 3 updates (#808)
• Additional commits viewable in compare view

Updates actions/upload-artifact from 6.0.0 to 7.0.0

Release notes

Sourced from actions/upload-artifact's releases.

v7.0.0

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

• Add proxy integration test by @​Link- in actions/upload-artifact#754
• Upgrade the module to ESM and bump dependencies by @​danwkennedy in actions/upload-artifact#762
• Support direct file uploads by @​danwkennedy in actions/upload-artifact#764

New Contributors

• @​Link- made their first contribution in actions/upload-artifact#754

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

Commits

• bbbca2d Support direct file uploads (#764)
• 589182c Upgrade the module to ESM and bump dependencies (#762)
• 47309c9 Merge pull request #754 from actions/Link-/add-proxy-integration-tests
• 02a8460 Add proxy integration test
• See full diff in compare view

Updates release-drafter/release-drafter from 6.2.0 to 7.1.1

Release notes

Sourced from release-drafter/release-drafter's releases.

v7.1.1

What's Changed

Bug Fixes

• fix: remove disable-releaser and disable-autolabeler from action.yaml (#1564) @​cchanche

Full Changelog: release-drafter/release-drafter@v7.1.0...v7.1.1

v7.1.0

What's Changed

New

• feat: filter previous releases by range with semver (#1445) @​cchanche
• feat: support advanced substitutions in replacers (#1517) @​cchanche

Bug Fixes

• fix: support pull_request_target event in autolabeler (#1560) @​jmeridth
• fix: empty template when prs all are excluded by labels (#1429) @​Bledai
• fix: fall back to org .github repo when config not found in current repo (#1554) @​jetersen

Maintenance

• ci: make sure PRs have a type label (#1557) @​cchanche

Documentation

• docs: update README with pull_request_target example (#1561) @​jmeridth

Full Changelog: release-drafter/release-drafter@v7.0.0...v7.1.0

v7.0.0

What's Changed

Breaking

• feat: new major version (#1475) @​cchanche

Bug Fixes

• fix: JSON schema too strict with required fields (#1535) @​jetersen

Maintenance

• chore(deps): update vitest to 4.1.0 (#1544) @renovate[bot]
• chore(deps): update linters (#1549) @renovate[bot]
• chore(deps): update dependency nock to 14.0.11 (#1548) @renovate[bot]
• chore(deps): update dependency @​graphql-codegen/near-operation-file-preset to 5.0.0 (#1545) @renovate[bot]

... (truncated)

Commits

• 139054a chore: release v7.1.1
• 114efa7 fix: remove disable-releaser and disable-autolabeler from action.yaml (#1564)
• b23b6d2 test: add semantic prefix replacer example
• 44a942e chore: release v7.1.0
• f1f40a0 docs: update README with pull_request_target example (#1561)
• ebb69bb fix: support pull_request_target event in autolabeler (#1560)
• bddbd54 ci: make sure PRs have a type label (#1557)
• 4a66170 fix: empty template when prs all are excluded by labels (#1429)
• 7431882 feat: filter releases by semver range (#1445)
• 5a8b0d3 ci: restore CodeQL category lost when matrix was removed
• Additional commits viewable in compare view

Updates cpp-linter/cpp-linter-action from 2.16.7 to 2.17.0

Release notes

Sourced from cpp-linter/cpp-linter-action's releases.

v2.17.0

🚀 New features and improvements

• feat: support clang version to include 22 and adjust default version to 20 by @​shenxianpeng in #398

👷 Changes for developers

• chore(deps): update Dependabot configuration to limit open pull requests and change schedule to weekly by @​shenxianpeng in #400

Full Changelog: cpp-linter/cpp-linter-action@v2.16.7...v2.17.0

Commits

• 2446798 feat: support clang version to include 22 and adjust default version to 20 (#...
• d67d37b chore(deps): update Dependabot config to limit open pull requests and change ...
• See full diff in compare view

Updates astral-sh/setup-uv from 7.3.0 to 7.6.0

Release notes

Sourced from astral-sh/setup-uv's releases.

v7.6.0 🌈 Fetch uv from Astral's mirror by default

Changes

We now default to download uv from releases.astral.sh. This means by default we don't hit the GitHub API at all and shouldn't see any rate limits and timeouts any more.

🚀 Enhancements

• Fetch uv from Astral's mirror by default @​zsol (#809)

🧰 Maintenance

• Switch to ESM for source and test, use CommonJS for dist @​eifinger (#806)
• chore: update known checksums for 0.10.10 @github-actions[bot] (#804)

⬆️ Dependency updates

• chore(deps): bump zizmorcore/zizmor-action from 0.5.0 to 0.5.2 @dependabot[bot] (#808)
• Bump deps @​eifinger (#805)

v7.5.0 🌈 Use astral-sh/versions as version provider

No more rate-limits

This release addresses a long-standing source of timeouts and rate-limit failures in setup-uv.

Previously, the action resolved version identifiers like 0.5.x by iterating over available uv releases via the GitHub API to find the best match. In contrast, latest and exact versions such as 0.5.0 skipped version resolution entirely and downloaded uv directly.

The manifest-file input was an earlier attempt to improve this. It allows providing an url to a file that lists available versions, checksums, and even custom download URLs. The action also shipped with such a manifest. However, because that bundled file could become outdated whenever new uv releases were published, the action still had to fall back to the GitHub API in many cases.

This release solves the problem by sourcing version data from Astral’s versions repository via the raw content endpoint:

https://raw.githubusercontent.com/astral-sh/versions/refs/heads/main/v1/uv.ndjson

By using the raw endpoint instead of the GitHub API, version resolution no longer depends on API authentication and is much less likely to run into rate limits or timeouts.

---

[!TIP] The next section is only interesting for users of the manifest-file input

The manifest-file input lets you override that source with your own URL, for example to test custom uv builds or alternate download locations.

The manifest file must be in NDJSON format, where each line is a JSON object representing a version and its artifacts. For example:

{"version":"0.10.7","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]}
{"version":"0.10.6","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]}

... (truncated)

Commits

• 37802ad Fetch uv from Astral's mirror by default (#809)
• 9f00d18 chore(deps): bump zizmorcore/zizmor-action from 0.5.0 to 0.5.2 (#808)
• fd8f376 Switch to ESM for source and test, use CommonJS for dist (#806)
• f9070de Bump deps (#805)
• cadb67b chore: update known checksums for 0.10.10 (#804)
• e06108d Use astral-sh/versions as primary version provider (#802)
• 0f6ec07 docs: replace copilot instructions with AGENTS.md (#794)
• 821e5c9 docs: add cross-client dependabot rollup skill (#793)
• 6ee6290 chore(deps): bump versions (#792)
• 9f332a1 Add riscv64 architecture support to platform detection (#791)
• Additional commits viewable in compare view

Updates actions/download-artifact from 7.0.0 to 8.0.1

Release notes

Sourced from actions/download-artifact's releases.

v8.0.1

What's Changed

• Support for CJK characters in the artifact name by @​danwkennedy in actions/download-artifact#471
• Add a regression test for artifact name + content-type mismatches by @​danwkennedy in actions/download-artifact#472

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

v8.0.0

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

• Don't attempt to un-zip non-zipped downloads by @​danwkennedy in actions/download-artifact#460
• Add a setting to specify what to do on hash mismatch and default it to error by @​danwkennedy in actions/download-artifact#461

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

Commits

• 3e5f45b Add regression tests for CJK characters (#471)
• e6d03f6 Add a regression test for artifact name + content-type mismatches (#472)
• 70fc10c Merge pull request #461 from actions/danwkennedy/digest-mismatch-behavior
• f258da9 Add change docs
• ccc058e Fix linting issues
• bd7976b Add a setting to specify what to do on hash mismatch and default it to error
• ac21fcf Merge pull request #460 from actions/danwkennedy/download-no-unzip
• 15999bf Add note about package bumps
• 974686e Bump t...

  Description has been truncated

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud