Skip to content

Bump whitaker-installer to 0.2.6 - #17

Merged
leynos merged 2 commits into
mainfrom
bump-whitaker-installer-0.2.6
Jul 17, 2026
Merged

Bump whitaker-installer to 0.2.6#17
leynos merged 2 commits into
mainfrom
bump-whitaker-installer-0.2.6

Conversation

@leynos

@leynos leynos commented Jul 17, 2026

Copy link
Copy Markdown
Owner

This pull request 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 driver cannot be compiled on that nightly, so the repository's CI lint step has been red until this bump lands. whitaker-installer 0.2.6 fixes this, and its prebuilt dependency binaries are now published.

Changed files

Installer 0.2.5 provisions cargo-dylint 4.1.0, whose dylint driver
cannot build on the suite's new nightly-2026-05-28 pin; 0.2.6
provisions cargo-dylint 6.0.1.
@leynos
leynos enabled auto-merge (squash) July 17, 2026 20:07

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Please try again later or upgrade to continue using Sourcery

@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown

Review Change Stack

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

Summary

  • Updated the pinned whitaker-installer from 0.2.5 to 0.2.6, provisioning cargo-dylint 6.0.1 for the nightly-2026-05-28 toolchain.
  • Standardised documentation spelling from “artifacts” to “artefacts” in the Limela pipeline design.
  • Regenerated typos.toml to satisfy the en-GB-oxendict spelling gate and cover additional spelling exceptions.

Walkthrough

The PR updates the Whitaker installer used by CI, standardises documentation to “artefacts”, and expands generated Typos ignore patterns and spelling mappings.

Changes

CI installer update

Layer / File(s) Summary
Update Whitaker installer version
.github/workflows/ci.yml
Set WHITAKER_INSTALLER_VERSION to 0.2.6, updating installation and cache selection.

Spelling policy updates

Layer / File(s) Summary
Expand Typos rules
typos.toml
Add ignore patterns and mappings for code tokens, abbreviations, and spelling variants; remove artifact mappings.
Standardise documentation spelling
docs/limela-pipeline-design.md
Replace four occurrences of “artifacts” with “artefacts”.

Possibly related PRs

Poem

Bump the installer, let builds take flight,
Tune spelling rules to mark words right.
Turn artefacts into the local tongue,
Let clean CI checks be brightly sung.
Keep every pipeline step precise.


Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

  • Ignore

❌ Failed checks (1 error, 1 warning)

Check name Status Explanation Resolution
Testing (Overall) ❌ Error No test guards the new typos policy: scripts/tests/test_typos_rollout.py only checks render/parse determinism, not the added ignore regexes or allow-listed words. Add a regression test that feeds a fixture with fenced code, inline code, rust-analyzer, and the new allow-listed spellings, then assert the spelling policy outcome.
Testing (Unit And Behavioural) ⚠️ Warning PR updates spelling config and Whitaker pin, but adds no behavioural test for the new typos rules; current tests only parse/render config. Add a regression test in scripts/tests/test_typos_rollout.py for fenced code, inline code, rust-analyzer and allow-listed terms; add a CI smoke check if feasible.
✅ Passed checks (18 passed)
Check name Status Explanation
Title check ✅ Passed Match the main installer bump from 0.2.5 to 0.2.6.
Description check ✅ Passed Describe the Whitaker installer bump and the CI fix rationale.
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.
User-Facing Documentation ✅ Passed Leave no users-guide update: the PR only changes CI, a design doc, and typo config, with no user-facing behaviour added.
Developer Documentation ✅ Passed PASS: only spelling and CI installer-pin changes landed; no new API or architecture change required a guide/ADR update, and the design doc stayed in sync.
Module-Level Documentation ✅ Passed No source modules were touched; the PR only changes docs and spelling config, so the module docstring rule is not applicable.
Testing (Property / Proof) ✅ Passed No new range-based invariant or proof obligation appears; the edit is declarative config/docs, not algorithmic logic.
Testing (Compile-Time / Ui) ✅ Passed Only docs, workflow, and generated TOML changed; no Rust/TS compile-time or UI surface changed, and existing rollout tests already validate deterministic TOML rendering.
Unit Architecture ✅ Passed Only CI, docs, and spelling-config files changed; no code paths or dependencies affecting query/command boundaries were touched.
Domain Architecture ✅ Passed Only workflow/docs/typos config changed; no domain, adapter, persistence, transport, or business-rule code was touched.
Observability ✅ Passed PASS: Limit the patch to CI/docs/typos; add no runtime code, logging, metrics, tracing, or alerts, so observability is not applicable.
Security And Privacy ✅ Passed Pass: retain read-only workflow permissions and spelling-only docs/typos changes; no new secrets, credentials, or sensitive-data exposure.
Performance And Resource Use ✅ Passed Only docs and typo-check config changed; no runtime code, loops, I/O, allocation, or background work were touched, and the new regexes are bounded.
Concurrency And State ✅ Passed Approve: the PR only bumps a workflow pin and updates spelling/docs; no shared mutable state, locking, async tasks, or ordering logic changed.
Architectural Complexity And Maintainability ✅ Passed PASS: Keep changes to a version bump, spelling fixes, and generated typo config; introduce no new abstractions, layers, or dependencies.
Rust Compiler Lint Integrity ✅ Passed PR only touches CI/docs/typos config; no Rust sources, lint suppressions, or clone changes were introduced.
✨ 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.

The shared en-GB-oxendict typos dictionary was recently updated,
dropping the "artifact"/"artifacts" allow-word entries and surfacing
four pre-existing spellings in docs/limela-pipeline-design.md that the
gate now flags. Corrected each occurrence to the Oxford spelling
"artefacts"; all four were genuine prose (email cleanup residue,
deployment artefacts, blob data artefacts, regex-removed noise), so
no typos.local.toml exception was needed. typos.toml is regenerated
by scripts/generate_typos_config.py from the refreshed shared
dictionary and is committed as produced.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

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

Inline comments:
In `@typos.toml`:
- Around line 34-39: Add a regression test in the test_typos_rollout.py test
suite that runs the typos checker against a fixture containing fenced code,
inline code, rust-analyzer, and the allow-listed terms from typos.toml. Assert
the expected checker behavior for each case, while preserving the existing
configuration parsing and rendering tests.
🪄 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: ASSERTIVE

Plan: Pro Plus

Run ID: cd3e2e59-7203-4c90-82df-2e6ca8d52d3f

📥 Commits

Reviewing files that changed from the base of the PR and between e1b4026 and 39068d9.

📒 Files selected for processing (3)
  • .github/workflows/ci.yml
  • docs/limela-pipeline-design.md
  • typos.toml
🔗 Linked repositories identified

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

  • leynos/whitaker (auto-detected)

Comment thread typos.toml
Comment on lines +34 to +39
"\\brust-analyzer\\b",
"`[^`\\n]+`",
]

[default.extend-words]
"ASO" = "ASO"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail
printf 'FILES:\n'
git ls-files | rg '(^|/)(typos\.toml|.*typos.*|.*spell.*|.*typo.*|Makefile|scripts/typos_rollout\.py|.*test.*|.*spec.*)$' || true
printf '\nTYPOS TOML:\n'
nl -ba typos.toml | sed -n '1,220p'
printf '\nSEARCH artifact/artifacts/ignore words:\n'
rg -n '"artifact|artifacts|rust-analyzer|ASO|ignore-regex|extend-words|typos' . || true

Repository: leynos/limela

Length of output: 504


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'TYPOS TOML:\n'
sed -n '1,220p' typos.toml

printf '\nLOCAL TYPOS TOML:\n'
sed -n '1,220p' typos.local.toml

printf '\nROLL OUT TESTS:\n'
sed -n '1,260p' scripts/tests/test_typos_rollout.py

printf '\nSEARCH RELEVANT REFERENCES:\n'
rg -n 'artifact|artifacts|rust-analyzer|ASO|extend-words|ignore-regex|typos' scripts tests .github . || true

Repository: leynos/limela

Length of output: 25385


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '--- typos.toml ---'
sed -n '1,220p' typos.toml

echo
echo '--- scripts/tests/test_typos_rollout.py ---'
sed -n '1,260p' scripts/tests/test_typos_rollout.py

echo
echo '--- grep relevant references ---'
rg -n 'artifact|artifacts|rust-analyzer|ASO|extend-words|ignore-regex|typos' typos.toml typos.local.toml scripts tests .github || true

Repository: leynos/limela

Length of output: 20461


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '--- Makefile relevant section ---'
sed -n '40,80p' Makefile

echo
echo '--- GitHub workflow references to typos/spellcheck ---'
rg -n 'typos|spellcheck|generate_typos_config|typos\.toml' .github Makefile scripts -g '!scripts/tests/test_typos_rollout.py'

echo
echo '--- generate_typos_config.py ---'
sed -n '1,220p' scripts/generate_typos_config.py

Repository: leynos/limela

Length of output: 7640


Add a regression test in scripts/tests/test_typos_rollout.py.
Exercise typos.toml with a fixture that hits fenced code, inline code, rust-analyzer, and the new allow-listed terms, so the checker behaviour stays covered. The current tests only parse and render the config.

🤖 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 `@typos.toml` around lines 34 - 39, Add a regression test in the
test_typos_rollout.py test suite that runs the typos checker against a fixture
containing fenced code, inline code, rust-analyzer, and the allow-listed terms
from typos.toml. Assert the expected checker behavior for each case, while
preserving the existing configuration parsing and rendering tests.

Source: Coding guidelines

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant