chore(deps): update dependency mistral-vibe to >=2.11.0

[shunkakinoki]

This PR contains the following updates:

Package	Change	Age	Confidence
mistral-vibe	>=2.10.1 → >=2.11.0

---

Release Notes

mistralai/mistral-vibe (mistral-vibe)

v2.11.0

Compare Source

Added

• Load skills from ~/.agents/skills so they can be shared across agents
• Restore the textual theme selection system with an onboarding theme picker
• Surface unauthenticated connectors in /mcp with needs auth / needs setup labels and start the OAuth flow from inside the CLI
• Current date injected into the system prompt
• minimal system prompt variant for eval and training

Changed

• Refreshed manual API key onboarding screen to match the new onboarding panel layout
• Newly discovered connectors are now disabled by default; existing user choices are preserved

Fixed

• Preserve original line endings in ACP search_replace
• Show MCP/connectors count as enabled/total in the banner
• ACP grep tool displays the search path as a chip and no longer drops the filename

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

---

Summary by cubic

Upgrade mistral-vibe to >=2.11.0 to enable shared skills loading and smoother connector onboarding, plus recent fixes. Dependency-only change.

• Dependencies
  • Update pyproject.toml: mistral-vibe >=2.11.0 (was >=2.10.1).
  • Upstream highlights: loads skills from ~/.agents/skills, supports OAuth-driven connector setup, adds a minimal system prompt and current-date injection, and includes MCP/ACP bug fixes.

^{Written for commit 6b91b84. Summary will update on new commits.}

[indent-zero]

PR Summary

Renovate-driven minor version bump that keeps the tracked mistral-vibe UV global tool current. No functional or runtime impact — the tools dependency group is a Renovate-only tracking list; tools are installed in isolation via uv tool install.

• Bumps mistral-vibe lower bound from >=2.10.1 to >=2.11.0 in pyproject.toml's [dependency-groups].tools.

Issues

No issues found.

CI Checks

All three failures are infrastructure issues unrelated to the mistral-vibe lower-bound bump in pyproject.toml:

• docker-check (linux/arm64) ran out of disk space while copying CUDA libraries (libcublas-12.9.1.4) during the nix build inside the container — No space left on device.
• nix-darwin aborted building llama-cpp-9309 with a libuv kqueue assertion (errno == EINTR, kqueue.c:279), exit 134 — a known macOS runtime flake in the llama-cpp build.
• nix-check is the required-status aggregator and only failed because nix-darwin did.

Re-running these jobs is the right next step; no code change is warranted.

docker-check

• The arm64 docker-build-push job exhausted runner disk space while the in-container nix build copied CUDA artifacts: cp: error copying './lib/libcublasLt.so.12.9.1.4' ... No space left on device (note: 'build failure may have been caused by lack of free disk space'). This cascaded into failures for cuda12.9-libcublas, cuda-merged-12.9, nvtop, and the rest of the home-manager build. Unrelated to the mistral-vibe version bump; re-run after the runner has more free space.

nix-darwin

• Build of llama-cpp-9309 aborted with a libuv kqueue assertion (errno == EINTR, kqueue.c:279), exit 134 — a runtime flake in the llama-cpp build under nix-darwin, unrelated to this PR. Re-running should resolve it.

nix-check

• The Alls Green aggregator failed solely because the required nix-darwin job failed. Will pass once nix-darwin is re-run successfully.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 69cd13b6-32b8-4fd0-9988-90d4a7a6cab5

📥 Commits

Reviewing files that changed from the base of the PR and between 467197d and 6b91b84.

📒 Files selected for processing (1)

• pyproject.toml

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated internal dependency to latest compatible version.

Walkthrough

This PR updates the mistral-vibe tool dependency in pyproject.toml from version >=2.10.1 to >=2.11.0, requiring a newer minimum version for the tools dependency group.

Changes

Dependency Version Update

Layer / File(s)	Summary
Mistral Vibe Version Constraint pyproject.toml	The mistral-vibe version constraint in the tools dependency group is bumped from >=2.10.1 to >=2.11.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• shunkakinoki/dotfiles#1859: Both PRs modify the mistral-vibe dependency version constraint in pyproject.toml's dependency-groups.tools entry.
• shunkakinoki/dotfiles#1861: Both PRs bump the mistral-vibe minimum version requirement in the same [dependency-groups].tools section.
• shunkakinoki/dotfiles#1410: Both PRs update the mistral-vibe minimum version constraint in pyproject.toml's tools dependency group.

Poem

🐰 A tiny hop through pyproject.toml,
Where mistral-vibe now stands up tall,
From 2.10.1 to 2.11.0 it springs,
Each version bump a rabbit's delight brings! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the mistral-vibe dependency from >=2.10.1 to >=2.11.0.
Description check	✅ Passed	The description is directly related to the changeset, providing detailed release notes and configuration information for the mistral-vibe dependency update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/all-minor-patch

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Code Review

This pull request updates the dependency version of "mistral-vibe" from ">=2.10.1" to ">=2.11.0" in "pyproject.toml". There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[mesa-dot-dev]

Mesa Description

TL;DR

Updates the mistral-vibe dependency to version >=2.11.0 to bring in new agent skill sharing, CLI onboarding improvements, and ACP/MCP fixes.

What changed?

• Dependency configuration: Updated mistral-vibe dependency constraint from >=2.10.1 to >=2.11.0.
• Inherited updates from mistral-vibe v2.11.0:
  • Added skill sharing across agents from ~/.agents/skills.
  • Restored textual theme selection with an onboarding theme picker.
  • Enabled OAuth flow starting inside CLI for unauthenticated MCP connectors.
  • Added current date injection and a minimal system prompt variant.
  • Fixed ACP search_replace line endings and improved grep tool path/file output.

^{Description generated by Mesa. Update settings}

[Copilot]

Pull request overview

Updates the tracked version constraint for the mistral-vibe UV global tool in pyproject.toml, keeping Renovate-managed tool versions current.

Changes:

• Bump mistral-vibe version requirement from >=2.10.1 to >=2.11.0 in the dependency-groups.tools list.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mesa-dot-dev]

Performed full review of 467197d...6b91b84

Analysis

• Unbounded version constraint (>=2.11.0) allows uncontrolled major version upgrades without review; implement upper bounds (e.g., <3.0.0) to ensure deliberate, tested upgrades.

• Date injection into system prompts breaks test determinism and snapshot reliability; validate existing test suites don't fail due to time-dependent output variations.

• Auto-loading skills from ~/.agents/skills introduces environment-dependent behavior and potential conflicts with repo-local skills, compromising reproducibility across dev/CI/prod; verify skill precedence and test with/without user directory present.

• Connector discovery now disables by default instead of enabling; confirm this doesn't break existing workflows that assume discovery enables functionality, particularly in non-interactive/CI contexts.

Tip

Help

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{0 files reviewed | 1 comments | Edit Agent Settings • Read Docs}

[mesa-dot-dev]

The unbounded version constraint >=2.11.0 allows any future version to be installed, including potentially breaking major releases (3.x, 4.x, etc.). This bypasses your review process and can introduce untested behavioral changes on fresh installs or when dependency locks are regenerated.

Consider using a bounded range instead:

• >=2.11.0,<3.0.0 (allows patch and minor updates within v2)
• >=2.11.0,<2.12.0 (stricter, only allows patch updates)

This ensures version upgrades remain deliberate and properly validated through your testing pipeline.

 • 

Prompt for Agent

Task: Address review feedback left on GitHub.
Repository: shunkakinoki/dotfiles#1879
File: pyproject.toml#L16
Action: Open this file location in your editor, inspect the highlighted code, and resolve the issue described below.

Feedback:
The unbounded version constraint `>=2.11.0` allows any future version to be installed, including potentially breaking major releases (3.x, 4.x, etc.). This bypasses your review process and can introduce untested behavioral changes on fresh installs or when dependency locks are regenerated.

Consider using a bounded range instead:
- `>=2.11.0,<3.0.0` (allows patch and minor updates within v2)
- `>=2.11.0,<2.12.0` (stricter, only allows patch updates)

This ensures version upgrades remain deliberate and properly validated through your testing pipeline.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}