Skip to content

chore: release 2026.4.28#9478

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

chore: release 2026.4.28#9478
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 29, 2026

🐛 Bug Fixes

  • (copr) remove stale pinned image digest and rebuild copr image on Dockerfile changes by @bestagi in #9451
  • (task) avoid gix panic when cloning a remote task by commit SHA by @jdx in #9473

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 29, 2026

Greptile Summary

Routine automated release bump from v2026.4.27 to v2026.4.28, updating version strings consistently across all packaging and distribution artifacts (Cargo.toml, Cargo.lock, default.nix, snapcraft.yaml, packaging/rpm/mise.spec, all shell completion scripts, and README.md). The changelog entry documents two bug fixes: removal of a stale pinned image digest in the copr pipeline and a fix for a gix panic when cloning a remote task by commit SHA.

Confidence Score: 5/5

Safe to merge — purely mechanical version bump with no logic changes.

All changes are version string substitutions applied uniformly across every packaging file and completion script. No logic, configuration, or dependency graph is altered beyond the version identifier itself.

No files require special attention.

Important Files Changed

Filename Overview
CHANGELOG.md New changelog entry added for v2026.4.28 with two bug fix references
Cargo.toml Version bumped from 2026.4.27 to 2026.4.28
Cargo.lock Lock file updated to reflect the new mise version 2026.4.28
README.md Version string in the ASCII-art output example updated to 2026.4.28
completions/_mise Temp spec-file name updated to include new version (2026_4_28)
completions/mise.bash Temp spec-file name updated to include new version (2026_4_28)
completions/mise.fish Temp spec-file name updated to include new version (2026_4_28)
completions/mise.ps1 Temp KDL spec-file name updated to include new version (2026_4_28)
default.nix Nix package version bumped to 2026.4.28
packaging/rpm/mise.spec RPM spec version bumped to 2026.4.28
snapcraft.yaml Snap package version bumped to 2026.4.28

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Release trigger\n(mise-en-dev bot)"] --> B["Bump version\n2026.4.27 → 2026.4.28"]
    B --> C1["Cargo.toml / Cargo.lock"]
    B --> C2["default.nix"]
    B --> C3["snapcraft.yaml"]
    B --> C4["packaging/rpm/mise.spec"]
    B --> C5["completions\n(_mise, .bash, .fish, .ps1)"]
    B --> C6["README.md\n(version example)"]
    B --> C7["CHANGELOG.md\n(new entry)"]
Loading

Reviews (6): 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 project version to 2026.4.28 and includes a downgrade of the Node.js version to 24.14.0 in the lock file, along with several new platform-specific configurations. The reviewer highlighted concerns regarding the unexplained Node.js version downgrade and the introduction of redundant platform entries in the lock file. Additionally, the reviewer suggested refactoring the shell completion scripts to use a version-agnostic filename for the usage spec file to reduce maintenance overhead and improve robustness.

Comment thread mise.lock Outdated
Comment on lines +586 to +631
version = "24.14.0"
backend = "core:node"

[tools.node."platforms.linux-arm64"]
checksum = "sha256:f44740cd218de8127f1c44c41510a3a740fa5c9c8d1cdce1c3bedada79f3cde7"
url = "https://nodejs.org/dist/v24.14.0/node-v24.14.0-linux-arm64.tar.gz"

[tools.node."platforms.linux-arm64-musl"]
checksum = "sha256:8f81d47b7f443455709d44eae8669591de2e58b37d3c2cb0aec667b6e6f826c1"
url = "https://unofficial-builds.nodejs.org/download/release/v24.14.0/node-v24.14.0-linux-arm64-musl.tar.gz"

[tools.node."platforms.linux-x64"]
checksum = "sha256:134e55b2408448a219760fe04dc44d6851f9de8a79549021ffd870e9082d9e7b"
url = "https://nodejs.org/dist/v25.9.0/node-v25.9.0-linux-x64.tar.gz"
checksum = "sha256:dbf5b8665dec15e59e6359a517fefb47b23fdb9152d8def975b9bca3dfc6d355"
url = "https://nodejs.org/dist/v24.14.0/node-v24.14.0-linux-x64.tar.gz"

[tools.node."platforms.linux-x64-baseline"]
checksum = "sha256:dbf5b8665dec15e59e6359a517fefb47b23fdb9152d8def975b9bca3dfc6d355"
url = "https://nodejs.org/dist/v24.14.0/node-v24.14.0-linux-x64.tar.gz"

[tools.node."platforms.linux-x64-musl"]
checksum = "sha256:bae0f2320448d5c744bcd4878081b483194d8b0f0eaab2b37d7f81df739c5a95"
url = "https://unofficial-builds.nodejs.org/download/release/v24.14.0/node-v24.14.0-linux-x64-musl.tar.gz"

[tools.node."platforms.linux-x64-musl-baseline"]
checksum = "sha256:bae0f2320448d5c744bcd4878081b483194d8b0f0eaab2b37d7f81df739c5a95"
url = "https://unofficial-builds.nodejs.org/download/release/v24.14.0/node-v24.14.0-linux-x64-musl.tar.gz"

[tools.node."platforms.macos-arm64"]
checksum = "sha256:a1a54f46a750d2523d628d924aab61758a51c9dad3e0238beb14141be9615dd3"
url = "https://nodejs.org/dist/v24.14.0/node-v24.14.0-darwin-arm64.tar.gz"

[tools.node."platforms.macos-x64"]
checksum = "sha256:f2879eb810e25993a0578e5d878930266fd2eafcffe9f2839b3d8db354d4879e"
url = "https://nodejs.org/dist/v24.14.0/node-v24.14.0-darwin-x64.tar.gz"

[tools.node."platforms.macos-x64-baseline"]
checksum = "sha256:f2879eb810e25993a0578e5d878930266fd2eafcffe9f2839b3d8db354d4879e"
url = "https://nodejs.org/dist/v24.14.0/node-v24.14.0-darwin-x64.tar.gz"

[tools.node."platforms.windows-x64"]
checksum = "sha256:313fa40c0d7b18575821de8cb17483031fe07d95de5994f6f435f3b345f85c66"
url = "https://nodejs.org/dist/v24.14.0/node-v24.14.0-win-x64.zip"

[tools.node."platforms.windows-x64-baseline"]
checksum = "sha256:313fa40c0d7b18575821de8cb17483031fe07d95de5994f6f435f3b345f85c66"
url = "https://nodejs.org/dist/v24.14.0/node-v24.14.0-win-x64.zip"
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.

high

This change downgrades the node version from 25.9.0 to 24.14.0 and adds many new platform-specific entries. This is a significant change that isn't mentioned in the pull request description.

Additionally, there appears to be duplicated configuration for several platforms. For example, linux-x64 and linux-x64-baseline are identical. This duplication is also present for:

  • linux-x64-musl and linux-x64-musl-baseline
  • macos-x64 and macos-x64-baseline
  • windows-x64 and windows-x64-baseline

Could you please clarify the reason for the node version downgrade? Also, please investigate the duplicated entries. If the duplication is intentional, it would be helpful to add a comment to the file explaining why.

Comment thread completions/_mise
fi

local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_4_27.spec"
local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise_2026_4_28.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 in the spec file path makes the release process more complex, as this version string needs to be updated in several completion scripts. This approach is fragile.

A more robust solution would be to use a version-agnostic filename and regenerate the spec file only when the mise binary itself is updated. You could achieve this by comparing file modification times. For example, in bash:

local spec_file="${TMPDIR:-/tmp}/usage__usage_spec_mise.spec"
if [[ ! -f "$spec_file" || "$(command -v mise)" -nt "$spec_file" ]]; then
  mise usage >| "$spec_file"
fi

Adopting this pattern across all completion scripts would simplify future releases.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 29, 2026

Hyperfine Performance

mise x -- echo

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.4.27 x -- echo 22.3 ± 0.9 21.4 35.2 1.00
mise x -- echo 22.3 ± 0.5 21.7 27.0 1.00 ± 0.05

mise env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.4.27 env 21.4 ± 0.6 20.5 26.0 1.00
mise env 21.9 ± 0.3 21.2 23.2 1.02 ± 0.03

mise hook-env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.4.27 hook-env 22.1 ± 0.4 21.3 26.9 1.00
mise hook-env 22.9 ± 0.7 21.8 32.0 1.03 ± 0.04

mise ls

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.4.27 ls 22.8 ± 0.5 22.0 27.7 1.00
mise ls 23.5 ± 0.4 22.5 25.5 1.03 ± 0.03

xtasks/test/perf

Command mise-2026.4.27 mise Variance
install (cached) 154ms 159ms -3%
ls (cached) 80ms 82ms -2%
bin-paths (cached) 81ms 84ms -3%
task-ls (cached) 803ms 811ms +0%

@mise-en-dev mise-en-dev merged commit 5478adb into main Apr 30, 2026
62 checks passed
@mise-en-dev mise-en-dev deleted the release branch April 30, 2026 10:40
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