Repository navigation
chore(deps): update github actions - #330
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
October 24, 2026 17:20
7529348 to
f47a23d
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
4 times, most recently
from
October 26, 2026 05:10
49e47d1 to
0051900
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
October 26, 2026 10:28
0051900 to
b4dd9da
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:
ae2d0aa→40fec54v4.6.0→v4.7.0v5.2.2→v5.2.3Release Notes
docker/login-action
v4.7.0Compare Source
registry-authby @crazy-max in #1089Full Changelog: docker/login-action@v4.6.0...v4.7.0
jdx/mise-action
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
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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.