fix: Vfox Plugin Auto-Installation for Environment Directives by pose · Pull Request #8035 · jdx/mise

pose · 2026-02-06T18:20:21Z

Issue

On a clean setup, env modules backed by vfox can fail during config loading with:

Plugin directory not found ...

This happens because [env] module evaluation can run before the plugin directory exists.

Fix

Ensure plugin installation once in EnvResults::module() before invoking vfox hooks.
Keep module() flow as:
- ensure_installed(...)
- mise_env(...)
- mise_path(...)
Remove ineffective per-instance install cache from VfoxPlugin:
- dropped env_module_ensured
- removed ensure_installed_for_env_module wrapper
Simplify vfox hook methods:
- VfoxPlugin::mise_env() / mise_path() no longer take config
- no install side effects inside these methods
Normalize new e2e file mode to repo convention (100644, non-executable).

Why this approach

Fixes clean-install failures by guaranteeing plugin availability before hook execution.
Avoids duplicate install checks within one module resolution without introducing unnecessary caching state.
Keeps hook methods focused on hook execution and moves orchestration to module resolution.

Testing

Added: e2e/env/test_env_module_auto_install (uses real plugin URL and exercises auto-install path).
Verified with:
- mise run test:e2e e2e/env/test_env_module_auto_install
- mise run lint

gemini-code-assist · 2026-02-06T18:20:40Z

Summary of Changes

Hello @pose, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical issue where mise would fail to load vfox plugins specified in [env] directives on systems without pre-existing plugin installations. The core problem was a timing conflict, with environment directives attempting to use plugins before they were installed. The solution involves refactoring the plugin environment and path resolution methods to proactively ensure the vfox plugin is installed before its hooks are executed, thereby providing a more robust and user-friendly experience, especially in clean environments or CI/CD pipelines.

Highlights

Vfox Plugin Auto-Installation: Implemented automatic installation of vfox plugins when they are referenced in [env] directives within mise.toml, resolving failures on clean installations where plugin directories might not exist yet.
Configuration Parameter Propagation: Modified VfoxPlugin::mise_env and VfoxPlugin::mise_path methods to accept a config parameter, which is then passed through the call chain from EnvResults::resolve() to ensure proper context for plugin installation.
Early Plugin Installation: Ensured that self.ensure_installed() is called at the beginning of VfoxPlugin::mise_env and VfoxPlugin::mise_path to guarantee the plugin is available before its environment hooks are executed.
New End-to-End Test: Added a new end-to-end test (e2e/env/test_env_module_auto_install) to validate the correct behavior of vfox plugin auto-installation when used with environment directives.

Changelog

e2e/env/test_env_module_auto_install
- Added a new end-to-end test to verify vfox plugin auto-installation for environment directives.
src/config/env_directive/mod.rs
- Updated the call to Self::module to pass the config parameter.
src/config/env_directive/module.rs
- Modified EnvResults::module to accept config and pass it to VfoxPlugin::mise_env and VfoxPlugin::mise_path.
- Imported Config and Arc types.
src/plugins/vfox_plugin.rs
- Modified VfoxPlugin::mise_env and VfoxPlugin::mise_path to accept a config parameter.
- Added a call to self.ensure_installed() at the beginning of mise_env and mise_path to ensure the plugin is installed before use.

Activity

Identified and diagnosed a timing issue where vfox plugins were accessed before installation.
Implemented a solution to ensure vfox plugins are automatically installed when referenced in environment directives.
Developed a new end-to-end test to confirm the fix and validate the new auto-installation behavior.
Verified that all related tests continue to pass after the changes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request correctly fixes a timing issue where vfox plugins referenced in the [env] section would fail on a clean installation because they weren't installed yet. The solution involves passing the config object down to mise_env and mise_path to ensure plugins are installed before use. The changes are logical and well-described. I've added a couple of suggestions to improve test coverage and code maintainability.

gemini-code-assist · 2026-02-06T18:28:11Z

e2e/env/test_env_module_auto_install

+# Test that env modules work correctly with vfox plugins when referenced
+# in the [env] section, creating the plugin directory beforehand to simulate
+# a plugin that's already been "installed" by other means.
+# This tests the scenario where mise loads env directives with vfox plugins.


This test is a great start, but it doesn't fully cover the auto-installation scenario described in the issue. The test creates the plugin directory manually, which simulates a pre-existing plugin. The original bug occurred on a clean installation where the plugin directory did not exist.

To more accurately test the fix, consider adding a test case that:

Initializes a local git repository for a mock plugin.

Adds the plugin to [plugins] in mise.toml using the local git repository URL.

Ensures the plugin directory does not exist in $MISE_DATA_DIR/plugins.

Runs mise env and verifies that the plugin is automatically cloned and the environment is set up correctly.

I wasn't able to add that test since I couldn't find how to specify a local plugin in the mise.toml configuration. I tried using the file: scheme, but it was not recognizing it. I also tried using a map and changing the url of the map when using the http backend to a file, but that didn't fly either (mise.toml schema expects [plugins] entries to be strings). The following e2e test reproduces the issue but it requires a remote git repository URL which is more brittle:

#!/usr/bin/env bash export MISE_TRUSTED_CONFIG_PATHS="" AUTO_PLUGIN_DIR="$MISE_DATA_DIR/plugins/vfox-pulumi" cat >mise.toml <<EOF [env] _.vfox-pulumi = { module_path = "." } [tools] "vfox-pulumi:pulumi/pulumictl" = '0.0.50' [plugins] vfox-pulumi = "https://github.com/pulumi/vfox-pulumi" EOF cat > "go.mod" <<EOF module sample toolchain go 1.23.4 EOF OUTPUT=$(env mise trust && mise env -s bash 2>&1) EXIT_CODE=$? if [ $EXIT_CODE -ne 0 ]; then echo "FAILURE: mise env failed with exit code $EXIT_CODE" echo "Output: $OUTPUT" exit 1 fi if [ ! -d "$AUTO_PLUGIN_DIR" ]; then echo "FAILURE: Expected plugin directory to be auto-installed" echo "Expected directory: $AUTO_PLUGIN_DIR" exit 1 fi # # Verify the env variable was set correctly if echo "$OUTPUT" | grep -q "GO_VERSION_MISE=1.23.4"; then echo "SUCCESS: Plugin env module executed correctly" else echo "FAILURE: Expected GO_VERSION_MISE=1.23.4 in output" echo "Output: $OUTPUT" exit 1 fi

I verified that in main that script reproduces the "Plugin directory not found" error, whereas using the code from this PR, it retrieves and installs the plugin successfully.

src/plugins/vfox_plugin.rs

jdx

Code review — the fix is correct in principle (auto-install vfox plugins before env hooks run). A few issues:

1. Double ensure_installed per module invocation

module() calls mise_env() then mise_path() sequentially on the same plugin. Both now call ensure_installed_for_env_hook(). The second call is a no-op (the directory exists by then), but it still creates a MultiProgressReport, checks config for repo URLs, etc. Consider either:

Calling ensure_installed once in module() before both calls, or
Caching the installed state on the VfoxPlugin instance

2. ensure_installed_for_env_hook is unnecessary indirection

async fn ensure_installed_for_env_hook(&self, config: &Arc<Config>) -> Result<()> {
    self.ensure_installed(config, &MultiProgressReport::get(), false, false).await
}

This is a one-liner wrapper that hardcodes MultiProgressReport::get(). It doesn't add clarity — just inline the ensure_installed call at the two call sites (or better, once in module() as suggested above).

3. E2e test doesn't test auto-install

The test name is test_env_module_auto_install but it manually creates the plugin directory with mkdir -p and populates it. It never tests the actual auto-install path (cloning from a URL when the directory doesn't exist). It's testing "env modules work with a pre-existing plugin," which is what the existing tests already cover. To test the fix, the test should define the plugin in [plugins] with a URL and not pre-create the directory.

4. E2e test style

The test uses manual if/grep/echo patterns instead of the project's assert / assert_contains helpers from e2e/assert.sh. See other e2e tests for the expected pattern.

5. Minor: PR description is very verbose

The PR body includes full function signatures, explanations of the entire call chain, and copies of the code. A concise summary of the problem + fix is sufficient — reviewers can read the diff.

Overall the core fix (passing config through and calling ensure_installed) is the right approach. The main suggestion is to call ensure_installed once in module() rather than inside each vfox method, and to fix the e2e test to actually exercise the auto-install codepath.

This review was generated by AI (Claude).

jdx

Code review — the fix is correct in principle (auto-install vfox plugins before env hooks run). A few issues:

1. Double ensure_installed per module invocation

module() calls mise_env() then mise_path() sequentially on the same plugin. Both now call ensure_installed_for_env_hook(). The second call is a no-op (the directory exists by then), but it still creates a MultiProgressReport, checks config for repo URLs, etc. Consider either:

Calling ensure_installed once in module() before both calls, or
Caching the installed state on the VfoxPlugin instance

2. ensure_installed_for_env_hook is unnecessary indirection

async fn ensure_installed_for_env_hook(&self, config: &Arc<Config>) -> Result<()> {
    self.ensure_installed(config, &MultiProgressReport::get(), false, false).await
}

This is a one-liner wrapper that hardcodes MultiProgressReport::get(). It doesn't add clarity — just inline the ensure_installed call at the two call sites (or better, once in module() as suggested above).

3. E2e test doesn't test auto-install

The test name is test_env_module_auto_install but it manually creates the plugin directory with mkdir -p and populates it. It never tests the actual auto-install path (cloning from a URL when the directory doesn't exist). It's testing "env modules work with a pre-existing plugin," which is what the existing tests already cover. To test the fix, the test should define the plugin in [plugins] with a URL and not pre-create the directory.

4. E2e test style

The test uses manual if/grep/echo patterns instead of the project's assert / assert_contains helpers from e2e/assert.sh. See other e2e tests for the expected pattern.

This review was generated by AI (Claude).

jdx · 2026-02-10T02:19:31Z

Re: point #3 — for the e2e test, you could use https://github.com/jdx/mise-env-sample as a real vfox plugin to test the auto-install path. Define it in [plugins] with that URL, reference it in [env], and don't pre-create the directory. That way the test actually exercises the ensure_installed codepath.

This comment was generated by AI (Claude).

jdx · 2026-02-10T02:20:07Z

good enhancement @pose! great to hear from you as well!

pose · 2026-02-10T09:21:17Z

good enhancement @pose! great to hear from you as well!

Thanks! Great to hear from you too :)

Addressed PR Feedback

✅ 1. Double ensure_installed per module invocation
✅ 2. ensure_installed_for_env_hook is unnecessary indirection

The double-ensure issue has been addressed while preserving call-site safety and layering:

module() still calls mise_env() then mise_path(), but installation is now ensured only once per VfoxPlugin instance.
This removes repeated overhead on the second call (progress/report setup and repo/config checks).
A separate caller-invoked init step is no longer required before mise_env() / mise_path(), which reduces misuse risk.
MultiProgressReport remains confined to plugin code and is not pulled into config/env_directive.
Constructor-time installation in VfoxPlugin::new was considered, but installation is async/fallible and side-effectful, so that would require a broader API redesign.

✅ 3. E2e test doesn't test auto-install: Used jdx/mise-env-sample as a real vfox plugin to test the auto-install path. Verified test effectively fails in main, but passes using the PR branch.
✅ 4. E2e test style: Adopted suggested helpers.
✅ 5. Minor: PR description is very verbose

jdx

This review is AI-generated.

Overall this looks good — real bug fix for a real problem on clean setups. Two notes:

1. env_module_ensured cache doesn't help here

VfoxPlugin is constructed fresh every time module() is called (module.rs:20):

let plugin = VfoxPlugin::new(name, path.clone());

So the AsyncMutex<bool> will always start as false — the per-instance cache never survives between calls. Within a single module() call, ensure_installed gets called twice (once for mise_env, once for mise_path), but since ensure_installed already short-circuits when self.plugin_path.exists(), the second call is cheap anyway.

I'd suggest either:

Calling ensure_installed once in module() before both mise_env/mise_path calls, or
Dropping the env_module_ensured field entirely and calling ensure_installed directly in each method

Both are simpler and avoid the unused tokio::sync::Mutex dependency.

2. E2E test file mode

The new test file is 100755 (executable). Convention in this repo is that e2e tests are not chmod'd executable.

pose · 2026-02-10T15:08:08Z

Addressed, thanks for the review.

Changes made

Removed ineffective per-instance cache
- Dropped env_module_ensured and its AsyncMutex<bool> from VfoxPlugin.
- Removed ensure_installed_for_env_module indirection.
Ensure install once per module resolution
- In src/config/env_directive/module.rs, module() now calls:
- plugin.ensure_installed(config, &MultiProgressReport::get(), false, false).await?
- before calling mise_env() and mise_path().
Simplified vfox env/path methods
- VfoxPlugin::mise_env() / mise_path() no longer take config and no longer perform install side effects internally.
Fixed e2e file mode
- Updated e2e/env/test_env_module_auto_install from 100755 to 100644 to match repo convention.

This keeps install orchestration in one place (module()), avoids double ensure calls within a single module invocation, and removes the unused async mutex path.

Note: this response was AI-generated.

## Issue On a clean setup, env modules backed by vfox can fail during config loading with: `Plugin directory not found ...` This happens because `[env]` module evaluation can run before the plugin directory exists. ## Fix - Pass `config` into `VfoxPlugin::mise_env()` / `VfoxPlugin::mise_path()` so installation can be ensured at hook-execution time. - Ensure the plugin is installed before running vfox env/path hooks. - Avoid duplicate ensure overhead when `module()` calls `mise_env()` then `mise_path()`: - ensure state is cached per `VfoxPlugin` instance - second call returns early instead of repeating setup work - Keep call sites simple: `module.rs` does not need an explicit pre-init call. ## Why this approach - Prevents the clean-install failure path. - Preserves API ergonomics (no “remember to initialize first” requirement). - Keeps progress/reporting concerns in the plugin layer rather than `config/env_directive`. ## Testing - Added: `e2e/env/test_env_module_auto_install` - Verifiev-module behavior and existing related e2e coverage: - `e2e/env/test_env_module_cmd_exec_tools` - other env e2e tests via the normal suite

Ensure vfox plugins are installed once in env module resolution, remove ineffective per-instance install caching, and normalize the new e2e test file mode to match repository conventions. Co-authored-by: Cursor <cursoragent@cursor.com>

@ctaintor

### 🚀 Features - **(activate)** add shims directory as fallback when auto-install is enabled by @ctaintor in [#8106](#8106) - **(env)** add `tools` variable to tera template context by @jdx in [#8108](#8108) - **(set)** add --stdin flag for multiline environment variables by @jdx in [#8110](#8110) ### 🐛 Bug Fixes - **(backend)** improve conda patchelf and dependency resolution for complex packages by @jdx in [#8087](#8087) - **(ci)** fix validate-new-tools grep pattern for test field by @jdx in [#8100](#8100) - **(config)** make MISE_OFFLINE work correctly by gracefully skipping network calls by @jdx in [#8109](#8109) - **(github)** skip v prefix for "latest" version by @jdx in [#8105](#8105) - **(gitlab)** resolve tool options from config for aliased tools by @jdx in [#8084](#8084) - **(install)** use version_expr for Flutter to fix version resolution by @jdx in [#8081](#8081) - **(registry)** add Linux support for tuist by @fortmarek in [#8102](#8102) - **(release)** write release notes to file instead of capturing stdout by @jdx in [#8086](#8086) - **(upgrade)** tools are not uninstalled properly due to outdated symlink by @roele in [#8099](#8099) - **(upgrade)** ensure uninstallation failure does not leave invalid symlinks by @roele in [#8101](#8101) - SLSA for in-toto statement with no signatures by @gerhard in [#8094](#8094) - Vfox Plugin Auto-Installation for Environment Directives by @pose in [#8035](#8035) ### 📚 Documentation - use mise activate for PowerShell in getting-started by @rileychh in [#8112](#8112) ### 📦 Registry - add conda backend for mysql by @jdx in [#8080](#8080) - add conda backends for 10 asdf-only tools by @jdx in [#8083](#8083) - added podman-tui by @tony-sol in [#8098](#8098) ### Chore - sort settings.toml alphabetically and add test by @jdx in [#8111](#8111) ### New Contributors - @ctaintor made their first contribution in [#8106](#8106) - @rileychh made their first contribution in [#8112](#8112) - @fortmarek made their first contribution in [#8102](#8102) - @pose made their first contribution in [#8035](#8035) - @gerhard made their first contribution in [#8094](#8094) ## 📦 Aqua Registry Updates #### New Packages (2) - [`entireio/cli`](https://github.com/entireio/cli) - [`rmitchellscott/reManager`](https://github.com/rmitchellscott/reManager) #### Updated Packages (1) - [`atuinsh/atuin`](https://github.com/atuinsh/atuin)

@ctaintor

### 🚀 Features - **(activate)** add shims directory as fallback when auto-install is enabled by @ctaintor in [#8106](#8106) - **(env)** add `tools` variable to tera template context by @jdx in [#8108](#8108) - **(set)** add --stdin flag for multiline environment variables by @jdx in [#8110](#8110) ### 🐛 Bug Fixes - **(backend)** improve conda patchelf and dependency resolution for complex packages by @jdx in [#8087](#8087) - **(ci)** fix validate-new-tools grep pattern for test field by @jdx in [#8100](#8100) - **(config)** make MISE_OFFLINE work correctly by gracefully skipping network calls by @jdx in [#8109](#8109) - **(github)** skip v prefix for "latest" version by @jdx in [#8105](#8105) - **(gitlab)** resolve tool options from config for aliased tools by @jdx in [#8084](#8084) - **(install)** use version_expr for Flutter to fix version resolution by @jdx in [#8081](#8081) - **(registry)** add Linux support for tuist by @fortmarek in [#8102](#8102) - **(release)** write release notes to file instead of capturing stdout by @jdx in [#8086](#8086) - **(upgrade)** tools are not uninstalled properly due to outdated symlink by @roele in [#8099](#8099) - **(upgrade)** ensure uninstallation failure does not leave invalid symlinks by @roele in [#8101](#8101) - SLSA for in-toto statement with no signatures by @gerhard in [#8094](#8094) - Vfox Plugin Auto-Installation for Environment Directives by @pose in [#8035](#8035) ### 📚 Documentation - use mise activate for PowerShell in getting-started by @rileychh in [#8112](#8112) ### 📦 Registry - add conda backend for mysql by @jdx in [#8080](#8080) - add conda backends for 10 asdf-only tools by @jdx in [#8083](#8083) - added podman-tui by @tony-sol in [#8098](#8098) ### Chore - sort settings.toml alphabetically and add test by @jdx in [#8111](#8111) ### New Contributors - @ctaintor made their first contribution in [#8106](#8106) - @rileychh made their first contribution in [#8112](#8112) - @fortmarek made their first contribution in [#8102](#8102) - @pose made their first contribution in [#8035](#8035) - @gerhard made their first contribution in [#8094](#8094) ## 📦 Aqua Registry Updates #### New Packages (2) - [`entireio/cli`](https://github.com/entireio/cli) - [`rmitchellscott/reManager`](https://github.com/rmitchellscott/reManager) #### Updated Packages (1) - [`atuinsh/atuin`](https://github.com/atuinsh/atuin)

## Issue On a clean setup, env modules backed by vfox can fail during config loading with: `Plugin directory not found ...` This happens because `[env]` module evaluation can run before the plugin directory exists. ## Fix - Ensure plugin installation once in `EnvResults::module()` before invoking vfox hooks. - Keep `module()` flow as: - `ensure_installed(...)` - `mise_env(...)` - `mise_path(...)` - Remove ineffective per-instance install cache from `VfoxPlugin`: - dropped `env_module_ensured` - removed `ensure_installed_for_env_module` wrapper - Simplify vfox hook methods: - `VfoxPlugin::mise_env()` / `mise_path()` no longer take `config` - no install side effects inside these methods - Normalize new e2e file mode to repo convention (`100644`, non-executable). ## Why this approach - Fixes clean-install failures by guaranteeing plugin availability before hook execution. - Avoids duplicate install checks within one module resolution without introducing unnecessary caching state. - Keeps hook methods focused on hook execution and moves orchestration to module resolution. ## Testing - Added: `e2e/env/test_env_module_auto_install` (uses real plugin URL and exercises auto-install path). - Verified with: - `mise run test:e2e e2e/env/test_env_module_auto_install` - `mise run lint` --------- Co-authored-by: Cursor <cursoragent@cursor.com>

@ctaintor

### 🚀 Features - **(activate)** add shims directory as fallback when auto-install is enabled by @ctaintor in [jdx#8106](jdx#8106) - **(env)** add `tools` variable to tera template context by @jdx in [jdx#8108](jdx#8108) - **(set)** add --stdin flag for multiline environment variables by @jdx in [jdx#8110](jdx#8110) ### 🐛 Bug Fixes - **(backend)** improve conda patchelf and dependency resolution for complex packages by @jdx in [jdx#8087](jdx#8087) - **(ci)** fix validate-new-tools grep pattern for test field by @jdx in [jdx#8100](jdx#8100) - **(config)** make MISE_OFFLINE work correctly by gracefully skipping network calls by @jdx in [jdx#8109](jdx#8109) - **(github)** skip v prefix for "latest" version by @jdx in [jdx#8105](jdx#8105) - **(gitlab)** resolve tool options from config for aliased tools by @jdx in [jdx#8084](jdx#8084) - **(install)** use version_expr for Flutter to fix version resolution by @jdx in [jdx#8081](jdx#8081) - **(registry)** add Linux support for tuist by @fortmarek in [jdx#8102](jdx#8102) - **(release)** write release notes to file instead of capturing stdout by @jdx in [jdx#8086](jdx#8086) - **(upgrade)** tools are not uninstalled properly due to outdated symlink by @roele in [jdx#8099](jdx#8099) - **(upgrade)** ensure uninstallation failure does not leave invalid symlinks by @roele in [jdx#8101](jdx#8101) - SLSA for in-toto statement with no signatures by @gerhard in [jdx#8094](jdx#8094) - Vfox Plugin Auto-Installation for Environment Directives by @pose in [jdx#8035](jdx#8035) ### 📚 Documentation - use mise activate for PowerShell in getting-started by @rileychh in [jdx#8112](jdx#8112) ### 📦 Registry - add conda backend for mysql by @jdx in [jdx#8080](jdx#8080) - add conda backends for 10 asdf-only tools by @jdx in [jdx#8083](jdx#8083) - added podman-tui by @tony-sol in [jdx#8098](jdx#8098) ### Chore - sort settings.toml alphabetically and add test by @jdx in [jdx#8111](jdx#8111) ### New Contributors - @ctaintor made their first contribution in [jdx#8106](jdx#8106) - @rileychh made their first contribution in [jdx#8112](jdx#8112) - @fortmarek made their first contribution in [jdx#8102](jdx#8102) - @pose made their first contribution in [jdx#8035](jdx#8035) - @gerhard made their first contribution in [jdx#8094](jdx#8094) ## 📦 Aqua Registry Updates #### New Packages (2) - [`entireio/cli`](https://github.com/entireio/cli) - [`rmitchellscott/reManager`](https://github.com/rmitchellscott/reManager) #### Updated Packages (1) - [`atuinsh/atuin`](https://github.com/atuinsh/atuin)

@ctaintor

### 🚀 Features - **(activate)** add shims directory as fallback when auto-install is enabled by @ctaintor in [jdx#8106](jdx#8106) - **(env)** add `tools` variable to tera template context by @jdx in [jdx#8108](jdx#8108) - **(set)** add --stdin flag for multiline environment variables by @jdx in [jdx#8110](jdx#8110) ### 🐛 Bug Fixes - **(backend)** improve conda patchelf and dependency resolution for complex packages by @jdx in [jdx#8087](jdx#8087) - **(ci)** fix validate-new-tools grep pattern for test field by @jdx in [jdx#8100](jdx#8100) - **(config)** make MISE_OFFLINE work correctly by gracefully skipping network calls by @jdx in [jdx#8109](jdx#8109) - **(github)** skip v prefix for "latest" version by @jdx in [jdx#8105](jdx#8105) - **(gitlab)** resolve tool options from config for aliased tools by @jdx in [jdx#8084](jdx#8084) - **(install)** use version_expr for Flutter to fix version resolution by @jdx in [jdx#8081](jdx#8081) - **(registry)** add Linux support for tuist by @fortmarek in [jdx#8102](jdx#8102) - **(release)** write release notes to file instead of capturing stdout by @jdx in [jdx#8086](jdx#8086) - **(upgrade)** tools are not uninstalled properly due to outdated symlink by @roele in [jdx#8099](jdx#8099) - **(upgrade)** ensure uninstallation failure does not leave invalid symlinks by @roele in [jdx#8101](jdx#8101) - SLSA for in-toto statement with no signatures by @gerhard in [jdx#8094](jdx#8094) - Vfox Plugin Auto-Installation for Environment Directives by @pose in [jdx#8035](jdx#8035) ### 📚 Documentation - use mise activate for PowerShell in getting-started by @rileychh in [jdx#8112](jdx#8112) ### 📦 Registry - add conda backend for mysql by @jdx in [jdx#8080](jdx#8080) - add conda backends for 10 asdf-only tools by @jdx in [jdx#8083](jdx#8083) - added podman-tui by @tony-sol in [jdx#8098](jdx#8098) ### Chore - sort settings.toml alphabetically and add test by @jdx in [jdx#8111](jdx#8111) ### New Contributors - @ctaintor made their first contribution in [jdx#8106](jdx#8106) - @rileychh made their first contribution in [jdx#8112](jdx#8112) - @fortmarek made their first contribution in [jdx#8102](jdx#8102) - @pose made their first contribution in [jdx#8035](jdx#8035) - @gerhard made their first contribution in [jdx#8094](jdx#8094) ## 📦 Aqua Registry Updates #### New Packages (2) - [`entireio/cli`](https://github.com/entireio/cli) - [`rmitchellscott/reManager`](https://github.com/rmitchellscott/reManager) #### Updated Packages (1) - [`atuinsh/atuin`](https://github.com/atuinsh/atuin)

gemini-code-assist bot reviewed Feb 6, 2026

View reviewed changes

pose force-pushed the pose/fixes/plugin-folder-not-found branch 2 times, most recently from 0af4690 to 5fe0839 Compare February 9, 2026 17:24

pose marked this pull request as ready for review February 9, 2026 17:38

jdx reviewed Feb 10, 2026

View reviewed changes

pose force-pushed the pose/fixes/plugin-folder-not-found branch from 4f157b9 to db5a29e Compare February 10, 2026 09:20

jdx reviewed Feb 10, 2026

View reviewed changes

pose force-pushed the pose/fixes/plugin-folder-not-found branch from cfdba72 to 6398d85 Compare February 10, 2026 15:07

pose force-pushed the pose/fixes/plugin-folder-not-found branch from 6398d85 to 2d18cf3 Compare February 10, 2026 15:09

pose and others added 3 commits February 10, 2026 16:17

Fix shellcheck lint issue

f6e6827

pose force-pushed the pose/fixes/plugin-folder-not-found branch from 2d18cf3 to f33d701 Compare February 10, 2026 16:17

jdx merged commit dd78b4b into jdx:main Feb 10, 2026
33 checks passed

mise-en-dev mentioned this pull request Feb 10, 2026

chore: release 2026.2.10 #8082

Merged

pose deleted the pose/fixes/plugin-folder-not-found branch February 11, 2026 10:13

BrewTestBot mentioned this pull request Feb 12, 2026

mise 2026.2.10 Homebrew/homebrew-core#267117

Merged

Uh oh!

Conversation

pose commented Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Issue

Fix

Why this approach

Testing

Uh oh!

gemini-code-assist bot commented Feb 6, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 6, 2026

Choose a reason for hiding this comment

Uh oh!

pose Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

jdx left a comment

Choose a reason for hiding this comment

Uh oh!

jdx left a comment

Choose a reason for hiding this comment

Uh oh!

jdx commented Feb 10, 2026

Uh oh!

jdx commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pose commented Feb 10, 2026

Addressed PR Feedback

Uh oh!

jdx left a comment

Choose a reason for hiding this comment

Uh oh!

pose commented Feb 10, 2026

Changes made

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

pose commented Feb 6, 2026 •

edited

Loading

jdx commented Feb 10, 2026 •

edited

Loading