mirror
/
renovate
mirror of https://github.com/renovatebot/renovate
2
0
Fork 0
Code Releases Activity
renovate/lib/modules/manager/mise
History
Risu bad3cb550e
feat(manager): add missing mise core toolings (#32954) 		2024-12-07 06:50:59 +00:00
..
__fixtures__ feat(manager): add mise package manager (#29950) 2024-07-08 14:27:31 +00:00
extract.spec.ts feat(manager): add mise package manager (#29950) 2024-07-08 14:27:31 +00:00
extract.ts chore: eslint to enforce for typed imports (#30844) 2024-08-19 13:15:27 +00:00
index.ts docs(managers): add missing url and displayName (#32621) 2024-12-01 08:47:27 +00:00
readme.md fix(mise): add config filenames (#30283) 2024-07-21 12:43:17 +00:00
schema.ts feat(manager): add mise package manager (#29950) 2024-07-08 14:27:31 +00:00
upgradeable-tooling.ts feat(manager): add missing mise core toolings (#32954) 2024-12-07 06:50:59 +00:00
utils.spec.ts feat(manager): add mise package manager (#29950) 2024-07-08 14:27:31 +00:00
utils.ts chore: eslint to enforce for typed imports (#30844) 2024-08-19 13:15:27 +00:00

readme.md

Renovate can update the mise .mise.toml file.

Renovate's mise manager can version these tools:

Renovate only updates primary versions

Renovate's mise manager is designed to automatically update the first (primary) version listed for each tool in the .mise.toml file.

Secondary or fallback versions require manual updates.

Example

Given a .mise.toml entry like:

[tools]
erlang = ["23.3", "22.0"]

Renovate will update "23.3" (the primary version) but will not touch "22.0" (the fallback version).

Why can Renovate only update primary versions?

To maintain consistency and reliability, Renovate opts to only manage the first listed version.

  • Fallback versions can often be older versions of a tool that are known to work and are there as a backup.

This follows the same workflow that Renovate's asdf manager uses.

Plugin/tool support

Renovate uses:

to understand and manage tool versioning.

Support for new tools/plugins needs to be manually added to Renovate's logic.

Adding new tool support

There are 2 ways to integrate versioning for a new tool:

  • Renovate's mise manager: ensure upstream mise supports the tool, then add support to the mise manager in Renovate
  • Renovate's asdf manager: improve the asdf manager in Renovate, which automatically extends support to mise

If mise adds support for more tools via its own core plugins, you can create a PR to extend Renovate's mise manager to add support for the new tooling.

You may be able to add support for new tooling upstream in the core plugins - create an issue and see if the community agrees whether it belongs there, or if it would be better as an asdf- plugin.

If you are wanting to add support for an existing asdf-x plugin to mise, you can create a PR to extend Renovate's asdf manager, which indirectly helps Renovate's mise manager as well.