Bump whitaker-installer to 0.2.6

[leynos]

This bumps the pinned whitaker-installer version from 0.2.5 to 0.2.6, because the Whitaker Dylint suite's rolling release now pins toolchain nightly-2026-05-28, which requires cargo-dylint 6.0.1. Installer 0.2.5 provisions cargo-dylint 4.1.0, whose dylint driver cannot compile on that nightly, so generated projects would fail to lint. Installer 0.2.6 provisions cargo-dylint 6.0.1 and its prebuilt dependency binaries are now published, resolving the incompatibility.

As this is a copier/Jinja template repository, the pin was updated in both places it is set: the generated CI workflow and the generated Makefile. No other occurrences of the version string, and no snapshot fixtures, reference whitaker-installer 0.2.5.

Changed files

• template/.github/workflows/ci.yml.jinja
• template/Makefile.jinja

Testing

make test was run locally (uv/pytest). All Whitaker-relevant suites pass, including tests/test_template.py, tests/test_helpers.py, and tests/test_github_actions_integration.py. One unrelated pre-existing failure was observed in tests/test_typos_rollout.py::test_committed_config_matches_current_shared_dictionary, caused by drift in the upstream shared typos dictionary; this failure reproduces identically on unmodified main and is unrelated to this change.

[sourcery-ai]

Sorry @leynos, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 12 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 68caedab-894c-49dd-9867-25f0cb51adcc

📥 Commits

Reviewing files that changed from the base of the PR and between 2bcb36d and 3882e2d.

📒 Files selected for processing (3)

• template/.github/workflows/ci.yml.jinja
• template/Makefile.jinja
• typos.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-whitaker-installer-0.2.6

---

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