Revert ruff checker version to force autoupdate from mintmaker

[joselsegura]

Description

Revert version back in order to check mintmaker execution

Type of change

• Configuration update

Testing steps

N/A

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Updated development tool configuration version.

Walkthrough

Updated the ruff pre-commit hook configuration by downgrading its revision from v0.15.7 to v0.15.6. Hook identifiers and their arguments remain unchanged.

Changes

Cohort / File(s)	Summary
Pre-commit Configuration .pre-commit-config.yaml	Downgraded the ruff-pre-commit hook repository revision from v0.15.7 to v0.15.6.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: reverting the ruff checker version from v0.15.7 to v0.15.6 in the pre-commit configuration.
Description check	✅ Passed	The description is related to the changeset, explaining the rationale for reverting the version and noting it as a configuration update.
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

---

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

[coderabbitai]

🧹 Nitpick comments (1)

.pre-commit-config.yaml (1)

42-42: Consider updating to the latest version directly instead of reverting.

Downgrading versions as a workaround to trigger auto-updates is indirect. While v0.15.6 is stable with no known issues, directly updating to v0.15.7 is cleaner and avoids unnecessary downgrade cycles. This approach also prevents the unlikely scenario where the auto-update mechanism fails or is delayed, leaving the codebase on an older version unnecessarily.

Better approaches:

• Update directly to the latest ruff version (v0.15.7)
• Configure mintmaker to recognize this dependency needs updating
• Investigate why mintmaker isn't picking up the update normally

🤖 Prompt for AI Agents

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

In @.pre-commit-config.yaml at line 42, Replace the downgraded ruff rev entry
(rev: v0.15.6) in .pre-commit-config.yaml with the current release (rev:
v0.15.7) instead of reverting; also update whatever mintmaker configuration or
dependency manifest that tracks pre-commit hooks so mintmaker will detect future
ruff updates (investigate mintmaker rules or dependency list that references the
ruff pre-commit hook and ensure it includes this dependency for auto-updates).

🤖 Prompt for all review comments with AI agents

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

Nitpick comments:
In @.pre-commit-config.yaml:
- Line 42: Replace the downgraded ruff rev entry (rev: v0.15.6) in
.pre-commit-config.yaml with the current release (rev: v0.15.7) instead of
reverting; also update whatever mintmaker configuration or dependency manifest
that tracks pre-commit hooks so mintmaker will detect future ruff updates
(investigate mintmaker rules or dependency list that references the ruff
pre-commit hook and ensure it includes this dependency for auto-updates).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b45726ba-b7fe-478a-b803-18cc6d44e123

📥 Commits

Reviewing files that changed from the base of the PR and between 9ac6e92 and 979952f.

📒 Files selected for processing (1)

• .pre-commit-config.yaml