ci: Regenerate mise.lock so rust@latest resolves under --locked

[unclesp1d3r]

Summary

Regenerates mise.lock with the current mise CLI so mise install --locked succeeds. This unblocks PR #315 (jdx/mise-action 4.0.1 -> 4.1.0).

Why

mise-action v4.1.0 runs mise install --locked with the newer mise CLI (2026.6.13, released 2026-06-23). The committed lockfile only pinned the previously-resolved rust@1.95.0 and had no entry keyed to the latest/stable channels that mise.toml (rust = "latest") and rust-toolchain.toml (channel = "stable") declare. Result on #315:

core:rust@latest: rust@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise ERROR Version: 2026.6.13

v4.0.1 did not enforce --locked, so main and other open PRs are unaffected today.

What

• Ran mise lock with mise 2026.6.13 (matching CI)
• rust latest now resolves to 1.96.0; a stable entry is derived from the committed rust-toolchain.toml
• Platform entries refreshed for all locked tools (python -> 3.14.4, bun backend, etc.)

Verification

• mise install --locked -> exit 0 locally (the exact command failing on chore(deps): Bump jdx/mise-action from 4.0.1 to 4.1.0 #315)
• Lockfile is reproducible from committed config only (no mise.local.toml present)

Merge order

Merge this first, then PR #315 will rebase onto it and pass.

Test plan

• mise install --locked exits 0 locally
• CI green on this PR (v4.0.1, unaffected)
• After merge: chore(deps): Bump jdx/mise-action from 4.0.1 to 4.1.0 #315 CI green

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• mise.lock is excluded by !**/*.lock and included by none

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 108dd1e2-e8a9-4938-8d6f-ce2861f3c5da

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[mergify]

Merge Protections

🔴 1 of 4 protections blocking

	Protection	Waiting on
🔴	🚦 Auto-queue	—
🟢	Enforce conventional commit	—
🟢	Full CI must pass	—
🟢	Do not merge outdated PRs	—

🔴 🚦 Auto-queue

This rule is failing.

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

• any of:
  • all of:
    • author = dosubot[bot]
    • base = main
    • label != do-not-merge
  • all of:
    • author = dependabot[bot]
    • base = main
    • label != do-not-merge
  • all of:
    • author = release-plz[bot]
    • head ~= ^release-plz-
    • base = main
    • label != do-not-merge

---

Show 3 satisfied protections

🟢 Enforce conventional commit

Require conventional commit format per https://www.conventionalcommits.org/en/v1.0.0/. Skipped for bots.

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?!?:

🟢 Full CI must pass

All CI checks must pass. Release-plz PRs are exempt because they only bump versions and changelogs (code was already tested on main), and GITHUB_TOKEN-triggered force-pushes suppress CI.

• check-success = coverage
• check-success = quality
• check-success = test
• check-success = test-cross-platform (macos-latest, macOS)
• check-success = test-cross-platform (ubuntu-22.04, Linux)
• check-success = test-cross-platform (ubuntu-latest, Linux)
• check-success = test-cross-platform (windows-latest, Windows)

🟢 Do not merge outdated PRs

Make sure PRs are within 10 commits of the base branch before merging

• #commits-behind <= 10

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request