Skip to content

chore: release 2026.4.25#9422

Merged
mise-en-dev merged 2 commits intomainfrom
release
Apr 28, 2026
Merged

chore: release 2026.4.25#9422
mise-en-dev merged 2 commits intomainfrom
release

Conversation

@mise-en-dev
Copy link
Copy Markdown
Collaborator

@mise-en-dev mise-en-dev commented Apr 27, 2026

🚀 Features

  • (task) add --name-only flag to mise tasks ls by @jdx in #9435

🐛 Bug Fixes

  • (Dockerfile) install copr-cli via dnf for better dependency management by @bestagi in #9421
  • (aqua) drop empty-releases fallback to tags by @jdx in #9443
  • (docs) fix theme flicker on docs by @vhespanha in #9427
  • (lockfile) update global lockfile on upgrade by @jdx in #9442
  • (ls-remote) omit rolling/prerelease from JSON when false by @jdx in #9439
  • (task) support usage refs in dependency template tags by @jdx in #9424
  • (task) populate usage.cmd for subcommand-only tasks; share make_usage_ctx by @jdx in #9431
  • (task) resolve sandbox allow_read/allow_write against task dir by @jdx in #9428

📚 Documentation

  • (site) add self-hosted page tracker via Cloudflare Worker, drop GoatCounter by @jdx in #9430

New Contributors

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 27, 2026

Greptile Summary

This is a routine automated release PR bumping mise from 2026.4.24 to 2026.4.25. All version references are consistently updated across Cargo.toml, Cargo.lock, default.nix, snapcraft.yaml, packaging/rpm/mise.spec, all four completion scripts, and README.md, with a matching changelog entry and updated star count.

Confidence Score: 5/5

This PR is safe to merge — it is a mechanical version bump with no logic changes.

All changes are version string updates and a changelog entry. Every packaging file, completion script, and the lock file are consistently updated to 2026.4.25. No logic, security, or correctness issues exist.

No files require special attention.

Important Files Changed

Filename Overview
CHANGELOG.md New changelog section for v2026.4.25 with features, bug fixes, and new contributors accurately listed.
Cargo.toml Version bumped from 2026.4.24 to 2026.4.25.
Cargo.lock Lock file updated to reflect new mise version 2026.4.25.
completions/_mise Spec file cache path updated to use new version string 2026_4_25.
completions/mise.bash Spec file cache path updated to use new version string 2026_4_25.
completions/mise.fish Spec file cache path updated to use new version string 2026_4_25.
completions/mise.ps1 Spec file cache path updated to use new version string 2026_4_25.
default.nix Nix package version bumped to 2026.4.25.
docs/.vitepress/stars.data.ts Star count updated from 27.2k to 27.3k.
packaging/rpm/mise.spec RPM spec version bumped to 2026.4.25.
snapcraft.yaml Snap package version bumped to 2026.4.25.
README.md Example version output in README updated to 2026.4.25 with the correct release date.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release PR: v2026.4.25] --> B[Version Bump Files]
    B --> B1[Cargo.toml / Cargo.lock]
    B --> B2[default.nix]
    B --> B3[snapcraft.yaml]
    B --> B4[packaging/rpm/mise.spec]
    A --> C[Completion Scripts]
    C --> C1[completions/_mise]
    C --> C2[completions/mise.bash]
    C --> C3[completions/mise.fish]
    C --> C4[completions/mise.ps1]
    A --> D[Docs & Metadata]
    D --> D1[CHANGELOG.md]
    D --> D2[README.md]
    D --> D3[docs/.vitepress/stars.data.ts]
Loading

Reviews (15): Last reviewed commit: "[autofix.ci] apply automated fixes" | 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 of mise to 2026.4.25 across the project, including Cargo manifests, changelogs, documentation, and shell completion scripts. Feedback was provided to improve the security and reliability of the completion scripts by including user-specific identifiers in temporary file paths to prevent permission conflicts in multi-user environments.

Comment thread completions/_mise
fi

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

Using a fixed filename in a shared temporary directory like /tmp can lead to permission conflicts or security risks in multi-user environments. If one user creates the file, others may encounter "permission denied" errors. Including the effective user ID ($EUID) in the filename ensures that each user has their own spec file.

  local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_${EUID}_2026_4_25.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_4_24.spec"
local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_4_25.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

Using a fixed filename in a shared temporary directory like /tmp can lead to permission conflicts or security risks in multi-user environments. Including the effective user ID ($EUID) in the filename ensures that each user has their own spec file and prevents potential access issues.

    local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_${EUID}_2026_4_25.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_4_24.spec"
set -l spec_file "$tmpdir/usage__usage_spec_mise_2026_4_25.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

Using a fixed filename in a shared temporary directory like /tmp can lead to permission conflicts or security risks in multi-user environments. Including the user ID (via id -u) in the filename ensures that each user has their own spec file.

set -l spec_file "$tmpdir/usage__usage_spec_mise_"(id -u)"_2026_4_25.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_4_24.kdl"
$specFile = Join-Path $tmpDir "usage__usage_spec_mise_2026_4_25.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

Using a fixed filename in a shared temporary directory can lead to permission conflicts in multi-user environments. Additionally, the .kdl extension is inconsistent with the .spec extension used in the Bash, Zsh, and Fish completion scripts. Consider including the username in the filename and using the .spec extension for consistency.

    $specFile = Join-Path $tmpDir "usage__usage_spec_mise_$($env:USERNAME)_2026_4_25.spec"

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 27, 2026

Hyperfine Performance

mise x -- echo

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.4.24 x -- echo 22.2 ± 0.5 21.4 26.4 1.00
mise x -- echo 22.8 ± 1.8 21.7 61.2 1.03 ± 0.09

mise env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.4.24 env 21.7 ± 0.5 20.8 26.2 1.00
mise env 22.2 ± 0.4 21.2 24.2 1.03 ± 0.03

mise hook-env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.4.24 hook-env 22.3 ± 0.4 21.4 24.1 1.00
mise hook-env 22.8 ± 0.5 21.8 25.8 1.02 ± 0.03

mise ls

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.4.24 ls 22.6 ± 0.6 21.7 30.7 1.00
mise ls 23.3 ± 0.8 22.5 32.0 1.03 ± 0.05

xtasks/test/perf

Command mise-2026.4.24 mise Variance
install (cached) 154ms 159ms -3%
ls (cached) 80ms 83ms -3%
bin-paths (cached) 82ms 83ms -1%
task-ls (cached) 804ms 808ms +0%

@mise-en-dev mise-en-dev force-pushed the release branch 10 times, most recently from 282c124 to 6862df2 Compare April 28, 2026 00:29
@mise-en-dev mise-en-dev merged commit edbe1ca into main Apr 28, 2026
63 checks passed
@mise-en-dev mise-en-dev deleted the release branch April 28, 2026 10:45
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