Repository navigation
chore(deps): pin dependencies - #134
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
2 times, most recently
from
September 20, 2026 03:47
407c177 to
bf7d925
Compare
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
4 times, most recently
from
October 7, 2026 10:46
d55f792 to
d1010da
Compare
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
14 times, most recently
from
October 16, 2026 16:11
63898e6 to
4b1fd52
Compare
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
5 times, most recently
from
October 19, 2026 13:32
91314e5 to
9156406
Compare
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
8 times, most recently
from
October 22, 2026 11:08
89dc1c9 to
476ca59
Compare
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
5 times, most recently
from
October 27, 2026 15:01
783c444 to
81508ec
Compare
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
8 times, most recently
from
November 1, 2026 21:46
1e6a512 to
8af21bf
Compare
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
3 times, most recently
from
November 7, 2026 07:34
d93c2d6 to
e3909eb
Compare
renovate
Bot
force-pushed
the
renovate/github-actions-pinned-digests
branch
from
November 8, 2026 03:46
e3909eb to
da2e12f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v6→v6.1.0v7→v7.0.1v4.2.2→v4.4.0v3→v3.3.0v3.2.0→v3.3.0v8→v8.0.2v8.0.1→v8.0.2v5→v5.7.0v6→v6.5.0v7.0.0→v7.1.0v7→v7.1.0v6→v6.3.0v7.0.1→v7.0.2v31→v31.11.3v7→v7.4.0v4→v4.8.0v4→v4.4.1v4→v4.4.0v5→v5.0.0v6→v6.4.1v5.2.0→v5.2.5v5.2.7(+1)v2.0.2→v2.0.3v6→v6.1.1b5b5b37v2.6.1→v2.6.5Add the preset
:preserveSemverRangesto your config if you don't want to pin your dependencies.Release Notes
actions/checkout
v4.4.0Compare Source
What's Changed
allow-unsafe-pr-checkoutto v4 by @aiqiaoy in #2502https://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.1Compare Source
v4.3.0Compare Source
actions/create-github-app-token
v3.3.0Compare Source
Features
Bug Fixes
actions/download-artifact
v8.0.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v8.0.1...v8.0.2
actions/setup-node
v7.1.0Compare 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.2Compare Source
What's Changed
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 v5Compare 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.sigstore.jsonthat 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 thegithub.com/jdx/miserepository. 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)jdx/mise-action@v5andactions/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 miseCompare 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
SHASUMS256.txtand 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 asSHASUMS256-<version>.txtand.minisigin<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)Full Changelog: jdx/mise-action@v5.2.3...v5.2.4
v5.2.3: : Faster cache key computation in large workspacesCompare Source
The cache key no longer comes from searching the whole workspace for mise config files. In repos that already contain
node_modulesorvendor/bundle, this removes a delay of several minutes in "Restoring mise cache".Fixed
**/…glob patterns. That meant it walked every subdirectory of the workspace, includingnode_modulesandvendor/bundle, before checking the cache at all. When the action ran after a step likepnpm installorruby/setup-rubywithbundler-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 formise.toml,.mise.toml,.config/mise/…,conf.dfragments,.tool-versions, and their local, env-specific and.lockvariants. The step also logsHashed mise config files in N.Ns. (#703 by @jdx and @corsicanec82)cache_keythat doesn't use{{file_hash}}or{{default}}, the action no longer hashes config files at all.--monorepo.New Contributors
Full Changelog: jdx/mise-action@v5.2.2...v5.2.3
v5.2.2: : Include conf.d config fragments in the cache keyCompare Source
The cache key now includes mise
conf.d/*.tomlconfig fragments, so changing one of them invalidates the cache.Fixed
conf.dfragment now invalidates the cache. mise can load config from single-file fragments inconf.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 hashesconf.d/*.tomlfiles under.config/mise/,.mise/andmise/. 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 laterCompare 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
packslip.sigstore.json. If that file wasn't found, though, the action quietly fell back to the minisign-signedSHASUMS256checksums. 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:sha256input, 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.3Compare Source
Highlights
What's Changed
New Contributors
Full Changelog: oras-project/setup-oras@v2.0.2...v2.0.3
sigstore/cosign
v2.6.5Compare 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.4Compare Source
This release is a backport of OCI manifest fixes, and better support for
cosign attestation downloadwhen 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=falseto 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
26261f0Allow attestation download to handle both bundle types (#4996) (#5017)d49a0c1fix: include artifactType in OCI 1.1 signature referrer manifest (cherry-pick PR-4997 to release-2.6) (#5002)Thanks to all contributors!
v2.6.3Compare Source
Changelog
v2.6.3 resolves GHSA-w6c6-c85g-mmv6.
fecddd3Fix DSSE predicate check (#4802)564c5b1Backport bundle detection to sign and attest (#4727)Thanks to all contributors!
v2.6.2Compare Source
v2.6.2 resolves GHSA-whqx-f9j3-ch6m.
Changes
Configuration
📅 Schedule: (in timezone Etc/UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.