jdx · jdx · Nov 26, 2025 · Nov 26, 2025
diff --git a/README.md b/README.md
@@ -72,17 +72,17 @@ echo '~/.local/bin/mise activate pwsh | Out-String | Invoke-Expression' >> ~/.co
 ### Execute commands with specific tools
 
 ```sh-session
-$ mise exec node@22 -- node -v
-mise node@22.x.x ✓ installed
-v22.x.x
+$ mise exec node@24 -- node -v
+mise node@24.x.x ✓ installed
+v24.x.x
 ```
 
 ### Install tools
 
 ```sh-session
-$ mise use --global node@22 go@1
+$ mise use --global node@24 go@1
 $ node -v
-v22.x.x
+v24.x.x
 $ go version
 go version go1.x.x macos/arm64
 ```

diff --git a/docs/demo.md b/docs/demo.md
@@ -13,9 +13,9 @@ The following demo shows:
 `mise exec <tool> -- <command>` allows you to run any tools with mise
 
 ```shell
-mise exec node@22 -- node -v
-# mise node@22.14.0 ✓ installed
-# v22.14.0
+mise exec node@24 -- node -v
+# mise node@24.x.x ✓ installed
+# v24.x.x
 ```
 
 node is only available in the mise environment, not globally

diff --git a/docs/dev-tools/index.md b/docs/dev-tools/index.md
@@ -229,22 +229,22 @@ For some users, `mise use` might be the only command you need to learn. It will
 
 ```shell
 > cd my-project
-> mise use node@22
+> mise use node@24
 # download node, verify signature...
-mise node@22.12.0 ✓ installed
-mise ~/my-project/mise.toml tools: node@22.12.0 # mise.toml created/updated
+mise node@24.x.x ✓ installed
+mise ~/my-project/mise.toml tools: node@24.x.x # mise.toml created/updated
 
 > which node
-~/.local/share/installs/node/22.12.0/bin/node
+~/.local/share/installs/node/24.x.x/bin/node
 ```
 
-`mise use node@22` will install the latest version of node-22 and create/update the
+`mise use node@24` will install the latest version of node-24 and create/update the
 `mise.toml`
 config file in the local directory. Anytime you're in that directory, that version of `node` will be
 used.
 
-`mise use -g node@22` will do the same but update the [global config](/configuration.html#global-config-config-mise-config-toml) (~/.config/mise/config.toml) so
-unless there is a config file in the local directory hierarchy, node-22 will be the default version
+`mise use -g node@24` will do the same but update the [global config](/configuration.html#global-config-config-mise-config-toml) (~/.config/mise/config.toml) so
+unless there is a config file in the local directory hierarchy, node-24 will be the default version
 for
 the user.
 

diff --git a/docs/dev-tools/mise-lock.md b/docs/dev-tools/mise-lock.md
@@ -110,7 +110,7 @@ When you want to update tool versions:
 
 ```sh
 # Update tool version in mise.toml
-mise use node@22
+mise use node@24
 
 # This will update both the installation and mise.lock
 ```

diff --git a/docs/environments/index.md b/docs/environments/index.md
@@ -53,11 +53,11 @@ mise exec -- echo $MY_VAR
 You can of course combine them with [tools](/dev-tools/):
 
 ```sh
-mise use node@22
+mise use node@24
 mise set MY_VAR=123
 cat mise.toml
 # [tools]
-# node = '22'
+# node = '24'
 # [env]
 # MY_VAR = '123'
 mise exec -- node --eval 'console.log(process.env.MY_VAR)'
@@ -81,7 +81,7 @@ If you are using [`shims`](/dev-tools/shims.html), the environment variables wil
 
 ```shell
 mise set NODE_ENV=production
-mise use node@22
+mise use node@24
 # using the absolute path for the example
 ~/.local/share/mise/shims/node --eval 'console.log(process.env.NODE_ENV)'
 ```

diff --git a/docs/getting-started.md b/docs/getting-started.md
@@ -107,19 +107,19 @@ mise exec python@3 -- python
 # >>> ...
 ```
 
-or run node 22:
+or run node 24:
 
 ```sh
-mise exec node@22 -- node -v
-# v22.x.x
+mise exec node@24 -- node -v
+# v24.x.x
 ```
 
 [`mise x|exec`](/cli/exec.html) is a powerful way to load the current `mise` context (tools & environment variables) without modifying your shell session or running ad-hoc commands with mise tools set. Installing [`tools`](/dev-tools/) is as simple as running [`mise u|use`](/cli/use.html).
 
 ```shell
-mise use --global node@22 # install node 22 and set it as the global default
+mise use --global node@24 # install node 24 and set it as the global default
 mise exec -- node my-script.js
-# run my-script.js with node 22...
+# run my-script.js with node 24...
 ```
 
 Another useful command is [`mise r|run`](/cli/run.html) which allows you to run a [`mise task`](/tasks/) or a script with the `mise` context.
@@ -219,16 +219,16 @@ You can run [`mise dr|doctor`](/cli/doctor.html) to verify that mise is correctl
 Now that `mise` is activated or its shims have been added to `PATH`, `node` is also available directly! (without using `mise exec`):
 
 ```sh
-mise use --global node@22
+mise use --global node@24
 node -v
-# v22.x.x
+# v24.x.x
 ```
 
-Note that when you ran `mise use --global node@22`, `mise` updated the global `mise` configuration.
+Note that when you ran `mise use --global node@24`, `mise` updated the global `mise` configuration.
 
 ```toml [~/.config/mise/config.toml]
 [tools]
-node = "22"
+node = "24"
 ```
 
 ## 4. Use tools from backends (npm, pipx, core, aqua, github) {#tool-backends}

diff --git a/docs/mise-cookbook/nodejs.md b/docs/mise-cookbook/nodejs.md
@@ -16,10 +16,10 @@ This will install the latest version of Node.js and create a `mise.toml` file wi
 node = "latest"
 ```
 
-If you want to install Node.JS globally instead (for example, node v22), you can use the following command:
+If you want to install Node.JS globally instead (for example, node v24), you can use the following command:
 
 ```shell
-mise use -g node@22
+mise use -g node@24
 ```
 
 ## Add node modules binaries to the PATH

diff --git a/docs/tapes/demo.tape b/docs/tapes/demo.tape
@@ -32,7 +32,7 @@ Enter
 Type '# "mise exec <tool> -- <command>" allows you to run any tools with mise'
 Sleep 1s Enter Wait
 
-Type "mise exec node@22 -- node -v"
+Type "mise exec node@24 -- node -v"
 Sleep 500ms Enter Wait Sleep 2s
 
 Type '# node is only available in the mise environment, not globally' Sleep 500ms Enter Wait

diff --git a/docs/tips-and-tricks.md b/docs/tips-and-tricks.md
@@ -151,7 +151,7 @@ export MISE_AQUA_MINISIGN=false
 ## [`mise up --bump`](/cli/upgrade.html)
 
 Use `mise up --bump` to upgrade all software to the latest version and update `mise.toml` files. This keeps the same semver range as before,
-so if you had `node = "20"` and node 22 is the latest, `mise up --bump node` will change `mise.toml` to `node = "22"`.
+so if you had `node = "22"` and node 24 is the latest, `mise up --bump node` will change `mise.toml` to `node = "24"`.
 
 ## cargo-binstall
 

diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
@@ -50,13 +50,13 @@ detected with your setup. If you submit a bug report, please include the output
 
 Likely this means that mise isn't first in PATH—using shims or `mise activate`. You can verify if
 this is the case by calling `which -a`, for example, if [email protected] is being used but mise specifies
-node@22.0.0, first make sure that mise has this version installed and active by running `mise ls node`.
+node@24.0.0, first make sure that mise has this version installed and active by running `mise ls node`.
 It should not say missing and have the correct "Requested" version:
 
 ```bash
 $ mise ls node
 Plugin  Version  Config Source       Requested
-node    22.0.0  ~/.mise/config.toml  22.0.0
+node    24.0.0  ~/.mise/config.toml  24.0.0
 ```
 
 If `node -v` isn't showing the right version, make sure mise is activated by running `mise doctor`.

diff --git a/docs/walkthrough.md b/docs/walkthrough.md
@@ -19,16 +19,16 @@ You use it like so (note that `mise` must be [activated](/getting-started.html#a
 
 ```bash
 mkdir example-project && cd example-project
-mise use node@22
+mise use node@24
 node -v
-# v22.0.0
+# v24.x.x
 ```
 
 And you'll also note that you now have a `mise.toml` file with the following content:
 
 ```mise-toml [mise.toml]
 [tools]
-node = "22"
+node = "24"
 ```
 
 - If this file is in the root of a project, `node` will be installed whenever someone runs [`mise install|i`](/cli/install).
@@ -78,11 +78,11 @@ Upgrading tool versions can be done with [`mise up|upgrade`](/cli/upgrade). By d
 the version prefix in `mise.toml`. If a [lockfile](/configuration/settings#lockfile) exists,
 mise will update `mise.lock` to the latest version of the tool with the prefix from `mise.toml`.
 
-So if you have `node = "22"` in `mise.toml`, then `mise upgrade node` will upgrade to the latest version of `node 22`.
+So if you have `node = "24"` in `mise.toml`, then `mise upgrade node` will upgrade to the latest version of `node 24`.
 
 If you'd like to upgrade to the latest version of node, you can use `mise upgrade --bump node`. It will set the version
-at the same specificity as the current version, so if you have `node = "22"`, but use `mise upgrade --bump node` to update to
-`node@24`, then it will set `node = "24"` in `mise.toml`.
+at the same specificity as the current version, so if you have `node = "24"`, but use `mise upgrade --bump node` to update to
+`node@26`, then it will set `node = "26"` in `mise.toml`.
 
 _See [Dev Tools](/dev-tools/) for more information on working with tools._