Skip to content

Repin install-whitaker to the 0.2.11 revision - #161

Merged
leynos merged 1 commit into
mainfrom
install-whitaker-0211
Oct 30, 2026
Merged

leynos merged 1 commit into
mainfrom
install-whitaker-0211

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 by concordat #331). That revision defaults whitaker-installer to 0.2.11, which builds the Dylint driver from a verified Clippy snapshot; upstream Dylint 6.0.1 clones Clippy's deleted master branch, so every cold Whitaker driver build was failing and the lint lane was red.

  • Pin-only change to the workflow files; no trailing version comment is added (it broke exact-match contracts elsewhere).
  • Any explicit installer-version / WHITAKER_INSTALLER_VERSION is set to 0.2.11.
  • Other Whitaker paths outside the action (cargo dylint, binstall whitaker, whitaker-installer, DYLINT_*): none that install or run Dylint outside the action and wrappers, unless listed below.

Summary by Sourcery

Repin the CI Whitaker installation action to restore reliable Dylint linting.

Bug Fixes:

  • Update the CI Whitaker installation action to a revision that uses Whitaker installer 0.2.11, restoring reliable cold-build lint runs.

CI:

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

Pin install-whitaker to shared-actions 5a99aed78ce68dcebd3052b75c31e6f173162b1e,
which defaults the installer to 0.2.11 and builds the Dylint driver from a
verified Clippy snapshot. Upstream Dylint 6.0.1 clones Clippy's deleted master
branch, so every cold driver build failed. Any explicit installer-version is set
to 0.2.11.
@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-30T05:14:52.715377Z 8d6e78e PR opened
🔒 Security Review ✅ Completed 2026-10-30T05:15:42.688483Z 8d6e78e 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

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: 922bbbe0-ac32-4872-addc-2fc3b36af1ed
Commits

Reviewing files that changed from the base of the PR and between fd7d819 and 8d6e78e.

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 1 review per hour.

Repin the Install Whitaker Dylint suite step in .github/workflows/ci.yml to shared action revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e.

Walkthrough

The CI workflow now uses revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e of the shared install-whitaker action instead of the previous revision.

Changes

CI installer reference

Layer / File(s) Summary
Update the installer pin
.github/workflows/ci.yml
Pin the Whitaker installer step to revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e.

Possibly related issues

  • leynos/axinite#675 — The workflow changes the immutable install-whitaker reference discussed in this issue; this PR does not change contract tests.
  • leynos/whitaker#530 — The new action revision adopts the shared installer release through a downstream workflow pin.
  • leynos/whitaker#529 — The new pin adopts a revision associated with the Clippy snapshot bootstrap policy; this PR does not change adapters.

Possibly related PRs

Priority: Normal

Change: Bug fix

Merge Risk: Minimal · up to 8d6e7

No actionable merge-blocking risk is identified in this pin-only workflow change.

Pre-merge checks: Passed 15
Check name Status Explanation
Title check Passed The title directly identifies the workflow pin change and the target 0.2.11 revision. No roadmap item or GitHub issue number is required by the supplied context.
Description check Passed The description explains the pin update, target revision, installer version, and failure it addresses. It is directly 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 testing check. The pull request changes only the pinned revision of the third-party install-whitaker GitHub Action in .github/workflows/ci.yml; it adds no repository functionality or loca…
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 …
Developer Documentation Passed Pass the developer documentation check. The pull request changes only the pinned SHA of the existing install-whitaker CI action in .github/workflows/ci.yml. It adds no internal API, architectural …
Module-Level Documentation Passed Pass. The pull request changes only one GitHub Actions pin in .github/workflows/ci.yml. It adds or changes no source module, so this module-level documentation check is not applicable.
Testing (Unit And Behavioural) Passed PASS — The pull request changes only one GitHub Actions revision in .github/workflows/ci.yml. It adds no local production behaviour, unit-testable logic, edge case, or error path. The workflow still…
Testing (Property / Proof) Passed Pass this check. The pull request changes one GitHub Actions reference from one immutable install-whitaker revision to another. It introduces no input-dependent invariant, state transition, lemma, o…
Testing (Compile-Time / Ui) Passed PASS. The pull request changes one GitHub Actions reference in .github/workflows/ci.yml from one install-whitaker revision to another. It adds no Rust or TypeScript compile-time behaviour and prod…
Unit Architecture Passed PASS. Treat this as an inapplicable architecture change: the pull request changes only one GitHub Actions revision in .github/workflows/ci.yml (line 39). It adds no query, command, fallible API, dep…
Domain Architecture Passed The pull request changes one GitHub Actions reference only: it repins install-whitaker to revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e. It changes no domain code, adapters, repositories, comm…
Observability Passed PASS. The pull request changes only the pinned revision of the named Install Whitaker Dylint suite GitHub Actions step in .github/workflows/ci.yml. It changes CI tool provisioning, not production …
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 testing check. The pull request changes only the pinned revision of the third-party install-whitaker GitHub Action in .github/workflows/ci.yml; it adds no repository functionality or local configuration logic. The check explicitly does not require tests to verify third-party tools. Existing CI still runs lint, tests, and workflow contract checks.

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 user-guide update is required.

Full details: Developer Documentation

Explanation

Pass the developer documentation check. The pull request changes only the pinned SHA of the existing install-whitaker CI action in .github/workflows/ci.yml. It adds no internal API, architectural boundary, design decision, project build requirement, or new developer-facing tool. Existing documentation covers workflow pin policy and the make lint build behaviour. No roadmap or execplan update is required.

Full details: Testing (Unit And Behavioural)

Explanation

PASS — The pull request changes only one GitHub Actions revision in .github/workflows/ci.yml. It adds no local production behaviour, unit-testable logic, edge case, or error path. The workflow still exercises the installed Whitaker suite through make lint, and the repository retains workflow contract tests. No additional unit test is required for this pin-only change.

Full details: Testing (Property / Proof)

Explanation

Pass this check. The pull request changes one GitHub Actions reference from one immutable install-whitaker revision to another. It introduces no input-dependent invariant, state transition, lemma, or proof assumption. Property tests and exhaustive proofs are therefore not applicable.

Full details: Testing (Compile-Time / Ui)

Explanation

PASS. The pull request changes one GitHub Actions reference in .github/workflows/ci.yml from one install-whitaker revision to another. It adds no Rust or TypeScript compile-time behaviour and produces no text-based or UI output requiring snapshot coverage. The trybuild and snapshot requirements are therefore not applicable.

Full details: Unit Architecture

Explanation

PASS. Treat this as an inapplicable architecture change: the pull request changes only one GitHub Actions revision in .github/workflows/ci.yml (line 39). It adds no query, command, fallible API, dependency, state mutation, or test unit. No explicit Unit Architecture failure condition is introduced.

Full details: Domain Architecture

Explanation

The pull request changes one GitHub Actions reference only: it repins install-whitaker to revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e. It changes no domain code, adapters, repositories, commands, or persistence boundaries. The Domain Architecture check therefore has no failure condition to report.

Full details: Observability

Explanation

PASS. The pull request changes only the pinned revision of the named Install Whitaker Dylint suite GitHub Actions step in .github/workflows/ci.yml. It changes CI tool provisioning, not production runtime behaviour. The workflow already exposes separate Install Whitaker Dylint suite and Lint failure boundaries, and no new service, queue, storage, throughput, latency, or retry behaviour requires metrics or tracing.

Pin the action, set the flow,
Let the Whitaker checks now go.
A new revision takes its place,
CI follows the updated trace.
Keep the workflow pin in view.

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

@sourcery-ai

sourcery-ai Bot commented Oct 30, 2026

Copy link
Copy Markdown

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 6 days and 16 hours by commenting @sourcery-ai review. Upgrade to get a review now.

@sourcery-ai

sourcery-ai Bot commented Oct 30, 2026

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

Reviewer's Guide

The CI workflow updates the install-whitaker action to the approved shared-actions revision that uses whitaker-installer 0.2.11 and avoids failing cold Whitaker driver builds; no other installation paths or workflow behavior change.

Sequence diagram for the pinned Whitaker CI installation

sequenceDiagram
    participant CI as GitHub Actions CI
    participant Action as install-whitaker action
    participant Installer as whitaker-installer 0.2.11
    participant Lint as make lint

    CI->>Action: Run pinned revision 5a99aed78ce68dcebd3052b75c31e6f173162b1e
    Action->>Installer: Install Whitaker toolchain
    Installer-->>Action: Provide verified Dylint driver
    Action-->>CI: Installation succeeds
    CI->>Lint: Run make lint
    Lint-->>CI: Lint lane completes
Loading

File-Level Changes

Change Details Files
Repin the shared Whitaker installation action to a revision that defaults to whitaker-installer 0.2.11.
  • Replace the action commit SHA used by the CI lint workflow.
  • Rely on the pinned action revision for a verified Clippy snapshot, preventing cold driver builds from following Dylint 6.0.1’s deleted upstream branch.
.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

@leynos
leynos merged commit 7520c79 into main Oct 30, 2026
16 of 17 checks passed
@leynos
leynos deleted the install-whitaker-0211 branch October 30, 2026 05:58
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