chore: update pre-commit hook versions

[gamaware]

Automated update of pre-commit hook versions.

Review the changes to .pre-commit-config.yaml and merge if CI passes.

Summary by CodeRabbit

• Chores
  • Updated the Markdown linting tool used during code quality checks to a newer version.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

The markdownlint-cli pre-commit hook revision is updated from v0.48.0 to v0.49.1 in .pre-commit-config.yaml.

Changes

markdownlint-cli Pre-commit Hook Version Bump

Layer / File(s)	Summary
markdownlint-cli rev bump .pre-commit-config.yaml	The hook revision changes from v0.48.0 to v0.49.1.

Estimated code review effort: 1 (Trivial) | ~1 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: updating pre-commit hook versions.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/update-pre-commit-hooks

---

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.}

[Copilot]

Pull request overview

This PR updates the markdownlint-cli pre-commit hook version to keep local Markdown linting aligned with the latest upstream release.

Changes:

• Bump igorshubovych/markdownlint-cli hook from v0.48.0 to v0.49.0.

[coderabbitai]

🧹 Nitpick comments (1)

.pre-commit-config.yaml (1)

54-58: ⚖️ Poor tradeoff

Consider tooling consistency between pre-commit and CI.

The pre-commit hook uses markdownlint-cli while the CI workflow (from context snippet 2) uses markdownlint-cli2-action. These are different tools with potentially different rule sets and behaviors, which could lead to inconsistent linting results between local development and CI.

Consider standardizing on one tool (markdownlint-cli2 is generally faster and more configurable) or ensuring both are configured with identical rules to prevent discrepancies.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.pre-commit-config.yaml around lines 54 - 58, Update the markdownlint
pre-commit hook in the .pre-commit-config.yaml file to use the same tool as your
CI workflow. The markdownlint hook entry that uses the
igorshubovych/markdownlint-cli repository should be replaced with
markdownlint-cli2 configuration (or alternatively, ensure both the pre-commit
hook and your CI workflow use identical versions and configurations of
markdownlint-cli to prevent discrepancies). Verify that the args and all linting
rules are consistent between your local pre-commit setup and your CI pipeline to
ensure uniform linting behavior.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.pre-commit-config.yaml:
- Around line 54-58: Update the markdownlint pre-commit hook in the
.pre-commit-config.yaml file to use the same tool as your CI workflow. The
markdownlint hook entry that uses the igorshubovych/markdownlint-cli repository
should be replaced with markdownlint-cli2 configuration (or alternatively,
ensure both the pre-commit hook and your CI workflow use identical versions and
configurations of markdownlint-cli to prevent discrepancies). Verify that the
args and all linting rules are consistent between your local pre-commit setup
and your CI pipeline to ensure uniform linting behavior.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3ee2f5ef-770e-4aa3-919d-3829244dd958

📥 Commits

Reviewing files that changed from the base of the PR and between e8fe3d4 and 78641cf.

📒 Files selected for processing (1)

• .pre-commit-config.yaml