Skip to content

chore: release 2026.3.13#8719

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

chore: release 2026.3.13#8719
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 23, 2026

🐛 Bug Fixes

  • (env) improve hook-env watch_files tracking and early-exits by @rpendleton in #8716
  • (install) create runtime symlinks in system/shared install directories by @jdx in #8722
  • apply --silent flag to global settings to suppress output by @nkakouros in #8720

📦️ Dependency Updates

  • ignore RUSTSEC-2026-0066 astral-tokio-tar advisory by @jdx in #8723

📦 Registry

New Contributors

📦 Aqua Registry Updates

Updated Packages (1)

@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 is a routine version bump for the mise tool. It updates the version number in various configuration and documentation files to reflect the new release. This ensures consistency across the project and provides users with accurate version information.

Highlights

  • Version Bump: This PR increments the mise version from 2026.3.12 to 2026.3.13 across multiple files.
  • File Updates: The changes include updates to Cargo.toml, Cargo.lock, README.md, CHANGELOG.md, completion scripts, default.nix, mise.spec, and snapcraft.yaml.
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.

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 23, 2026

Greptile Summary

This is a routine release bump PR from 2026.3.12 to 2026.3.13, updating version strings consistently across all packaging manifests (Cargo.toml, Cargo.lock, default.nix, snapcraft.yaml, packaging/rpm/mise.spec), shell completion scripts, and the README. The only substantive code change is in the aqua-registry astral-sh/ty package definition.

Key changes:

  • Version bumped to 2026.3.13 across all packaging and distribution files.
  • Shell completion spec-cache filenames updated to include the new version string (zsh, bash, fish, PowerShell).
  • astral-sh/ty registry entry updated with two improvements:
    • A new version_constraint: semver("<= 0.0.23") override is added to handle older ty releases that pre-date GitHub artifact attestations — these use only checksum verification.
    • github_artifact_attestations (signer workflow astral-sh/ty/.github/workflows/release.yml) is added to the catch-all "true" block for all newer releases.
  • aqua-registry sub-crate bumped from 2026.3.7 to 2026.3.8 accordingly.

The registry.yaml structure is internally consistent: the legacy <= 0.0.23 block mirrors the new block in asset layout and checksum config, simply omitting attestation verification that didn't exist in those older releases.

Confidence Score: 5/5

  • Safe to merge — all changes are mechanical version bumps plus a well-structured aqua-registry improvement.
  • All version strings are incremented consistently across every packaging file. The only non-trivial change (the ty registry.yaml) correctly splits old attestation-less versions from newer attested ones using ordered version_constraint blocks, and the legacy block structure is an exact mirror of the existing block. No logic regressions, no missing fields, and no inconsistencies were found.
  • No files require special attention.

Important Files Changed

Filename Overview
CHANGELOG.md Added 2026.3.13 changelog entry covering bug fixes, dependency updates, registry additions, and aqua registry updates — content accurately mirrors the PR description.
Cargo.toml Version bumped from 2026.3.12 to 2026.3.13, consistent with all other packaging files.
crates/aqua-registry/aqua-registry/pkgs/astral-sh/ty/registry.yaml Added version_override for semver <= 0.0.23 (no attestations) and added github_artifact_attestations to the catch-all "true" block for newer releases; structure is internally consistent.
completions/_mise Spec file cache path updated from 2026_3_12 to 2026_3_13 — routine version bump in zsh completion script.
crates/aqua-registry/Cargo.toml aqua-registry sub-crate version bumped from 2026.3.7 to 2026.3.8 to reflect the ty registry update.
default.nix Nix package version bumped to 2026.3.13.
packaging/rpm/mise.spec RPM spec version bumped to 2026.3.13.
snapcraft.yaml Snap package version bumped to 2026.3.13.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[aqua resolves astral-sh/ty version] --> B{version_constraint check}
    B -->|semver <= 0.0.23| C[Use legacy asset config\nNo attestation check]
    B -->|all other versions 'true'| D[Use current asset config\n+ github_artifact_attestations]
    C --> E[Asset: ty-Arch-OS.tar.gz\nChecksum: .sha256 from GitHub release]
    D --> F[Asset: ty-Arch-OS.tar.gz\nChecksum: .sha256 from GitHub release\nAttestation: astral-sh/ty release.yml]
    E --> G{goos == windows?}
    F --> H{goos == windows?}
    G -->|yes| I[Override: .zip format\nfiles: name=ty]
    G -->|no| J[tar.gz\nfiles: src=ty-Arch-OS/ty]
    H -->|yes| K[Override: .zip format\nfiles: name=ty]
    H -->|no| L[tar.gz\nfiles: src=ty-Arch-OS/ty]
Loading

Reviews (5): Last reviewed commit: "chore: release 2026.3.13" | Re-trigger Greptile

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 updates the version to 2026.3.13 across various files for the new release. The changes are mostly straightforward version bumps.

My review includes suggestions to improve the shell completion scripts. Currently, they hardcode the version number, which requires them to be updated with every release. I've proposed changes to make them dynamically determine the version from the mise binary itself, which would make them more robust and reduce future maintenance.

Comment thread completions/_mise
fi

local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_3_12.spec"
local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_3_13.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.

medium

Hardcoding the version number in the spec file path makes the completion script brittle. If mise is updated, this script would need to be updated as well. To make it more robust, you can dynamically get the version from the mise binary. This avoids the need to update this file with every release.

  local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_$(mise --version 2>/dev/null | command tail -n 1 | command awk '{print $1}' | command tr '.' '_').spec"

Comment thread completions/mise.bash
local cur prev words cword was_split comp_args
_comp_initialize -n : -- "$@" || return
local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_3_12.spec"
local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_3_13.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.

medium

Hardcoding the version number in the spec file path makes the completion script brittle. If mise is updated, this script would need to be updated as well. To make it more robust, you can dynamically get the version from the mise binary. This avoids the need to update this file with every release.

    local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_$(mise --version 2>/dev/null | command tail -n 1 | command awk '{print $1}' | command tr '.' '_').spec"

Comment thread completions/mise.fish
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_12.spec"
set -l spec_file "$tmpdir/usage__usage_spec_mise_2026_3_13.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.

medium

Hardcoding the version number in the spec file path makes the completion script brittle. If mise is updated, this script would need to be updated as well. To make it more robust, you can dynamically get the version from the mise binary. This avoids the need to update this file with every release.

set -l spec_file "$tmpdir/usage__usage_spec_mise_"(mise --version 2>/dev/null | command tail -n 1 | command awk '{print $1}' | command tr '.' '_')".spec"

Comment thread completions/mise.ps1

$tmpDir = if ($env:TEMP) { $env:TEMP } else { [System.IO.Path]::GetTempPath() }
$specFile = Join-Path $tmpDir "usage__usage_spec_mise_2026_3_12.kdl"
$specFile = Join-Path $tmpDir "usage__usage_spec_mise_2026_3_13.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.

medium

Hardcoding the version number in the spec file path makes the completion script brittle. If mise is updated, this script would need to be updated as well. To make it more robust, you can dynamically get the version from the mise binary. This avoids the need to update this file with every release.

    $specFile = Join-Path $tmpDir "usage__usage_spec_mise_$((mise --version 2>$null | Select-Object -Last 1).Split(' ')[0].Replace('.', '_')).kdl"

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 23, 2026

Hyperfine Performance

mise x -- echo

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.3.12 x -- echo 24.8 ± 0.9 23.6 30.5 1.00
mise x -- echo 24.9 ± 0.9 23.8 31.1 1.00 ± 0.05

mise env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.3.12 env 24.2 ± 1.0 22.8 29.4 1.00
mise env 24.4 ± 0.8 23.2 27.3 1.01 ± 0.05

mise hook-env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.3.12 hook-env 24.9 ± 0.8 23.7 28.3 1.00
mise hook-env 25.3 ± 0.9 24.0 28.5 1.02 ± 0.05

mise ls

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.3.12 ls 24.2 ± 0.9 22.9 35.7 1.00
mise ls 24.5 ± 0.8 23.4 27.5 1.01 ± 0.05

xtasks/test/perf

Command mise-2026.3.12 mise Variance
install (cached) 155ms 161ms -3%
ls (cached) 85ms 86ms -1%
bin-paths (cached) 91ms 88ms +3%
task-ls (cached) 825ms 831ms +0%

@mise-en-dev mise-en-dev force-pushed the release branch 2 times, most recently from bf470ad to 9dd56ac Compare March 23, 2026 09:30
@mise-en-dev mise-en-dev enabled auto-merge (squash) March 23, 2026 10:28
@mise-en-dev mise-en-dev merged commit 503195f into main Mar 23, 2026
62 checks passed
@mise-en-dev mise-en-dev deleted the release branch March 23, 2026 13:42
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