Skip to content

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

Merged
leynos merged 1 commit into
mainfrom
repin-install-whitaker-5a99aed7
Oct 31, 2026
Merged

leynos merged 1 commit into
mainfrom
repin-install-whitaker-5a99aed7

Conversation

@leynos

@leynos leynos commented Oct 31, 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). 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 files changed are (.github/workflows/ci.yml ) and only the install-whitaker revision moves. The previous pin was not an approved QG-002 revision.

Other Whitaker paths

None found: no bare cargo dylint, cargo binstall whitaker, hand-rolled installer or explicit installer-version 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

Repin the CI Whitaker installation action to the approved revision to keep Dylint driver builds working.

Bug Fixes:

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

CI:

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

Upstream Dylint 6.0.1 clones Clippy's master branch, which no longer exists, so every cold Whitaker driver build fails. shared-actions 5a99aed7 (#651), approved as a root by concordat QG-002, makes install-whitaker default to whitaker-installer 0.2.11, which builds the driver from a verified Clippy snapshot.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 31, 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-31T01:01:52.128666Z 6dd618d PR opened
🔒 Security Review ✅ Completed 2026-10-31T01:02:50.977142Z 6dd618d 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 31, 2026 •

Copy link
Copy Markdown
Contributor

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

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Team
  • Run ID: b344e632-fbb9-42fc-8c3d-1a57dee0be99
Commits

Reviewing files that changed from the base of the PR and between 33eb360 and 6dd618d.

Files selected for processing: 1
  • .github/workflows/ci.yml

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

Summary

  • Pin install-whitaker in .github/workflows/ci.yml to shared-actions revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e. This revision defaults to whitaker-installer 0.2.11, which builds the Dylint driver from a verified Clippy snapshot.

No new execplan was identified. The stated CI gate result is not reported.

Walkthrough

The CI workflow now pins the Whitaker Dylint installation action to revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e.

Changes

CI action pin

Layer / File(s) Summary
Update the Whitaker action pin
.github/workflows/ci.yml
The installation step now uses revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e instead of 872f59f53717b5bebe8e24b2f4a7496b089a939a.

Possibly related issues

  • Whitaker issue 530 tracks the released installer and bootstrap acceptance evidence supplied by the shared action revision used here.

Possibly related PRs

Suggested labels: Issue

Change: Bug fix

Merge Risk: Minimal · up to 6dd61

No actionable merge-blocking risk was identified in the reviewed change.

Caution

Pre-merge checks failed

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

  • Ignore

Failed Failed checks: 1 error · 1 warning

Check name Status Explanation Resolution
Testing (Unit And Behavioural) Error Add behavioural coverage for the changed CI integration. The PR changes only the install-whitaker action revision in .github/workflows/ci.yml. No test file changes cover this action. Existing work… Add a workflow contract test for the Whitaker action reference and its ordering before make lint. Run the lint lane with a cold cache and verify that the pinned installer builds the driver and that make lint completes successfully.
Developer Documentation Warning The pull request changes the CI tooling pin from install-whitaker revision 872f59f... to 5a99aed.... The new revision changes the Whitaker installer behaviour to whitaker-installer 0.2.11, but… Update docs/developers-guide.md with the Whitaker installation requirement and the reason for the pinned install-whitaker revision. Keep the documentation aligned with the CI workflow, or do not change the tooling requirement.
Passed Passed checks: 13 passed
Check name Status Explanation
Title check Passed Keep the title. It clearly describes the change to repin the Whitaker installation action and does not require a repository issue number based on the supplied context.
Description check Passed Keep the description. It explains the Whitaker repin, the failure cause, the affected file, and the validation gate.
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 this check. The pull request changes one workflow action pin only: it moves install-whitaker to a new third-party revision. It adds no repository functionality or local behavioural logic. The w…
User-Facing Documentation Passed The pull request changes only the pinned revision of the install-whitaker action in .github/workflows/ci.yml. This updates CI tooling and does not introduce or change user-facing functionality or …
Module-Level Documentation Passed Pass the check. The pull request changes only the revision of the install-whitaker action in .github/workflows/ci.yml. It introduces no module, so the module-level documentation requirement does n…
Testing (Property / Proof) Passed The pull request changes one GitHub Actions revision in .github/workflows/ci.yml. It introduces no invariant over inputs, states, orderings, or transitions, and it introduces no lemma or proof assum…
Testing (Compile-Time / Ui) Passed Pass the testing check. The pull request changes only the install-whitaker revision in .github/workflows/ci.yml; it changes no Rust or TypeScript compile-time behaviour and adds no text or UI outp…
Unit Architecture Passed Pass. The pull request changes only the pinned revision of the existing install-whitaker GitHub Action in .github/workflows/ci.yml. It does not change queries, commands, fallible APIs, dependency …
Domain Architecture Passed Pass this check. The pull request changes only the pinned revision of the CI install-whitaker action in .github/workflows/ci.yml. It does not change domain code, adapters, repositories, commands, …
Observability Passed PASS — The pull request changes only the pinned revision of the existing install-whitaker CI action in .github/workflows/ci.yml. It introduces no production runtime behaviour, service boundary, qu…
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 this check. The pull request changes one workflow action pin only: it moves install-whitaker to a new third-party revision. It adds no repository functionality or local behavioural logic. The workflow already runs make lint and make test-workflow-contracts. The check does not require tests to verify that a third-party tool or action works as advertised.

Full details: User-Facing Documentation

Explanation

The pull request changes only the pinned revision of the install-whitaker action in .github/workflows/ci.yml. This updates CI tooling and does not introduce or change user-facing functionality or behaviour. No users-guide update is required.

Full details: Module-Level Documentation

Explanation

Pass the check. The pull request changes only the revision of the install-whitaker action in .github/workflows/ci.yml. It introduces no module, so the module-level documentation requirement does not apply.

Full details: Testing (Property / Proof)

Explanation

The pull request changes one GitHub Actions revision in .github/workflows/ci.yml. It introduces no invariant over inputs, states, orderings, or transitions, and it introduces no lemma or proof assumption. Property testing and exhaustive proof are therefore not applicable.

Full details: Testing (Compile-Time / Ui)

Explanation

Pass the testing check. The pull request changes only the install-whitaker revision in .github/workflows/ci.yml; it changes no Rust or TypeScript compile-time behaviour and adds no text or UI output. Trybuild or snapshot tests are therefore not applicable.

Full details: Unit Architecture

Explanation

Pass. The pull request changes only the pinned revision of the existing install-whitaker GitHub Action in .github/workflows/ci.yml. It does not change queries, commands, fallible APIs, dependency injection, state mutation, or tests. The Unit Architecture conditions do not apply to this pin-only workflow change.

Full details: Domain Architecture

Explanation

Pass this check. The pull request changes only the pinned revision of the CI install-whitaker action in .github/workflows/ci.yml. It does not change domain code, adapters, repositories, commands, or business rules. Therefore, it introduces no domain-boundary violation.

Full details: Observability

Explanation

PASS — The pull request changes only the pinned revision of the existing install-whitaker CI action in .github/workflows/ci.yml. It introduces no production runtime behaviour, service boundary, queue, retry, cache, or resource-consumption change. The existing Lint step remains directly after the installation step and reports Whitaker diagnostics through CI logs. No new metrics, tracing, alerts, or logging are required by this pin-only change.

Full details: Testing (Unit And Behavioural)

Explanation

Add behavioural coverage for the changed CI integration. The PR changes only the install-whitaker action revision in .github/workflows/ci.yml. No test file changes cover this action. Existing workflow tests cover unrelated contracts, and the build-standard tests do not inspect Whitaker installation. The change affects the externally observable CI workflow and its network-backed installer boundary.

Resolution

Add a workflow contract test for the Whitaker action reference and its ordering before make lint. Run the lint lane with a cold cache and verify that the pinned installer builds the driver and that make lint completes successfully.

Full details: Developer Documentation

Explanation

The pull request changes the CI tooling pin from install-whitaker revision 872f59f... to 5a99aed.... The new revision changes the Whitaker installer behaviour to whitaker-installer 0.2.11, but the only changed file is .github/workflows/ci.yml. docs/developers-guide.md documents the make lint command and Whitaker rule behaviour, but it does not document the installer, the pin, or the cold-build requirement. No design or roadmap change applies.

Resolution

Update docs/developers-guide.md with the Whitaker installation requirement and the reason for the pinned install-whitaker revision. Keep the documentation aligned with the CI workflow, or do not change the tooling requirement.

Pin the action to its new place
Let Whitaker follow the trace
One revision, clearly in view
The workflow knows which commit to use
Keep the linting step on cue

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

@sourcery-ai

sourcery-ai Bot commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Sorry @leynos, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 5 days and 20 hours by commenting @sourcery-ai review. Upgrade to get a review now.

@sourcery-ai

sourcery-ai Bot commented Oct 31, 2026

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

Reviewer's Guide

The CI workflow makes a pin-only update to the Whitaker installer action, switching to the approved shared-actions revision for whitaker-installer 0.2.11 and fixing cold Dylint driver builds affected by upstream Clippy branch removal.

Sequence diagram for the pinned Whitaker CI lint setup

sequenceDiagram
    participant CI as CI lint job
    participant Action as install-whitaker action
    participant Installer as whitaker-installer 0.2.11
    participant Dylint as Dylint driver
    participant Lint as make lint

    CI->>Action: Run pinned revision 5a99aed7
    Action->>Installer: Install whitaker-installer 0.2.11
    Installer->>Dylint: Build driver from verified Clippy snapshot
    Dylint-->>Action: Driver ready
    Action-->>CI: Whitaker suite installed
    CI->>Lint: Run make lint
    Lint->>Dylint: Execute lint checks
    Dylint-->>CI: Return diagnostics
Loading

File-Level Changes

Change Details Files
Repin the Whitaker installation action to an approved shared-actions revision that uses whitaker-installer 0.2.11.
  • Replace the previous action SHA with the approved 5a99aed7 revision.
  • Use the updated installer behavior to build the Dylint driver from a verified Clippy snapshot, avoiding the obsolete upstream master reference.
.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

@coderabbitai coderabbitai Bot added the Issue label Oct 31, 2026

@coderabbitai coderabbitai 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.

Pre-merge checks failed. Please resolve the failing checks before merging.

@leynos
leynos merged commit 2804159 into main Oct 31, 2026
6 checks passed
@leynos
leynos deleted the repin-install-whitaker-5a99aed7 branch October 31, 2026 01:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant