chore(docs): switch canonical domain to mise.en.dev

.github/workflows/cloudflare-deploy.yml

@@ -46,13 +46,3 @@ jobs:
           CLOUDFLARE_ACCESS_KEY_ID: ${{ secrets.CLOUDFLARE_ACCESS_KEY_ID }}
           CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_TOKEN }}
           CLOUDFLARE_SECRET_ACCESS_KEY: ${{ secrets.CLOUDFLARE_SECRET_ACCESS_KEY }}
-
-      - name: Update Redirect
-        run: |
-          VERSION="$(./scripts/get-version.sh)"
-          mise x -- scripts/update-redirect.sh "$VERSION"
-        continue-on-error: true
-        env:
-          CLOUDFLARE_ACCESS_KEY_ID: ${{ secrets.CLOUDFLARE_ACCESS_KEY_ID }}
-          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_TOKEN }}
-          CLOUDFLARE_SECRET_ACCESS_KEY: ${{ secrets.CLOUDFLARE_SECRET_ACCESS_KEY }}

CLAUDE.md

@@ -203,10 +203,10 @@ When posting comments on GitHub PRs or discussions, always include a note that t
 ### URL Structure
 When referencing mise documentation URLs, use the correct path structure based on the `docs/` directory layout:
 
-- **Dev tools & backends**: `mise.jdx.dev/dev-tools/backends/<backend>.html` (e.g., `mise.jdx.dev/dev-tools/backends/s3.html`)
-- **Configuration**: `mise.jdx.dev/configuration/...`
-- **Tasks**: `mise.jdx.dev/tasks/...`
-- **Environments**: `mise.jdx.dev/environments/...`
-- **CLI reference**: `mise.jdx.dev/cli/...`
+- **Dev tools & backends**: `mise.en.dev/dev-tools/backends/<backend>.html` (e.g., `mise.en.dev/dev-tools/backends/s3.html`)
+- **Configuration**: `mise.en.dev/configuration/...`
+- **Tasks**: `mise.en.dev/tasks/...`
+- **Environments**: `mise.en.dev/environments/...`
+- **CLI reference**: `mise.en.dev/cli/...`
 
-Do NOT use shortened paths like `mise.jdx.dev/backends/...` - always include the full path matching the `docs/` directory structure.
+Do NOT use shortened paths like `mise.en.dev/backends/...` - always include the full path matching the `docs/` directory structure.

CONTRIBUTING.md

@@ -1,3 +1,3 @@
 # Contributing
 
-Please read the full contribution guide at: <https://mise.jdx.dev/contributing.html>
+Please read the full contribution guide at: <https://mise.en.dev/contributing.html>

Cargo.toml

@@ -12,8 +12,8 @@ version = "2026.4.22"
 edition = "2024"
 description = "The front-end to your dev env"
 authors = ["Jeff Dickey (@jdx)"]
-homepage = "https://mise.jdx.dev"
-documentation = "https://mise.jdx.dev"
+homepage = "https://mise.en.dev"
+documentation = "https://mise.en.dev"
 repository = "https://github.com/jdx/mise"
 readme = "README.md"
 license = "MIT"

README.md

@@ -1,7 +1,7 @@
 <div align="center">
 
 <h1 align="center">
-  <a href="https://mise.jdx.dev">
+  <a href="https://mise.en.dev">
     <picture>
       <source media="(prefers-color-scheme: dark)" srcset="docs/public/logo-dark.svg" />
       <img src="docs/public/logo-light.svg" alt="mise" width="256" height="256" />
@@ -21,11 +21,11 @@
 <p><b>The front-end to your dev env</b></p>
 
 <p align="center">
-  <a href="https://mise.jdx.dev/getting-started.html">Getting Started</a> •
-  <a href="https://mise.jdx.dev">Documentation</a> •
-  <a href="https://mise.jdx.dev/dev-tools/">Dev Tools</a> •
-  <a href="https://mise.jdx.dev/environments/">Environments</a> •
-  <a href="https://mise.jdx.dev/tasks/">Tasks</a>
+  <a href="https://mise.en.dev/getting-started.html">Getting Started</a> •
+  <a href="https://mise.en.dev">Documentation</a> •
+  <a href="https://mise.en.dev/dev-tools/">Dev Tools</a> •
+  <a href="https://mise.en.dev/environments/">Environments</a> •
+  <a href="https://mise.en.dev/tasks/">Tasks</a>
 </p>
 
 <hr />
@@ -34,9 +34,9 @@
 
 ## What is it?
 
-- Like [asdf](https://asdf-vm.com) (or [nvm](https://github.com/nvm-sh/nvm) or [pyenv](https://github.com/pyenv/pyenv) but for any language) it manages [dev tools](https://mise.jdx.dev/dev-tools/) like node, python, cmake, terraform, and [hundreds more](https://mise.jdx.dev/registry.html).
-- Like [direnv](https://github.com/direnv/direnv) it manages [environment variables](https://mise.jdx.dev/environments/) for different project directories.
-- Like [make](https://www.gnu.org/software/make/manual/make.html) it manages [tasks](https://mise.jdx.dev/tasks/) used to build and test projects.
+- Like [asdf](https://asdf-vm.com) (or [nvm](https://github.com/nvm-sh/nvm) or [pyenv](https://github.com/pyenv/pyenv) but for any language) it manages [dev tools](https://mise.en.dev/dev-tools/) like node, python, cmake, terraform, and [hundreds more](https://mise.en.dev/registry.html).
+- Like [direnv](https://github.com/direnv/direnv) it manages [environment variables](https://mise.en.dev/environments/) for different project directories.
+- Like [make](https://www.gnu.org/software/make/manual/make.html) it manages [tasks](https://mise.en.dev/tasks/) used to build and test projects.
 
 ## Demo
 
@@ -45,15 +45,15 @@ Note that calling `which node` gives us a real path to node, not a shim.
 
 It also shows that you can use `mise` to install and many other tools such as `jq`, `terraform`, or `go`.
 
-[![demo](./docs/tapes/demo.gif)](https://mise.jdx.dev/demo.html)
+[![demo](./docs/tapes/demo.gif)](https://mise.en.dev/demo.html)
 
-See [demo transcript](https://mise.jdx.dev/demo.html).
+See [demo transcript](https://mise.en.dev/demo.html).
 
 ## Quickstart
 
 ### Install mise
 
-See [Getting started](https://mise.jdx.dev/getting-started.html) for more options.
+See [Getting started](https://mise.en.dev/getting-started.html) for more options.
 
 ```sh-session
 $ curl https://mise.run | sh
@@ -96,7 +96,7 @@ $ go version
 go version go1.x.x macos/arm64
 ```
 
-See [dev tools](https://mise.jdx.dev/dev-tools/) for more examples.
+See [dev tools](https://mise.en.dev/dev-tools/) for more examples.
 
 ### Manage environment variables
 
@@ -112,7 +112,7 @@ $ echo $SOME_VAR
 bar
 ```
 
-Note that `mise` can also [load `.env` files](https://mise.jdx.dev/environments/#env-directives).
+Note that `mise` can also [load `.env` files](https://mise.en.dev/environments/#env-directives).
 
 ### Run tasks
 
@@ -128,7 +128,7 @@ $ mise run build
 building...
 ```
 
-See [tasks](https://mise.jdx.dev/tasks/) for more information.
+See [tasks](https://mise.en.dev/tasks/) for more information.
 
 ### Example mise project
 
@@ -173,11 +173,11 @@ mise install # install tools specified in mise.toml
 mise run deploy
 ```
 
-Find more examples in the [mise cookbook](https://mise.jdx.dev/mise-cookbook/).
+Find more examples in the [mise cookbook](https://mise.en.dev/mise-cookbook/).
 
 ## Full Documentation
 
-See [mise.jdx.dev](https://mise.jdx.dev)
+See [mise.en.dev](https://mise.en.dev)
 
 ## GitHub Issues & Discussions
 

SECURITY.md

@@ -20,9 +20,9 @@ the project. I only select dependencies with broad usage across the Rust communi
 I'm open to PRs or suggestions on reducing dependency count even at the cost of functionality because it will make
 mise more secure.
 
-## mise.jdx.dev
+## mise.en.dev
 
-mise.jdx.dev is the asset host for mise. It's used to host precompiled mise CLI binaries, and hosts a "[VERSION](https://mise.jdx.dev/VERSION)"
+mise.en.dev is the asset host for mise. It's used to host precompiled mise CLI binaries, and hosts a "[VERSION](https://mise.en.dev/VERSION)"
 which mise uses to occasionally check for a new version being released. Everything hosted there uses a single
 vendor to reduce surface area.
 
@@ -60,7 +60,7 @@ If you notice a tool offers security verification methods (gpg/slsa/cosign/minis
 
 ## `mise.lock`
 
-mise has support for [lockfiles](https://mise.jdx.dev/configuration/settings.html#lockfile) which will
+mise has support for [lockfiles](https://mise.en.dev/configuration/settings.html#lockfile) which will
 store/verify the checksum of tool tarballs. Committing this into your repository is a good way to ensure
 that the exact same version of a tool is installed across all developers and CI/CD systems.
 

cloudflare/workers/mise-run.js

@@ -22,16 +22,16 @@ async function handleRequest(request) {
   // Route based on path
   switch (path) {
     case "/":
-      targetUrl = "https://mise.jdx.dev/install.sh";
+      targetUrl = "https://mise.en.dev/install.sh";
       break;
     case "/zsh":
-      targetUrl = "https://mise.jdx.dev/mise.run/zsh";
+      targetUrl = "https://mise.en.dev/mise.run/zsh";
       break;
     case "/bash":
-      targetUrl = "https://mise.jdx.dev/mise.run/bash";
+      targetUrl = "https://mise.en.dev/mise.run/bash";
       break;
     case "/fish":
-      targetUrl = "https://mise.jdx.dev/mise.run/fish";
+      targetUrl = "https://mise.en.dev/mise.run/fish";
       break;
     default:
       return new Response("Not found", { status: 404 });

crates/aqua-registry/Cargo.toml

@@ -6,7 +6,7 @@ description = "Aqua registry backend for mise"
 authors = ["Jeff Dickey (@jdx)"]
 license = "MIT"
 repository = "https://github.com/jdx/mise"
-homepage = "https://mise.jdx.dev"
+homepage = "https://mise.en.dev"
 readme = "README.md"
 keywords = ["mise", "aqua", "registry", "package-manager"]
 categories = ["development-tools"]

crates/aqua-registry/README.md

@@ -1,6 +1,6 @@
 # aqua-registry
 
-Aqua registry backend for [mise](https://mise.jdx.dev).
+Aqua registry backend for [mise](https://mise.en.dev).
 
 This crate provides support for the [Aqua](https://aquaproj.github.io/) registry format, allowing mise to install tools from the Aqua ecosystem.
 
@@ -14,7 +14,7 @@ This crate provides support for the [Aqua](https://aquaproj.github.io/) registry
 
 ## Usage
 
-This crate is primarily used internally by mise. For more information about mise, visit [mise.jdx.dev](https://mise.jdx.dev).
+This crate is primarily used internally by mise. For more information about mise, visit [mise.en.dev](https://mise.en.dev).
 
 ## License
 

crates/mise-shim/src/main.rs

@@ -30,7 +30,7 @@ fn main() {
         Err(e) => {
             eprintln!("mise-shim: failed to execute mise: {e}");
             eprintln!("Ensure `mise` is installed and available on your PATH.");
-            eprintln!("See https://mise.jdx.dev for installation instructions.");
+            eprintln!("See https://mise.en.dev for installation instructions.");
             exit(1);
         }
     }

docs/cache-behavior.md

@@ -62,5 +62,5 @@ _.source = { file = "dynamic.sh", cacheable = false }
 
 ## Cache auto-pruning
 
-mise will automatically delete old files in its cache directory (configured with [`cache_prune_age`](https://mise.jdx.dev/configuration/settings.html#cache_prune_age)). Much of
+mise will automatically delete old files in its cache directory (configured with [`cache_prune_age`](https://mise.en.dev/configuration/settings.html#cache_prune_age)). Much of
 the contents are also ignored by mise if they are >24 hours old or a few days. For this reason, it's likely wasteful to store this directory in CI jobs.

docs/cli/activate.md

@@ -63,7 +63,7 @@ PATH="$HOME/.local/share/mise/shims:$PATH"
 ```
 
 `mise activate --shims` does not support all the features of `mise activate`.
-See <https://mise.jdx.dev/dev-tools/shims.html#shims-vs-path> for more information
+See <https://mise.en.dev/dev-tools/shims.html#shims-vs-path> for more information
 
 Examples:
 

docs/cli/set.md

@@ -9,7 +9,7 @@ Set environment variables in mise.toml
 By default, this command modifies `mise.toml` in the current directory.
 If multiple config files exist (e.g., both `mise.toml` and `mise.local.toml`),
 the lowest precedence file (`mise.toml`) will be used.
-See <https://mise.jdx.dev/configuration.html#target-file-for-write-operations>
+See <https://mise.en.dev/configuration.html#target-file-for-write-operations>
 
 Use `-E <env>` to create/modify environment-specific config files like `mise.<env>.toml`.
 

docs/cli/settings/set.md

@@ -9,7 +9,7 @@ Add/update a setting
 
 This modifies the contents of ~/.config/mise/config.toml by default.
 With `--local`, modifies the local config file instead.
-See <https://mise.jdx.dev/configuration.html#target-file-for-write-operations>
+See <https://mise.en.dev/configuration.html#target-file-for-write-operations>
 
 ## Arguments
 

docs/cli/tasks/add.md

@@ -7,7 +7,7 @@
 Create a new task
 
 Adds a task to the local mise.toml file.
-See <https://mise.jdx.dev/configuration.html#target-file-for-write-operations>
+See <https://mise.en.dev/configuration.html#target-file-for-write-operations>
 
 ## Arguments
 

docs/cli/tool-stub.md

@@ -16,7 +16,7 @@ tool = "node" version = "20.0.0" bin = "node"
 
 The stub will automatically install the specified tool version if missing and execute it with any arguments passed to the stub.
 
-For more information, see: <https://mise.jdx.dev/dev-tools/tool-stubs.html>
+For more information, see: <https://mise.en.dev/dev-tools/tool-stubs.html>
 
 ## Arguments
 

docs/cli/unuse.md

@@ -10,7 +10,7 @@ Removes installed tool versions from mise.toml
 By default, this will use the `mise.toml` file that has the tool defined.
 If multiple config files exist (e.g., both `mise.toml` and `mise.local.toml`),
 the lowest precedence file (`mise.toml`) will be used.
-See <https://mise.jdx.dev/configuration.html#target-file-for-write-operations>
+See <https://mise.en.dev/configuration.html#target-file-for-write-operations>
 
 In the following order:
 - If `--global` is set, it will use the global config file.

docs/cli/upgrade.md

@@ -11,7 +11,7 @@ By default, this keeps the range specified in mise.toml. So if you have node@20
 upgrade to the latest 20.x.x version available. See the `--bump` flag to use the latest version
 and bump the version in mise.toml.
 
-This will update mise.lock if it is enabled, see <https://mise.jdx.dev/configuration/settings.html#lockfile>
+This will update mise.lock if it is enabled, see <https://mise.en.dev/configuration/settings.html#lockfile>
 
 ## Arguments
 

docs/cli/use.md

@@ -11,7 +11,7 @@ This will install the tool version if it is not already installed.
 By default, this will use a `mise.toml` file in the current directory.
 If multiple config files exist (e.g., both `mise.toml` and `mise.local.toml`),
 the lowest precedence file (`mise.toml`) will be used.
-See <https://mise.jdx.dev/configuration.html#target-file-for-write-operations>
+See <https://mise.en.dev/configuration.html#target-file-for-write-operations>
 
 In the following order:
 - If `--global` is set, it will use the global config file.
@@ -93,7 +93,7 @@ e.g.: `mise use --pin node@20` will save 20.0.0 as the version
 Set `MISE_PIN=1` to make this the default behavior
 
 Consider using mise.lock as a better alternative to pinning in mise.toml:
-<https://mise.jdx.dev/configuration/settings.html#lockfile>
+<https://mise.en.dev/configuration/settings.html#lockfile>
 
 ### `--raw`
 

docs/configuration.md

@@ -299,9 +299,9 @@ See [Monorepo Tasks](/tasks/monorepo) for detailed usage and examples.
 
 ### `mise.toml` schema
 
-- You can find the JSON schema for `mise.toml` in [schema/mise.json](https://github.com/jdx/mise/blob/main/schema/mise.json) or at <https://mise.jdx.dev/schema/mise.json>.
+- You can find the JSON schema for `mise.toml` in [schema/mise.json](https://github.com/jdx/mise/blob/main/schema/mise.json) or at <https://mise.en.dev/schema/mise.json>.
 - Some editors can load it automatically to provide autocompletion and validation for when editing a `mise.toml` file ([VSCode](https://code.visualstudio.com/docs/languages/json#_json-schemas-and-settings), [IntelliJ](https://www.jetbrains.com/help/idea/json.html#ws_json_using_schemas), [neovim](https://github.com/b0o/SchemaStore.nvim), etc.). It is also available in the [JSON schema store](https://www.schemastore.org/).
-- Note that for `included tasks` (see [task configuration](/tasks/task-configuration), there is another schema: <https://mise.jdx.dev/schema/mise-task.json>)
+- Note that for `included tasks` (see [task configuration](/tasks/task-configuration), there is another schema: <https://mise.en.dev/schema/mise-task.json>)
 
 ## Global config: `~/.config/mise/config.toml`
 

docs/contributing.md

@@ -816,9 +816,9 @@ docker run -ti --rm ubuntu
 apt update -y
 apt install -y curl
 install -dm 755 /etc/apt/keyrings
-curl -fSso /etc/apt/keyrings/mise-archive-keyring.pub https://mise.jdx.dev/gpg-key.pub
+curl -fSso /etc/apt/keyrings/mise-archive-keyring.pub https://mise.en.dev/gpg-key.pub
 echo "deb [signed-by=/etc/apt/keyrings/mise-archive-keyring.pub arch=arm64] \
-https://mise.jdx.dev/deb stable main" >/etc/apt/sources.list.d/mise.list
+https://mise.en.dev/deb stable main" >/etc/apt/sources.list.d/mise.list
 apt update -y
 apt install -y mise
 mise -V

docs/dev-tools/shims.md

@@ -236,7 +236,7 @@ The obvious downside is that anytime one wants to use `mise` they need to prefix
 > work on mise yourself I would recommend working in a similar way and disabling `mise activate` or shims
 > while you are working on it.
 >
-> See [How I use mise](https://mise.jdx.dev/how-i-use-mise.html) for more information.
+> See [How I use mise](https://mise.en.dev/how-i-use-mise.html) for more information.
 
 :::
 

docs/faq.md

@@ -2,7 +2,7 @@
 
 ## I don't want to put a `mise.toml`/`.tool-versions` file into my project since git shows it as an untracked file
 
-Use [`mise.local.toml`](https://mise.jdx.dev/configuration.html#mise-toml) and put that into your global gitignore file. This file should never be committed.
+Use [`mise.local.toml`](https://mise.en.dev/configuration.html#mise-toml) and put that into your global gitignore file. This file should never be committed.
 
 If you really want to use a `mise.toml` or `.tool-versions`, here are 3 ways to make git ignore these files:
 
@@ -202,7 +202,7 @@ It handles daemon management with features like automatic restarts on failure, s
 
 In VSCode, many extensions will throw an "error spawn EINVAL" due to a [Node.js security fix](https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2#command-injection-via-args-parameter-of-child_processspawn-without-shell-option-enabled-on-windows-cve-2024-27980---high).
 
-The default `exe` shim mode should resolve this. If you're using an older mode, you can change [windows_shim_mode](https://mise.jdx.dev/configuration/settings.html#windows_shim_mode) to `exe`, `hardlink`, or `symlink`.
+The default `exe` shim mode should resolve this. If you're using an older mode, you can change [windows_shim_mode](https://mise.en.dev/configuration/settings.html#windows_shim_mode) to `exe`, `hardlink`, or `symlink`.
 
 ## What is the difference between `mise install` and `mise use`?
 

docs/getting-started.md

@@ -54,8 +54,8 @@ choco install mise
 ```sh
 sudo apt update -y && sudo apt install -y curl
 sudo install -dm 755 /etc/apt/keyrings
-curl -fSs https://mise.jdx.dev/gpg-key.pub | sudo tee /etc/apt/keyrings/mise-archive-keyring.asc 1> /dev/null
-echo "deb [signed-by=/etc/apt/keyrings/mise-archive-keyring.asc] https://mise.jdx.dev/deb stable main" | sudo tee /etc/apt/sources.list.d/mise.list
+curl -fSs https://mise.en.dev/gpg-key.pub | sudo tee /etc/apt/keyrings/mise-archive-keyring.asc 1> /dev/null
+echo "deb [signed-by=/etc/apt/keyrings/mise-archive-keyring.asc] https://mise.en.dev/deb stable main" | sudo tee /etc/apt/sources.list.d/mise.list
 sudo apt update -y
 sudo apt install -y mise
 ```