Skip to content

Repin install-whitaker to 5a99aed7 (whitaker-installer 0.2.11) - #670

Merged
leynos merged 2 commits into
mainfrom
repin-install-whitaker-0-2-11
Oct 30, 2026
Merged

leynos merged 2 commits into
mainfrom
repin-install-whitaker-0-2-11

Conversation

@leynos

@leynos leynos commented Oct 30, 2026 •

Copy link
Copy Markdown
Owner

Part of DF12-89

Repins leynos/shared-actions/.github/actions/install-whitaker to 5a99aed78ce68dcebd3052b75c31e6f173162b1e (shared-actions #651, approved as a root by concordat QG-002, leynos/concordat#331). The action then defaults to whitaker-installer 0.2.11, which builds the Dylint driver from a verified Clippy snapshot: upstream Dylint 6.0.1 clones Clippy's master, which no longer exists, so every cold Whitaker driver build fails.

Pin-only: the single uses: line(s) change; no other file.

Other Whitaker paths

No bare cargo dylint, cargo binstall whitaker or hand-rolled installer outside the action and the whitaker wrapper.

Notes

A cache-restored driver rebuilds once (about a minute); that is expected. Gate: CI green on the lint lane at the head, with the lint job's log read for Whitaker's diagnostics.

Summary by Sourcery

Restore reliable Whitaker lint setup by updating the CI installation action to the approved revision.

Bug Fixes:

  • Update the Whitaker installation action to a verified revision that uses whitaker-installer 0.2.11, restoring cold Dylint driver builds in CI.

CI:

  • Repin the CI Whitaker installation action to the approved shared-actions revision.

@sourcery-ai

sourcery-ai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The CI lint workflow now pins the Whitaker installer action to shared-actions commit 5a99aed7, avoiding cold driver-build failures caused by upstream Dylint cloning the removed Clippy master branch; reviewers should verify the lint lane is green and inspect its Whitaker diagnostics.

File-Level Changes

Change Details Files
Repin the Whitaker installation action to an approved shared-actions revision that uses whitaker-installer 0.2.11 and a verified Clippy snapshot.
  • Replace the existing action commit with the approved 5a99aed7 revision.
  • Add an inline comment documenting the shared-actions commit and installer version.
  • Keep the workflow structure and all other files unchanged.
.github/workflows/ci.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-30T03:14:43.762168Z 804d1d2 PR opened
🔒 Security Review ✅ Completed 2026-10-30T03:15:49.338090Z 804d1d2 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Review in 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

  • Pin the Whitaker installation action in .github/workflows/ci.yml to shared-actions revision 5a99aed7 (whitaker-installer 0.2.11).

Walkthrough

The CI workflow now pins the Whitaker installer to shared-actions revision 5a99aed7, annotated as whitaker-installer 0.2.11.

Changes

Whitaker CI installer pin

Layer / File(s) Summary
Update the CI action pin
.github/workflows/ci.yml
The workflow now uses shared-actions revision 5a99aed7 for the Whitaker installer.

Possibly related issues

  • leynos/shared-actions#650 — The issue describes the cold-install failure addressed by the updated installer revision.
  • leynos/whitaker#530 — The issue covers adoption of the released Whitaker bootstrap; this change updates a consumer to use that action.

Possibly related PRs

Priority: Normal

Change: Bug fix

Merge Risk: Minimal · previous review 804d1

No actionable merge-blocking risk was identified.

Pre-merge checks: Passed 14 · Failed 1

Failed Failed checks: 1 warning

Check name Status Explanation Resolution
Developer Documentation Warning The pull request changes the Whitaker CI tooling pin from shared-actions revision 013346cc to 5a99aed7 and that action defaults to whitaker-installer 0.2.11 (the linked leynos/shared-actions… Update docs/developers-guide.md in the Whitaker tool-installation section. State that the pinned action revision uses whitaker-installer 0.2.11, provisions the verified Clippy snapshot for the Dylint driver, and can rebuild the cached…
Passed Passed checks: 14 passed
Check name Status Explanation
Title check Passed The title clearly describes the main change: repinning the Whitaker installation action to revision 5a99aed7. No roadmap item or GitHub issue number requires inclusion in the title.
Description check Passed The description directly explains the Whitaker action repin, its purpose, scope, and validation criteria. It is related to the changeset.
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
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.
Testing (Overall) Passed PASS. The pull request changes one uses: reference in .github/workflows/ci.yml; it does not add repository functionality or local Whitaker logic. The referenced action is a third-party installer. …
User-Facing Documentation Passed The pull request changes only the pinned install-whitaker GitHub Actions reference in .github/workflows/ci.yml (one line). It changes CI tool provisioning and introduces no user-facing functionali…
Module-Level Documentation Passed Pass the check. The pull request changes only the Whitaker action revision in .github/workflows/ci.yml; it adds no module or module code. Therefore, it introduces no module-level documentation failu…
Testing (Unit And Behavioural) Passed PASS — the pull request changes only the SHA of the existing Whitaker installer step in .github/workflows/ci.yml (base 013346cc… to head 5a99aed7…). It adds no local application behaviour that n…
Testing (Property / Proof) Passed Pass this check. The pull request changes only the Whitaker action pin in .github/workflows/ci.yml; it introduces no code invariant, range of inputs, state transition, lemma, or proof assumption tha…
Testing (Compile-Time / Ui) Passed PASS: The pull request changes only the pinned install-whitaker action reference in .github/workflows/ci.yml. It introduces no Rust or TypeScript compile-time behaviour and no text, structured, or…
Unit Architecture Passed Accept this change. The pull request changes only the pinned revision on the existing Install Whitaker workflow step. It does not add queries, commands, dependencies, state mutation, or new responsi…
Domain Architecture Passed The pull request changes only .github/workflows/ci.yml. It repins the install-whitaker GitHub Action and adds a version comment. It does not change domain logic, adapters, persistence, transport, …
Observability Passed Pass this check. The pull request changes one CI-only install-whitaker SHA in .github/workflows/ci.yml (line 326); it does not change a production service or request path. The lint-test job expo…
Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Full details: Testing (Overall)

Explanation

PASS. The pull request changes one uses: reference in .github/workflows/ci.yml; it does not add repository functionality or local Whitaker logic. The referenced action is a third-party installer. The check therefore does not require a new test for the installer implementation. Existing CI still runs make lint, whose lint-whitaker target invokes Whitaker across the Rust workspace (Makefile:536-542).

Full details: User-Facing Documentation

Explanation

The pull request changes only the pinned install-whitaker GitHub Actions reference in .github/workflows/ci.yml (one line). It changes CI tool provisioning and introduces no user-facing functionality or behaviour. No update to docs/users-guide.md is required.

Full details: Module-Level Documentation

Explanation

Pass the check. The pull request changes only the Whitaker action revision in .github/workflows/ci.yml; it adds no module or module code. Therefore, it introduces no module-level documentation failure.

Full details: Testing (Unit And Behavioural)

Explanation

PASS — the pull request changes only the SHA of the existing Whitaker installer step in .github/workflows/ci.yml (base 013346cc… to head 5a99aed7…). It adds no local application behaviour that needs unit tests. The existing lint-test workflow exercises the functional boundary: it installs Whitaker, then runs make lint; lint-whitaker invokes the installed whitaker wrapper for the Rust workspace. The referenced shared action also has behavioural coverage for verified installation, cache reuse, and installer failure paths at leynos/shared-actions commit 5a99aed78ce68dcebd3052b75c31e6f173162b1e (.github/actions/install-whitaker/tests/test_install_whitaker_install.py:90-133 and tests/test_install_whitaker_run_step.py:175-214). No additional local unit test would provide meaningful coverage for this pin-only change.

Full details: Testing (Property / Proof)

Explanation

Pass this check. The pull request changes only the Whitaker action pin in .github/workflows/ci.yml; it introduces no code invariant, range of inputs, state transition, lemma, or proof assumption that requires property testing or exhaustive proof.

Full details: Testing (Compile-Time / Ui)

Explanation

PASS: The pull request changes only the pinned install-whitaker action reference in .github/workflows/ci.yml. It introduces no Rust or TypeScript compile-time behaviour and no text, structured, or UI output requiring trybuild or snapshot tests.

Full details: Unit Architecture

Explanation

Accept this change. The pull request changes only the pinned revision on the existing Install Whitaker workflow step. It does not add queries, commands, dependencies, state mutation, or new responsibilities. The existing action contract and Whitaker references remain unchanged.

Full details: Domain Architecture

Explanation

The pull request changes only .github/workflows/ci.yml. It repins the install-whitaker GitHub Action and adds a version comment. It does not change domain logic, adapters, persistence, transport, or infrastructure code boundaries. The Domain Architecture check passes.

Full details: Observability

Explanation

Pass this check. The pull request changes one CI-only install-whitaker SHA in .github/workflows/ci.yml (line 326); it does not change a production service or request path. The lint-test job exposes installation and lint failures through named failed steps (lines 325-326 and 410-411), and it records job summaries for compiler-cache results (lines 428-440). The pinned shared action also emits bounded cache, transfer, digest, source-selection, and failure diagnostics to the GitHub step summary at commit 5a99aed78ce68dcebd3052b75c31e6f173162b1e (.github/actions/install-whitaker/action.yml, lines 236-247 and 920-1021). No additional production metrics, traces, or alerts are required.

Full details: Developer Documentation

Explanation

The pull request changes the Whitaker CI tooling pin from shared-actions revision 013346cc to 5a99aed7 and that action defaults to whitaker-installer 0.2.11 (the linked leynos/shared-actions action manifest at commit 5a99aed78ce68dcebd3052b75c31e6f173162b1e, .github/actions/install-whitaker/action.yml, lines 5-16). The pull request changes only .github/workflows/ci.yml; docs/developers-guide.md still documents only 0.2.9 or later at lines 943-962. It does not document the new 0.2.11 verified Clippy snapshot bootstrap or its cold-driver-build implication.

Resolution

Update docs/developers-guide.md in the Whitaker tool-installation section. State that the pinned action revision uses whitaker-installer 0.2.11, provisions the verified Clippy snapshot for the Dylint driver, and can rebuild the cached driver once on a cold cache. Keep the action pin and the documented installer version aligned. Add an ADR or design-document update only if this pin represents a broader architectural decision; the current evidence does not require one.

Pin the workflow to the shared revision.
Keep Whitaker’s installer reference aligned.
Let CI call the updated action.
Carry the version through the YAML.
Run the checks with the new pin.

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

codescene-access[bot]

This comment was marked as outdated.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hey - I've found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path=".github/workflows/ci.yml" line_range="326" />
<code_context>

       - name: Install Whitaker
-        uses: leynos/shared-actions/.github/actions/install-whitaker@013346ccfd37bd1e02eb430525233f1a4cd942b8
+        uses: leynos/shared-actions/.github/actions/install-whitaker@5a99aed78ce68dcebd3052b75c31e6f173162b1e # shared-actions 5a99aed7 (whitaker-installer 0.2.11)

       - name: Validate Mermaid diagrams
</code_context>
<issue_to_address>
**Lint workflow exceeds line limit**

When the lint job runs yamllint, `yamllint` rejects this `uses:` line because its action pin and inline comment exceed the configured 120-character limit, so the lint job fails.

Move the revision comment to a separate line or shorten it so the workflow line stays within 120 characters.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread .github/workflows/ci.yml Outdated

- name: Install Whitaker
uses: leynos/shared-actions/.github/actions/install-whitaker@013346ccfd37bd1e02eb430525233f1a4cd942b8
uses: leynos/shared-actions/.github/actions/install-whitaker@5a99aed78ce68dcebd3052b75c31e6f173162b1e # shared-actions 5a99aed7 (whitaker-installer 0.2.11)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔴 Critical · Lint workflow exceeds line limit

When the lint job runs yamllint, yamllint rejects this uses: line because its action pin and inline comment exceed the configured 120-character limit, so the lint job fails.

Move the revision comment to a separate line or shorten it so the workflow line stays within 120 characters.

Prompt for AI agents
In `.github/workflows/ci.yml` at line 326:

**Lint workflow exceeds line limit**

When the lint job runs yamllint, `yamllint` rejects this `uses:` line because its action pin and inline comment exceed the configured 120-character limit, so the lint job fails.

Move the revision comment to a separate line or shorten it so the workflow line stays within 120 characters.

@leynos
leynos merged commit f868a6f into main Oct 30, 2026
21 checks passed
@leynos
leynos deleted the repin-install-whitaker-0-2-11 branch October 30, 2026 04:30
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