Skip to content

chore(deps): pin dependencies - #134

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions-pinned-digests
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions-pinned-digests

Conversation

@renovate

@renovate renovate Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change Pending
actions/checkout action pin v6 → v6.1.0
actions/checkout action pin v7 → v7.0.1
actions/checkout action minor v4.2.2 → v4.4.0
actions/create-github-app-token action pin v3 → v3.3.0
actions/create-github-app-token action minor v3.2.0 → v3.3.0
actions/download-artifact action pin v8 → v8.0.2
actions/download-artifact action patch v8.0.1 → v8.0.2
actions/setup-java action pin v5 → v5.7.0
actions/setup-node action pin v6 → v6.5.0
actions/setup-node action minor v7.0.0 → v7.1.0
actions/setup-node action pin v7 → v7.1.0
actions/setup-python action pin v6 → v6.3.0
actions/upload-artifact action patch v7.0.1 → v7.0.2
cachix/install-nix-action action pin v31 → v31.11.3
docker/build-push-action action pin v7 → v7.4.0
docker/login-action action pin v4 → v4.8.0
docker/setup-buildx-action action pin v4 → v4.4.1
docker/setup-qemu-action action pin v4 → v4.4.0
googleapis/release-please-action action pin v5 → v5.0.0
gradle/actions action pin v6 → v6.4.1
jdx/mise-action action patch v5.2.0 → v5.2.5 v5.2.7 (+1)
oras-project/setup-oras action patch v2.0.2 → v2.0.3
pnpm/action-setup action pin v6 → v6.1.1
re-actors/alls-green action pinDigest → b5b5b37
sigstore/cosign uses-with patch v2.6.1 → v2.6.5

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Release Notes

actions/checkout

v4.4.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@v4.3.1...v4.4.0

v4.3.1

Compare Source

v4.3.0

Compare Source

actions/create-github-app-token

v3.3.0

Compare Source

Features
Bug Fixes
  • deps: bump nested undici from 6.24.0 to 6.29.0 (#​403) (12461a3)
  • deps: bump the production-dependencies group across 1 directory with 3 updates (#​395) (a69c19d)
actions/download-artifact

v8.0.2

Compare Source

What's Changed

New Contributors

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

actions/setup-node

v7.1.0

Compare Source

What's Changed

Enhancements:
Bug fixes:
Documentation updates:
Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v7.0.0...v7.1.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

jdx/mise-action

v5.2.5: : Bundled packslip verifier updated to 1.11.0; README examples use v5

Compare Source

This release updates the packslip library that the action uses to verify downloaded mise releases, and updates the README examples to use the current major versions.

Changed
  • packslip updated from 1.8.0 to 1.11.0. The action uses packslip to check a downloaded mise binary against the signed packslip.sigstore.json that ships with mise releases from 2026.9.3 onward. The new version runs extra checks on the signed statement: the identity it declares must match the certificate that signed it, and the certificate must belong to the github.com/jdx/mise repository. GitHub and GitLab repository names now match regardless of letter case. The action still asks for the same identity, issuer and tag as before, and there are no new inputs. (#​715)
  • The README examples now use jdx/mise-action@v5 and actions/checkout@v7. (#​710 by @​deining)

Full Changelog: jdx/mise-action@v5.2.4...v5.2.5

v5.2.4: : Reuse cached signed checksums when restoring mise

Compare Source

Jobs that restore mise from the cache no longer have to download its signed checksums from GitHub on every run, so a network failure at that step no longer fails a job that otherwise restored correctly.

Fixed

  • Restoring a cached mise no longer needs a network download of the checksums. The action checks the cached mise binary against the signed SHASUMS256.txt and its .minisig. Before this release it downloaded both files from GitHub on every run, even when the cache restored correctly. When that download failed, for example after repeated curl errors, the job failed. Now, once the signature checks out, the action saves both files as SHASUMS256-<version>.txt and .minisig in <mise_dir>/bin, which is part of the mise cache. On later runs it reads them from the restored cache and checks the minisign signature again before using them. If the files are missing, corrupt or tampered with, the action downloads them as it did before. There are no new inputs. (#​708 by @​jdx)
    • Caches saved by earlier versions don't contain these files. The main cache is only saved on a cache miss, so runs keep downloading the checksums until the cache is saved again or its key changes.

Full Changelog: jdx/mise-action@v5.2.3...v5.2.4

v5.2.3: : Faster cache key computation in large workspaces

Compare Source

The cache key no longer comes from searching the whole workspace for mise config files. In repos that already contain node_modules or vendor/bundle, this removes a delay of several minutes in "Restoring mise cache".

Fixed
  • "Restoring mise cache" no longer takes minutes after installing dependencies. To build the cache key, the action used to match about 25 **/… glob patterns. That meant it walked every subdirectory of the workspace, including node_modules and vendor/bundle, before checking the cache at all. When the action ran after a step like pnpm install or ruby/setup-ruby with bundler-cache: true, this could take 3–7 minutes. The action now looks for mise config files the same way mise does: only in the working directory and each parent directory up to the workspace root. It checks for mise.toml, .mise.toml, .config/mise/…, conf.d fragments, .tool-versions, and their local, env-specific and .lock variants. The step also logs Hashed mise config files in N.Ns. (#​703 by @​jdx and @​corsicanec82)
    • If you set a custom cache_key that doesn't use {{file_hash}} or {{default}}, the action no longer hashes config files at all.
    • Config files in subdirectories, such as monorepo sub-projects, no longer affect the cache key. mise only loads them with --monorepo.
    • Cache keys change, so the first run after you upgrade will miss the cache.
New Contributors

Full Changelog: jdx/mise-action@v5.2.2...v5.2.3

v5.2.2: : Include conf.d config fragments in the cache key

Compare Source

The cache key now includes mise conf.d/*.toml config fragments, so changing one of them invalidates the cache.

Fixed
  • Editing a conf.d fragment now invalidates the cache. mise can load config from single-file fragments in conf.d/ directories, but the action didn't hash those files when it built the cache key. As a result, adding or changing tools in a fragment could restore an outdated cache. The cache key now also hashes conf.d/*.toml files under .config/mise/, .mise/ and mise/. If your repo already uses these fragments, the cache will miss once after you upgrade. (#​698 by @​rileymichael)
New Contributors

Full Changelog: jdx/mise-action@v5.2.1...v5.2.2

v5.2.1: : Require the signed packslip for mise 2026.9.3 and later

Compare Source

The action now refuses to install mise 2026.9.3 or later if the release's signed packslip is missing. This closes a gap where verification could be downgraded to the weaker checksum check.

Fixed
  • A missing packslip no longer weakens the check on recent mise releases. v5.2.0 started checking the mise binary against the release's signed packslip.sigstore.json. If that file wasn't found, though, the action quietly fell back to the minisign-signed SHASUMS256 checksums. Anyone who could hide the file could force the weaker check. Every mise release from 2026.9.3 on includes a packslip, so for those versions a missing bundle now stops the install with an error like this:
    mise v2026.10.11 must ship a signed packslip, but https://github.com/jdx/mise/releases/download/v2026.10.11/packslip.sigstore.json was not found
    
    Releases before 2026.9.3 don't include a packslip, so they're still checked against the signed checksums. A version string that isn't three dot-separated numbers also requires a packslip. If you set the sha256 input, it still takes precedence over both checks. A packslip that fails verification still never falls back to the checksums. (#​695 by @​jdx)

Full Changelog: jdx/mise-action@v5.2.0...v5.2.1

oras-project/setup-oras

v2.0.3

Compare Source

Highlights
  • Support ORAS CLI version(s): 1.3.5, 1.3.6
What's Changed
New Contributors

Full Changelog: oras-project/setup-oras@v2.0.2...v2.0.3

sigstore/cosign

v2.6.5

Compare Source

Changelog

This release backports GHSA-fx35-mq7g-6g98 (Verification bypass via public key in legacy bundle) to Cosign v2.6.x.

We strongly encourage folks to continue their migration to the bundle format. The Cosign v3.1.x releases support both formats; the primary change being that the default for signing is the bundle format (although you can specify --new-bundle-format=false to sign with the old format). The verification commands in Cosign v3.1.x support both formats, and will try to detect the format for you for maximum compatibility.

Thanks to all contributors!

v2.6.4

Compare Source

This release is a backport of OCI manifest fixes, and better support for cosign attestation download when you are using a mix of old Cosign signatures with the more recent bundle format.

We strongly encourage folks to continue their migration to the bundle format. The Cosign v3.1.x releases support both formats; the primary change being that the default for signing is the bundle format (although you can specify --new-bundle-format=false to sign with the old format). The verification commands in Cosign v3.1.x support both formats, and will try to detect the format for you for maximum compatibility.

Changelog

  • 26261f0 Allow attestation download to handle both bundle types (#​4996) (#​5017)
  • d49a0c1 fix: include artifactType in OCI 1.1 signature referrer manifest (cherry-pick PR-4997 to release-2.6) (#​5002)
Thanks to all contributors!

v2.6.3

Compare Source

Changelog

v2.6.3 resolves GHSA-w6c6-c85g-mmv6.

Thanks to all contributors!

v2.6.2

Compare Source

v2.6.2 resolves GHSA-whqx-f9j3-ch6m.

Changes


Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • "before 9am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 added area: tooling Reusable workflows, Gradle, templates, Renovate, and API tooling. component: dependencies Dependency update or dependency policy. dependencies Dependency update, lockfile change, or dependency policy. priority: P2 Medium; normal planned work. type: chore Maintenance work without intended behavior change. labels Sep 14, 2026
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch 2 times, most recently from 407c177 to bf7d925 Compare September 20, 2026 03:47
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch 4 times, most recently from d55f792 to d1010da Compare October 7, 2026 10:46
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch 14 times, most recently from 63898e6 to 4b1fd52 Compare October 16, 2026 16:11
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch 5 times, most recently from 91314e5 to 9156406 Compare October 19, 2026 13:32
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch 8 times, most recently from 89dc1c9 to 476ca59 Compare October 22, 2026 11:08
@renovate
renovate Bot enabled auto-merge (squash) October 22, 2026 11:08
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch 5 times, most recently from 783c444 to 81508ec Compare October 27, 2026 15:01
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch 8 times, most recently from 1e6a512 to 8af21bf Compare November 1, 2026 21:46
@renovate renovate Bot changed the title chore(deps): update github-actions pinned digests chore(deps): pin dependencies Nov 1, 2026
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch 3 times, most recently from d93c2d6 to e3909eb Compare November 7, 2026 07:34
@renovate
renovate Bot force-pushed the renovate/github-actions-pinned-digests branch from e3909eb to da2e12f Compare November 8, 2026 03:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: tooling Reusable workflows, Gradle, templates, Renovate, and API tooling. component: dependencies Dependency update or dependency policy. dependencies Dependency update, lockfile change, or dependency policy. priority: P2 Medium; normal planned work. type: chore Maintenance work without intended behavior change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants