chore: update dev tool versions from PyPI

[github-actions]

Summary

This PR updates the pinned dev tool versions in autofix-versions.env.
It matches the latest releases on PyPI.

Changes

Checking versions in .github/workflows/autofix-versions.env...
  Checking black... 26.5.1 -> 26.5.1 [OK]
  Checking ruff... 0.15.18 -> 0.15.19 [OUTDATED]
  Checking isort... 8.0.1 -> 8.0.1 [OK]
  Checking docformatter... 1.7.8 -> 1.7.8 [OK]
  Checking mypy... 2.1.0 -> 2.1.0 [OK]
  Checking pytest... 9.1.1 -> 9.1.1 [OK]
  Checking pytest-cov... 7.1.0 -> 7.1.0 [OK]
  Checking pytest-xdist... 3.8.0 -> 3.8.0 [OK]
  Checking coverage... 7.14.3 -> 7.14.3 [OK]

⚠️  Found 1 outdated version(s):
  ruff: 0.15.18 -> 0.15.19

✅ Updated 1 version(s) in .github/workflows/autofix-versions.env

Why this matters

Keeping dev tool versions current ensures:

• Consumer repos receive the latest bug fixes and features
• We don't ship known-vulnerable or outdated tooling
• Version drift between repos is minimized

---

Auto-generated by the maint-auto-update-pypi-versions workflow

Summary by CodeRabbit

• Chores
  • Updated development tool dependency versions across project configurations and templates to the latest compatible release, ensuring consistency and access to current tooling improvements.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a2267811-45c7-4633-a0a5-1478b13cb94f

📥 Commits

Reviewing files that changed from the base of the PR and between f329dbd and 9fc9ad0.

⛔ Files ignored due to path filters (1)

• requirements.lock is excluded by !**/*.lock, !**/*.lock

📒 Files selected for processing (4)

• .github/workflows/autofix-versions.env
• pyproject.toml
• templates/consumer-repo/.github/workflows/autofix-versions.env
• templates/integration-repo/.github/workflows/autofix-versions.env

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• stranske/Template (auto-detected)
• stranske/Fine-Art-Archive (auto-detected)
• stranske/Ready (auto-detected)
• stranske/Workflows-Integration-Tests (auto-detected)

---

📝 Walkthrough

Walkthrough

Bumps the ruff version pin from 0.15.18 to 0.15.19 in four places: the root CI autofix env file, both template repo autofix env files (consumer and integration), and the dev optional dependency in pyproject.toml.

Changes

Ruff 0.15.19 version bump

Layer / File(s)	Summary
Ruff 0.15.19 pin across all config files .github/workflows/autofix-versions.env, pyproject.toml, templates/consumer-repo/.github/workflows/autofix-versions.env, templates/integration-repo/.github/workflows/autofix-versions.env	RUFF_VERSION and the ruff dev dependency are each updated from 0.15.18 to 0.15.19.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

maintenance, github:actions, sync

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: update dev tool versions from PyPI' accurately describes the main change: bumping ruff and other dev tool versions to match PyPI releases.
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 docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch auto/update-pypi-versions-20260624

---

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

[stranske-keepalive]

Workflow source needed

PR #2526 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely.

Please do one of:

• Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
• Check one Workflow Source option in the PR body.
• Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
• Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.

[stranske]

Closing as superseded by #2524, which carries the same ruff pin update plus the validated source/template/lock alignment and review follow-up.