[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
jdx/mise	uses-with	patch	2026.10.9 → 2026.10.12	v2026.10.18 (+4)
jdx/mise-action	action	minor	v5.1.2 → v5.2.0	v5.2.2 (+1)

---

Release Notes

jdx/mise

v2026.10.12: : Per-tool Python runtimes for PyPI tools, Gradle workspace discovery, and env file find_up

Compare Source

PyPI and pipx tools can now choose their own Python runtime, the workspace graph can read Gradle multi-module builds, and env._.file can search parent directories. When mise-versions is having an outage, GitHub lookups now retry on api.github.com, and _.source scripts no longer pick up ~/.bashrc when mise is launched from an editor.

Added

• Per-tool Python for pypi: tools. Set python to a minor series or an exact version, and mise installs that runtime and passes it to uv or pipx for that tool only. The runtime stays private to the tool and does not become your shell's default Python. mise lock records the selected Python with the tool, and mise prune keeps any runtime that a retained tool environment still uses. You can't combine python with --python/-p in uvx_args or pipx_args. Tools that don't set python behave as before. #​14479 (@​jdx)

  [tools]
  "pypi:black" = { version = "latest", python = "3.12" }
  "pypi:ruff" = { version = "latest", python = "3.12.12" }

  If you change a tool's python, mise installs a new environment instead of reusing the old one. If that install fails, the previous working environment is left untouched. #​14504 (@​jdx)

• Gradle workspace discovery. mise tasks graph and mise run --affected now find projects listed by include in settings.gradle or settings.gradle.kts, using Groovy or Kotlin syntax. Project IDs follow Gradle paths: :app becomes gradle::app, and the root project is gradle::. Literal project(":lib") references in a project's top-level dependencies {} block become graph edges. mise reads the scripts as text and never runs Gradle. If an include is computed or conditional, a projectDir isn't a plain file("...") literal, or both settings files exist, mise reports an error that points to [monorepo.projects."gradle:..."] overrides. Editing the settings script marks every Gradle project as affected. Based on a prototype by @​Jarvvski. #​14512 (@​jdx)

• find_up for env._.file. With find_up = true, mise looks for a relative path in the current directory and in every parent, so a global config can load each project's .env files. Files load from the root down, so values in closer files win. The default is false, and the option has no effect on absolute paths. #​14497 (@​jdx)

  # ~/.config/mise/config.toml
  [env]
  _.file = [
    { path = ".env", find_up = true },
    { path = ".env.local", find_up = true },
  ]

• Detect git-rewritten files in watch_files hooks. mise sets MISE_WATCH_FILES_GIT_REWRITTEN=1 when every changed file was last written before git's most recent HEAD move (checkout, pull, rebase). Commits don't count as HEAD moves. Hooks such as format-on-edit can use this to skip files the user didn't edit. git stash pop/apply don't move HEAD, so mise doesn't detect them. #​14511 (@​jdx)

  [[watch_files]]
  patterns = ["**/*.go"]
  run = '[ -n "$MISE_WATCH_FILES_GIT_REWRITTEN" ] || { IFS=:; hk fix $MISE_WATCH_FILES_MODIFIED; }'

• .tera sources inferred for dotfile group templates. A mode = "template" entry in [dotfile_groups] no longer needs a source just to point at a .tera file. If the exact path doesn't exist, mise falls back to the same path with .tera added. An explicit source still takes precedence, and the .tera file is not also deployed under its suffixed name. #​14502 (@​jdx)

• mise lock warns about unsupported platforms. If you name platforms with lockfile_platforms or mise lock --platform, mise prints a warning for each tool version that has no build for one of them, for example apko@0.30.0 is not available for windows-x64; it will not install there. The default platform set still only logs this at debug level, and the exit status is unchanged. #​14500 (@​jdx)

• Registry: added martin (github:maplibre/martin). #​14488 (@​ivan-ivkovic, @​jdx)

Fixed

• GitHub lookups survive mise-versions outages. If mise-versions times out, drops the connection, or returns 429 or 5xx, mise now retries the lookup on api.github.com, using your GitHub token if one is set. This covers releases, tags, repository contents, attestations and self-update. A 404, 403 or empty answer from mise-versions is still trusted and not retried, so normal use doesn't spend GitHub's anonymous rate limit. If both sources fail, the error shows both failures, and a previously cached version list is still used. #​14501 (@​jdx)
• _.source no longer loads ~/.bashrc. When mise's stdin was a socket and SHLVL was unset, which happens when an editor extension such as the VS Code mise extension starts it, bash sourced ~/.bashrc before the script. That leaked variables into the environment and could drop the script's PATH entries. The script now runs with --norc. #​14487 (@​pikeas)
• Each version entry uses its own options. When a tool listed several versions, options set only on the first entry leaked into the later ones. For example, prerelease = true on a latest entry made a separate "1" entry resolve to a prerelease. #​14476 (@​JamBalaya56562, @​risu729)
• Project overrides now work when a workspace provider fails. Previously, if a provider couldn't read its manifest (for example, a malformed go.work), mise tasks graph and mise run --affected failed for the whole repo. Declaring a project in that provider's namespace under [monorepo.projects] now replaces the provider's output and clears its error. Providers with no declared projects still fail loudly. #​14508 (@​jdx)

Documentation

• Explained why mise activate keeps shims on PATH #​14493 (@​jdx), and clarified the platform-specific mise cache paths for CI #​14506 (@​zeitlinger).

Full Changelog: jdx/mise@v2026.10.11...v2026.10.12

💚 Sponsor mise

mise is built and maintained by @​jdx, an open source developer at entire.io, the title sponsor of his open source work.

If mise saves you or your team time, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep mise fast, free, and independent.

v2026.10.11: : Much faster installs and far fewer GitHub API calls

Compare Source

mise is much faster in this release and calls the GitHub API far less. Version lists, release tags, attestations and other public GitHub metadata now come from mise-versions, so everyday commands like mise install, exec, shims, outdated, lock and self-update are quicker and users without a GitHub token no longer run into the 60-requests-an-hour limit. Cached version lists are reused for longer, so repeat installs skip most lookups. It also adds mise bootstrap --upgrade and mise env --paths, and closes a trust gap in remote task files.

Speed and GitHub API usage

Cold-cache timings for v2026.10.10 versus v2026.10.11, measured with hyperfine on one Linux x64 machine with no GitHub token set:

Command	v2026.10.10	v2026.10.11
mise ls-remote python	961 ms	93 ms
mise install (jq, ripgrep, fd, bat, gh, shellcheck)	1.49 s	1.08 s
mise outdated (same six tools installed)	433 ms	272 ms

The install and outdated runs are noisy (±0.1–0.4s over 4 runs) and the install time includes downloads, so treat them as rough. Requests to api.github.com in a cold mise install of github: tools dropped from 2 to 0. Cold mise outdated made 8 network requests before and none now.

• Public GitHub metadata comes from mise-versions. With use_versions_host on (the default), release lists, latest, git tags (aqua github_tag packages, ubi and go), artifact attestations (including aqua's predicate_type filters) and the digest in the checksum-mismatch hint are read from mise-versions instead of api.github.com. GitHub is still asked directly for repositories mise-versions doesn't list when you have a token (the private-repository case), and in paranoid mode for attestations. The direct API is also used with use_versions_host = false, GitHub url_replacements and custom api_urls. #​14460, #​14461, #​14469, #​14481, #​14477, #​14443
• Other requests also moved off the GitHub API:
  • mise x, mise exec, shims and hook-env use mise-versions when they auto-install a tool. #​14458
  • mise self-update reads mise's releases from mise-versions and downloads the archive from github.com release downloads. Packslip and zipsign verification are unchanged. #​14464
  • mise lock downloads artifacts for provenance checks from github.com instead of the API asset endpoint. #​14465
  • Aqua registries hosted on GitHub are fetched from raw.githubusercontent.com. #​14470
  • Ruby looks up the latest ruby-build release through mise-versions. #​14471
• Fewer version-list fetches. mise install, use and run now reuse a cached version list for the tool's minimum_release_age window minus one hour, clamped to 1–24h. With the default 24h cutoff, that is 23h. outdated, upgrade, ls-remote, lock and latest still refresh after 1h. If you set fetch_remote_versions_cache yourself, your value applies to every command. #​14484, #​14485, #​14457
• Faster version resolution:
  • Multi-tool commands such as mise outdated can resolve many registry tools with one request to the mise-versions index. #​14473
  • latest is resolved without refetching the list. #​14456
  • Explicit backend args such as aqua:jqlang/jq reuse the registry tool's version list. #​14459
  • Release tags come from the versions host instead of being listed or guessed. #​14442
  • Packslip installs no longer re-download what resolution already verified. #​14466
  • Install tracking and the Python version list are served from static assets. #​14441
• Python version listing no longer clones pyenv. mise ls-remote python, outdated, upgrade and fuzzy mise use python@3.12 read the python-build definitions from mise-versions. A cold listing took about 960ms before and about 90ms now. pyenv is still cloned when mise compiles Python, when python.pyenv_repo points at a fork, when you're offline, or when use_versions_host = false. Some definitions that had no date before now have one, so they are held back by minimum_release_age until they are old enough. #​14455
• mise oci build now requires root for apt: packages, as it already did for apk, and fails up front with a clear message. If apt-get still fails, the error now includes the last lines of dpkg's output. #​14447
• Registry: native-sdk now installs from npm (@native-sdk/cli), so the native command works. It requires Node 24+. #​14431

Security

• Remote task files now need trust before their headers render. A mise.toml with only [tasks] loads without trust. Before this fix, if one of those tasks set file to a remote URL, mise tasks ls, mise tasks info and mise tasks validate rendered the file's #MISE headers, so a template like {{ exec(...) }} ran without a trust prompt. Remote files now follow the same rule as local task includes: if the headers contain template syntax, the config that references them must be trusted first. Remote files with plain headers still list without trust, and braces in the script body need no trust. #​14416 (@​JamBalaya56562, @​risu729)
• Updated rustls to 0.23.46 to address a RustSec advisory. #​14434

Added

• mise bootstrap --upgrade installs what is missing and then upgrades what is already installed, in a single run. In the packages phase it runs the same upgrade as mise bootstrap packages upgrade, and pins are respected. In the tools phase it runs mise upgrade without --bump, so configured version ranges hold. Both run before the matching post hooks and dependent services. --dry-run previews both steps and --skip works as before. It does not update mise itself, repositories or images, and it does not restart services. #​14433

  mise self-update --yes && mise bootstrap --upgrade

• mise env --paths prints the PATH entries mise manages, one per line and in PATH order: tool bin directories, _.path entries, and inherited directories that mise moves forward, such as ~/.cargo/bin. This lets CI integrations export only mise's additions without diffing PATH. #​14429

  $ mise env --paths
  /home/me/.local/share/mise/installs/node/24.11.0/bin
  /home/me/.cargo/bin

• The install script downloads pinned versions from mise.jdx.dev. curl https://mise.run | MISE_VERSION=<version> sh now tries mise.jdx.dev first and falls back to GitHub Releases if that download fails. Checksums for pinned versions still come only from GitHub's SHASUMS256.txt. If no checksum is found, the script refuses to install. MISE_INSTALL_FROM_GITHUB=1 still uses GitHub only. #​14446

• Registry: gdal installs the GDAL/OGR command-line tools from conda-forge (conda:libgdal-core). #​14440 (@​ivan-ivkovic)

Fixed

• A bare mise upgrade no longer installs lazy tools that have never been installed. Naming the tool still installs it. A lazy tool that already has a version installed upgrades as before. A missing lazy tool is still installed if an upgraded tool depends on it. mise outdated now marks these tools as [MISSING] (lazy), and the bare upgrade no longer looks up their versions. #​14422 (@​ryanrhughes), #​14444
• Fixed false stack limit reached errors on the static musl builds, for example on Ubuntu 26.04. These errors broke aqua version_filter parsing and made shims such as kubectl's report "not a valid shim". #​14450
• mise lock --platform ... run on Alpine or NixOS no longer records Node source builds for other platforms. Only an explicit node.compile or all_compile = true forces source builds for those targets. #​14432
• mise upgrade --bump and hand-edited version pins no longer drop a pipx tool's locked uv dependency graph. Before, mise install --locked then failed on a fresh checkout. #​14426 (@​wislertt)
• Packslip prefixes such as fnox@1 now skip releases this host can't install, the same way latest does. Each skipped release gets a warning, and if no match can be installed, mise reports a clear error. #​14467
• A bash shim ahead of /bin no longer causes a false "shim fallback recursion detected" error for commands like bash -c 'bash --version'. The docs now recommend installing shells with the system package manager instead of [tools]. #​14475
• Bootstrap UFW rules with an interface now render the incoming direction (ufw allow in on tailscale0 ...), which fixes Invalid token 'on' errors. #​14480
• Dotfiles:
  • Before the files: apply prompt, mise now lists each file it will create, overwrite or remove and warns that local edits will be replaced. The prompt now defaults to No. #​14430
  • mise dot add --changed now also captures edited files that a copy-mode dotfile_groups root discovers automatically, not just files listed explicitly in entries. #​14436

Documentation

• The docs now recommend committing mise.lock, so CI and Docker builds skip version lookups. #​14453

New Contributors

• @​ivan-ivkovic made their first contribution in #​14440

Full Changelog: jdx/mise@v2026.10.10...v2026.10.11

💚 Sponsor mise

mise is built and maintained by @​jdx, an open source developer at entire.io, the title sponsor of his open source work.

If mise saves you or your team time, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep mise fast, free, and independent.

v2026.10.10: : Task skip_if, snap and COPR in bootstrap, and dotfiles pull fixes

Compare Source

Tasks can now skip themselves with a skip_if check, and bootstrap gains Snap packages, Fedora COPR repositories, and branch selection for --adopt. This release also fixes several mise dot pull problems that could loop, stall, or leave sharing paused on long histories. On the Windows side, it fixes .mise-bins executables and npm installs restored from a cache.

Added

• skip_if for tasks. Before a task runs, mise runs its skip_if shell command. If the command exits 0, mise skips the task and counts it as successful. Any other exit status runs the task as usual. #​14399

  [tasks.setup]
  skip_if = "test -f .initialized"
  run = "touch .initialized"

  The check runs after depends and before confirm. It uses the task's directory, shell, environment, sandbox and timeout, and it supports Tera templates and task arguments. Its output is discarded and it gets no stdin. It does not receive the task's secrets. File tasks can set it with #MISE skip_if="...". mise run --force skips the check, --dry-run prints it without running it, and mise tasks info shows it. If the check can't start, times out, or is killed, the task fails.

• Snap packages in bootstrap. On Linux, you can declare snaps in [bootstrap.packages] alongside apt and flatpak, with optional channel and classic, and state = "absent" to remove a snap. If a snap tracks a different channel than you declared, status shows it and apply moves it with snap refresh --channel. snapd can't install or hold a specific version, so apply and upgrade skip entries with a version pin and print a warning. #​14402

  [bootstrap.packages]
  "snap:jq" = "latest"
  "snap:node" = { channel = "22/stable", classic = true }

• COPR repositories with [bootstrap.dnf.repos]. You can declare a COPR next to the dnf: packages that come from it, instead of using a pre-packages hook. mise writes the same /etc/yum.repos.d file that dnf copr enable does. It does not need the copr plugin, so this also works on Fedora Atomic hosts that layer packages. The chroot is chosen from /etc/os-release (Fedora, EL, Amazon Linux). Without --yes, mise asks before enabling any COPR. mise never disables or removes repositories, but mise bootstrap unapply names any leftover files. #​14401

  [bootstrap.dnf.repos]
  ghostty = { copr = "scottames/ghostty" }
  
  [bootstrap.packages]
  "dnf:ghostty" = "latest"

• mise bootstrap --adopt <url>?ref=<branch> adopts a branch other than the default, either for global config or for a setup history. This also works with mise bootstrap remote. The ref must be a branch: tags, commits and missing branches are refused before anything is cloned. mise never switches an existing ~/.config/mise checkout to another branch, even with --update, so use git switch first. The docs now also explain how mise dot origin set relates to an adopted global config. #​14400

• GitHub OAuth refresh token in the Secure Enclave. On a Mac with Touch ID, set github.oauth_cache_secure_enclave = true to keep the native GitHub OAuth refresh token behind Touch ID instead of in plaintext in github-oauth-tokens.toml. Touch ID asks for a fingerprint only when the token needs refreshing. If you cancel the prompt, mise skips the refresh and keeps the cached access token. This needs the Developer ID-signed release build. Homebrew and source builds print a warning and keep the token in the cache file. #​14413

Changed

• On Windows, experimental = true now turns on the identity install layout by itself, which keeps deep npm, pipx and Java trees under the 260-character path limit. Only new installs use it. Existing installs stay where they are, and mise installs migrate can move them. To keep the old layout, set install_layout = "legacy" (or MISE_INSTALL_LAYOUT=legacy). Linux and macOS still need install_layout = "identity" set explicitly. #​14392

Fixed

Dotfiles

• Machines that share an origin and track an encrypted file no longer swap ciphertext back and forth forever. age encryption gives different ciphertext for the same content, so mise dot watch could publish commits endlessly without any real edits. Now mise keeps the ciphertext that history already has whenever it decrypts to the same content, mode and recipients. Machines that are already looping settle after one more sync. #​14405
• mise dot pull on long histories is much faster. The number of git processes no longer grows with the length of the history: in one test with 2,000 commits, a pull went from 137 s to under 6 s. #​14407, #​14415
• When a pull's plan went out of date because another operation saved first, it was treated as a failed apply and paused sharing until someone ran mise dot pull by hand. Now, if nothing has been written yet, mise retries on the next attempt and the watcher keeps applying changes. #​14414
• After an interrupted history operation, mise dot pull --yes no longer fails with "local saved history changed since planning". The pull now recovers the interrupted operation before it plans. #​14410
• A file that already has the incoming version (content and mode) is no longer held as an unsaved edit or conflict that pauses sharing. Running mise dot pull --take-remote <path> again for a path an earlier pull already resolved no longer fails with "is not a conflict". #​14411

Windows

• mise x and shims now run the original executable instead of its copy in .mise-bins, for tools installed with aqua symlink_bins, github filter_bins, or packslip. Programs that look for DLLs or data next to their own executable, such as exiftool, now start correctly. Tools installed by older versions need mise install --force to get this. A shell from mise activate that finds the copy on PATH still runs the copy. #​14397
• npm tools installed with the built-in aube installer are reinstalled if their dependency links are missing, for example after a CI cache restore drops NTFS junctions. Before, mise reported them as installed and they failed at run time with ERR_MODULE_NOT_FOUND. #​14418

Tools and installs

• rust@nightly, mise ls-remote rust, and mise outdated/upgrade now read the nightly manifest from RUSTUP_DIST_SERVER, so a mirror such as panamax no longer needs access to static.rust-lang.org. If [env] sets RUSTUP_DIST_SERVER or RUSTUP_UPDATE_ROOT, mise also passes them to rustup-init and rustup toolchain install. #​14384
• With a global minimum_release_age, mise use --tool-option minimum_release_age=0s <tool> now installs the actual latest version instead of the version the global cutoff allows. #​14398 (@​halms)
• Upgrading a global npm tool that mise lock --global locked with a dependency graph now regenerates the graph for the new version, including with --bump. Before, the upgrade dropped the graph and the next mise install --locked failed. #​14419 (@​altendky)
• Reinstalling a packslip tool signed by a shared reusable workflow works again with its saved pin. In v2026.10.9, mise rejected the unchanged signer as "not a workflow of" the tool's repository. Signer, workflow or repository changes are still refused. #​14408
• Building Erlang from source now shows compiling with kerl while the build runs, instead of staying on verifying checksum. kerl's output now prints above the progress row instead of writing over it. #​14391
• mise prune now shows a progress line while it scans for unused versions, instead of printing nothing for what could be a long time. #​14420
• The JSON schema now rejects unknown keys in env._.python and its venv options, matching what mise already refused at load time. Editors now flag these mistakes. #​14387 (@​JamBalaya56562, @​risu729)

Documentation

• The configuration docs now explain how mise searches for config before listing the per-directory file names. #​14390
• The bootstrap overview and run order now include [bootstrap.apt.sources]. #​14396

Full Changelog: jdx/mise@v2026.10.9...v2026.10.10

💚 Sponsor mise

mise is built and maintained by @​jdx, an open source developer at entire.io, the title sponsor of his open source work.

If mise saves you or your team time, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep mise fast, free, and independent.

jdx/mise-action

v5.2.0: : Periodic cache rebuilds, signed packslip verification, and monorepo installs

Compare Source

The default cache key now rolls over every 30 days, so long-lived caches pick up newer mise releases. The action also checks the downloaded mise binary against the release's signed packslip, and it runs mise install --monorepo automatically in monorepos. Existing caches miss once after you upgrade, because the default cache key format has changed.

Added

• The cache is rebuilt every 30 days by default. GitHub never evicts a cache that keeps getting hits. Before this release, an active repo could keep the same mise binary and tools for months, until a config file changed. The default cache key now includes a period suffix (-p<N>), so the cache is rebuilt from scratch at least once per period. All repos roll over on the same calendar boundary. Use the new cache_max_age_days input to change the period, or set it to 0 to keep the old key that never expires. Custom cache_key templates can use the new {{cache_period}} variable, which {{default}} already includes. A custom key that doesn't use it behaves as before. On self-hosted runners that keep mise data between runs, you may also need auto_update: true to pick up a newer mise. (#​689 by @​jdx, fixes #​688)

  - uses: jdx/mise-action@v5
    with:
      cache_max_age_days: 14 # default 30; 0 disables periodic rebuilds

• Throttled cache restores and saves can be retried. Before this release, when GitHub's cache service returned HTTP 429, the action gave up right away: a restore counted as a miss and a save was skipped. The new cache_restore_retry_budget and cache_save_retry_budget inputs set how long the action may wait. Each retry waits for the Retry-After value plus some random jitter. Once the budget runs out, the action falls back to the old behavior. Retries apply to the main cache, the post-step save and the binary cache. Real cache misses and reservation conflicts are never retried. Both budgets default to 0s (no retries). @actions/cache doesn't report 429 errors directly, so the action detects throttling from its warning messages. If those messages change in a future @actions/cache release, throttling won't be detected and nothing will be retried. (#​692 by @​jdx, fixes #​691)

  - uses: jdx/mise-action@v5
    with:
      cache_restore_retry_budget: 60s
      cache_save_retry_budget: 120s

• The latest mise binary can fall back to a second download source. When the action downloads the latest mise version, it can fall back between GitHub and mise.jdx.dev if the first source fails. The fetch_from_github setting decides which source it tries first. Pinned versions and minimum_release_age installs are only downloaded from GitHub. The binary is still checked against the signed checksums for the resolved version, whichever source it came from. (#​692 by @​jdx)
• The mise binary is checked against its signed packslip. If a mise release includes packslip.sigstore.json, the action checks the downloaded binary against it. The bundle must be signed by mise's release workflow for that exact tag. After a successful check, the log shows Verified <asset> against the signed packslip. If the check fails, the install stops instead of falling back to a weaker check. Releases without a packslip use the existing minisign and SHASUMS256 check. An explicit sha256 input still takes precedence. (#​693 by @​jdx)
• Monorepo-aware installs. If your mise config sets [monorepo].config_roots, the action now adds --monorepo to mise install, so tools configured anywhere in the monorepo get installed. Repos without that setting aren't affected. To opt out, set monorepo: false. (#​679 by @​zeitlinger)

Fixed

• Tool directories that mise moves to the front of PATH are now exported. The action used to find mise's PATH changes by comparing mise's PATH with the runner's. If a tool's bin directory was already on the runner's PATH, such as ~/.cargo/bin, mise only moved it to the front, so the action didn't export it. Later steps then found the mise shim first. For example, rustup resolved to the shim instead of ~/.cargo/bin/rustup. The action now asks mise for its entries with mise env --paths and exports them in the order mise reports. This fix needs a mise version that supports --paths. With older versions, the action uses the old comparison. (#​685 by @​jdx)

Documentation

• The new "Release workflows" section of the README says that jobs that publish releases shouldn't restore caches. A lower-trust workflow that can write to default-branch caches could otherwise slip files into a release. In those jobs, use cache: false or GitHub's cache-mode: none. (#​682 by @​jdx)
• The README explains how to cache mise's downloads, keyed on mise.lock, instead of installed tools. It includes a Windows example that sets MISE_CACHE_DIR from ${{ runner.temp }}, because actions/cache doesn't expand %TEMP%. (#​686, #​690 by @​zeitlinger)

Breaking Changes

• The default cache key has a new format, so the first run after upgrading is a cache miss and saves a fresh cache. After that, the cache is rebuilt every 30 days by default. To keep the old cache key that never expires, set cache_max_age_days: 0. Workflows that set a custom cache_key without {{default}} or {{cache_period}} aren't affected.

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.