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

[shunkakinoki]

This PR contains the following updates:

Package	Change	Age	Confidence
mistral-vibe	>=2.7.2 → >=2.7.3

---

Release Notes

mistralai/mistral-vibe (mistral-vibe)

v2.7.3

Compare Source

Added

• /data-retention slash command to view Mistral AI's data retention notice and privacy settings

---

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 Renovate Bot.

---

Summary by cubic

Update mistral-vibe to >=2.7.3 to pull in the latest patch release. This includes the new /data-retention slash command from upstream.

^{Written for commit 0a57406. Summary will update on new commits.}

[mesa-dot-dev]

You do not have enough credits to review this pull request. Please purchase more credits to continue.

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated build tooling dependency to a newer minimum version for improved stability and compatibility.

Walkthrough

Updated the minimum version constraint for the mistral-vibe dependency tool in pyproject.toml from >=2.7.2 to >=2.7.3. This is a routine dependency version bump with no structural or control flow changes.

Changes

Cohort / File(s)	Summary
Dependency Version Update pyproject.toml	Bumped mistral-vibe minimum version from >=2.7.2 to >=2.7.3 in the dependency-groups.tools configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(deps): update dependency mistral-vibe to >=2.7.1 #1406: Modifies the same mistral-vibe dependency entry in pyproject.toml to update its minimum version constraint.
• chore(deps): update dependency mistral-vibe to >=2.7.2 #1410: Updates the mistral-vibe minimum version constraint in the same pyproject.toml configuration section.
• fix(deps): update all non-major dependencies (patch) #787: Changes the version constraint for mistral-vibe in pyproject.toml dependency declarations.

Suggested labels

dependencies

Poem

🐰 A version hops by, so small yet fine,
From 2.7.2 to 2.7.3 it must align,
The bunny updates with gentle care,
Dependencies fresh in the springtime air! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: updating the mistral-vibe dependency to >=2.7.3 in pyproject.toml.
Description check	✅ Passed	The description is directly related to the changeset, providing release notes and context about the mistral-vibe update from >=2.7.2 to >=2.7.3.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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/patch-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.}

[mesa-dot-dev]

Mesa Description

TL;DR

Updates the mistral-vibe dependency to version >=2.7.3, which includes a new /data-retention slash command.

What changed?

Updated the mistral-vibe dependency from >=2.7.2 to >=2.7.3. This version introduces a /data-retention slash command.

^{Description generated by Mesa. Update settings}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pyproject.toml`:
- Line 13: The pyproject dependency entry for mistral-vibe is pointing at a
non-published release; update the constraint for the package name "mistral-vibe"
in pyproject.toml from ">=2.7.3" to a published version (for example ">=2.7.2"
or a specific released pin like "==2.7.2") so installs use a PyPI-published
release and avoid referencing the GitHub-only tag.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b224f8a2-283e-47a4-aa42-d414f66bf0c4

📥 Commits

Reviewing files that changed from the base of the PR and between a2c254b and 0a57406.

📒 Files selected for processing (1)

• pyproject.toml

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Confirm from official package sources/release notes that mistral-vibe 2.7.3 is published and compatible with Python >=3.13.

💡 Result:

No, mistral-vibe 2.7.3 is not confirmed as published on official package sources like PyPI, and there is no evidence from release notes or official docs that it is compatible with Python >=3.13. The latest referenced PyPI versions are up to v2.7.0 or v2.7.2, all requiring Python >=3.12. A GitHub tag v2.7.3 exists, but no PyPI publication or Python version update to >=3.13 is documented in CHANGELOG.md, pyproject.toml samples, or docs.mistral.ai. Official install docs specify Python 3.12+.

Citations:

• 1: https://github.com/mistralai/mistral-vibe/blob/main/CHANGELOG.md
• 2: https://github.com/mistralai/mistral-vibe/tags
• 3: https://pypi.org/project/mistral-vibe/
• 4: https://docs.mistral.ai/mistral-vibe/introduction/install
• 5: https://github.com/mistralai/mistral-vibe/releases
• 6: https://github.com/mistralai/mistral-vibe
• 7: https://github.com/mistralai/mistral-vibe/releases/tag/v2.7.2
• 8: https://github.com/mistralai/mistral-vibe/blob/4d449be2/pyproject.toml

---

Do not merge: mistral-vibe 2.7.3 is not published on PyPI.

The version bump specifies mistral-vibe>=2.7.3, but v2.7.3 does not exist on PyPI. The latest published versions are v2.7.0 and v2.7.2, which both require Python >=3.12. A GitHub tag v2.7.3 exists but has not been released to PyPI. Installing this dependency as specified will fail or silently resolve to an older version.

Correct the version constraint to an actually published release (e.g., >=2.7.2) or wait for the official PyPI release of v2.7.3 with release notes confirming the version and Python compatibility.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@pyproject.toml` at line 13, The pyproject dependency entry for mistral-vibe
is pointing at a non-published release; update the constraint for the package
name "mistral-vibe" in pyproject.toml from ">=2.7.3" to a published version (for
example ">=2.7.2" or a specific released pin like "==2.7.2") so installs use a
PyPI-published release and avoid referencing the GitHub-only tag.

[Copilot]

Pull request overview

Updates the Renovate-tracked UV global tool dependency constraint for mistral-vibe in pyproject.toml, keeping the toolchain aligned with the latest patch release.

Changes:

• Bump mistral-vibe from >=2.7.2 to >=2.7.3 in the [dependency-groups].tools list.

---

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

[gemini-code-assist]

Code Review

This pull request updates the version of the mistral-vibe tool in pyproject.toml from 2.7.2 to 2.7.3. I have no feedback to provide.

[cubic-dev-ai]

No issues found across 1 file