Skip to content

chore: release 2026.3.4#8469

Merged
mise-en-dev merged 1 commit intomainfrom
release
Mar 7, 2026
Merged

chore: release 2026.3.4#8469
mise-en-dev merged 1 commit intomainfrom
release

Conversation

@mise-en-dev
Copy link
Copy Markdown
Collaborator

@mise-en-dev mise-en-dev commented Mar 4, 2026

🚀 Features

  • (github) keep exe extensions on Windows by @iki in #8424
  • (task) add interactive field for exclusive terminal access by @jdx in #8491
  • add header comment to generated lockfiles by @ivy in #8481
  • runtime musl/glibc detection for correct libc variant selection by @jdx in #8490

🐛 Bug Fixes

  • (github) use registry platform options during install by @jdx in #8492
  • (http) store tool opts as native TOML to fix platform switching by @jdx in #8448
  • (installer) error if MISE_INSTALL_PATH is a directory by @jdx in #8468
  • (prepare) resolve sources/outputs relative to dir when set by @jdx in #8472
  • (ruby) fetch precompiled binary by release tag instead of listing all releases by @jdx in #8488
  • (schema) support structured objects in task depends by @risu729 in #8463
  • (task) replace println!/eprintln! with calm_io in task output macros by @vmaleze in #8485
  • handle scoped npm package names without backend prefix by @jdx in #8477

📦️ Dependency Updates

  • update ghcr.io/jdx/mise:copr docker digest to c485c4c by @renovate[bot] in #8484
  • update ghcr.io/jdx/mise:alpine docker digest to 8118bc7 by @renovate[bot] in #8483

📦 Registry

New Contributors

📦 Aqua Registry Updates

New Packages (5)

Updated Packages (6)

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 performs a routine release of mise version 2026.3.4. The primary change in this release is the inclusion of a bug fix that addresses an installer error related to the MISE_INSTALL_PATH environment variable, ensuring smoother installations.

Highlights

  • Version Bump: Updated the mise project version from 2026.3.3 to 2026.3.4 across all relevant configuration and documentation files.
  • Bug Fix: Included a fix for an installer issue where mise would error if MISE_INSTALL_PATH was specified as an existing directory.
Changelog
  • CHANGELOG.md
    • Added entry for version 2026.3.4 including a bug fix for the installer.
    • Updated the version link to compare v2026.3.3 with v2026.3.4.
  • Cargo.lock
    • Updated the mise package version to 2026.3.4.
  • Cargo.toml
    • Updated the mise package version to 2026.3.4.
  • README.md
    • Updated the displayed mise version in the example output to 2026.3.4.
  • completions/_mise
    • Updated the temporary spec file name to include the new version 2026.3.4.
  • completions/mise.bash
    • Updated the temporary spec file name to include the new version 2026.3.4.
  • completions/mise.fish
    • Updated the temporary spec file name to include the new version 2026.3.4.
  • completions/mise.ps1
    • Updated the temporary spec file name to include the new version 2026.3.4.
  • default.nix
    • Updated the mise package version to 2026.3.4.
  • packaging/rpm/mise.spec
    • Updated the mise package version to 2026.3.4.
  • snapcraft.yaml
    • Updated the mise package version to 2026.3.4.
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.

Footnotes

  1. 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.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 4, 2026

Greptile Summary

This is the automated release PR for mise 2026.3.4 (released 2026-03-07), bumping the version across all packaging manifests (Cargo.toml, Cargo.lock, default.nix, snapcraft.yaml, packaging/rpm/mise.spec, completions, and README.md) and updating the aqua-registry crate to 2026.3.1.

Key changes bundled in this release:

  • New features: Windows .exe extension preservation for GitHub backend, interactive task field for exclusive terminal access, lockfile header comments, and runtime musl/glibc detection for libc variant selection.
  • Bug fixes: Registry platform options during install, native TOML storage for tool opts, installer directory guard for MISE_INSTALL_PATH, dir-relative sources/outputs resolution, Ruby precompiled binary fetching by release tag, npm scoped package name handling, and task output macro replaced with calm_io.
  • Aqua registry: 5 new packages (datadog-labs/pup, k1LoW/mo, rtk-ai/rtk, suzuki-shunsuke/docfresh, yashikota/exiftool-go) and 6 updated packages; the most notable change is a complete restructure of both mozilla/sccache and cloudflare/cloudflared registries to use version-descending constraint ordering with proper ARM support and modern checksum verification, replacing the old ascending >= approach.
  • All version references are consistent across every packaging file.

Confidence Score: 5/5

  • This release PR is safe to merge — all changes are automated version bumps and curated registry updates consistent with the project's release process.
  • This is a standard release PR generated by the mise-en-dev bot. All version strings are consistently updated across every packaging manifest. The aqua registry YAML restructurings (especially sccache and cloudflared) follow correct constraint-ordering semantics, and new packages include proper checksum/cosign verification. No logic changes to the core Rust codebase are present in this diff.
  • No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[sccache version requested] --> B{Version == v0.3.2?}
    B -- Yes --> C[no_asset]
    B -- No --> D{Version in v0.5.1 or v0.6.0?}
    D -- Yes --> E[tar.gz, limited OS support\nwindows_arm_emulation]
    D -- No --> F{Version == v0.13.0?}
    F -- Yes --> G[tar.gz, linux/darwin/arm64\nspecial darwin override]
    F -- No --> H{semver <= 0.2.13?}
    H -- Yes --> I[error: version too old]
    H -- No --> J{semver <= 0.3.1?}
    J -- Yes --> K[tar.gz, musl linux\nno ARM darwin]
    J -- No --> L{semver <= 0.4.0-pre.1?}
    L -- Yes --> M[tar.gz, darwin/windows/amd64\nARM darwin override]
    L -- No --> N{semver <= 0.8.1?}
    N -- Yes --> O[tar.gz, all platforms\nARM support added]
    N -- No --> P[true: latest format\ntar.gz, all platforms\nfull ARM support]
Loading

Last reviewed commit: 907b89a

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request prepares for the release of version 2026.3.4, primarily through version bumps in files like Cargo.toml, CHANGELOG.md, README.md, and shell completion scripts. While the version updates are consistent, a security vulnerability has been identified: the completion scripts for zsh, bash, fish, and powershell use predictable filenames in a world-writable temporary directory to cache usage specs. This pattern is vulnerable to local symlink attacks, which could lead to arbitrary file overwrite. It is recommended to move these temporary files to a user-specific directory such as ~/.cache/mise/completions.

fi

local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_3_3.spec"
local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_3_4.spec"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-medium medium

The completion script uses a predictable filename in a world-writable directory (/tmp or $TMPDIR) to store a spec file. This is vulnerable to a local symlink attack, where an attacker could create a symlink at this path pointing to a sensitive file, causing mise usage to overwrite it when completions are triggered. Consider using a user-specific directory like ~/.cache/mise/completions instead.

local cur prev words cword was_split comp_args
_comp_initialize -n : -- "$@" || return
local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_3_3.spec"
local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_3_4.spec"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-medium medium

The completion script uses a predictable filename in a world-writable directory (/tmp or $TMPDIR) to store a spec file. This is vulnerable to a local symlink attack, where an attacker could create a symlink at this path pointing to a sensitive file, causing mise usage to overwrite it when completions are triggered. Consider using a user-specific directory like ~/.cache/mise/completions instead.

end
set -l tmpdir (if set -q TMPDIR; echo $TMPDIR; else; echo /tmp; end)
set -l spec_file "$tmpdir/usage__usage_spec_mise_2026_3_3.spec"
set -l spec_file "$tmpdir/usage__usage_spec_mise_2026_3_4.spec"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-medium medium

The completion script uses a predictable filename in a world-writable directory (/tmp or /tmp by default) to store a spec file. This is vulnerable to a local symlink attack, where an attacker could create a symlink at this path pointing to a sensitive file, causing mise usage to overwrite it when completions are triggered. Consider using a user-specific directory like ~/.cache/mise/completions instead.


$tmpDir = if ($env:TEMP) { $env:TEMP } else { [System.IO.Path]::GetTempPath() }
$specFile = Join-Path $tmpDir "usage__usage_spec_mise_2026_3_3.kdl"
$specFile = Join-Path $tmpDir "usage__usage_spec_mise_2026_3_4.kdl"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-medium medium

The completion script uses a predictable filename in a temporary directory to store a spec file. This is vulnerable to a local symlink attack, where an attacker could create a symlink at this path pointing to a sensitive file, causing mise usage to overwrite it when completions are triggered. Consider using a user-specific directory like ~/.cache/mise/completions instead.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 4, 2026

Hyperfine Performance

mise x -- echo

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.3.3 x -- echo 23.5 ± 0.5 22.7 28.7 1.00
mise x -- echo 23.8 ± 0.7 22.6 28.9 1.02 ± 0.03

mise env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.3.3 env 25.0 ± 0.9 23.1 30.9 1.05 ± 0.05
mise env 23.9 ± 0.6 22.7 26.5 1.00

mise hook-env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.3.3 hook-env 24.6 ± 0.5 23.4 26.4 1.02 ± 0.04
mise hook-env 24.0 ± 0.7 22.7 26.3 1.00

mise ls

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.3.3 ls 23.0 ± 0.6 22.3 29.4 1.00
mise ls 23.2 ± 0.7 22.1 25.8 1.01 ± 0.04

xtasks/test/perf

Command mise-2026.3.3 mise Variance
install (cached) 153ms 150ms +2%
ls (cached) 83ms 82ms +1%
bin-paths (cached) 85ms 84ms +1%
task-ls (cached) 822ms 832ms -1%

@mise-en-dev mise-en-dev enabled auto-merge (squash) March 5, 2026 10:14
@mise-en-dev mise-en-dev force-pushed the release branch 14 times, most recently from f9e3efc to 3686c6e Compare March 7, 2026 03:59
@mise-en-dev mise-en-dev merged commit 6d69c1f into main Mar 7, 2026
62 of 63 checks passed
@mise-en-dev mise-en-dev deleted the release branch March 7, 2026 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant