Skip to content

fix(ci): restore dylint nightly toolchain visibility and adopt setup-soldr native dylint cache - #174

Merged
zackees merged 1 commit into
mainfrom
fix/lint-dylint-toolchain
Jun 12, 2026
Merged

zackees merged 1 commit into
mainfrom
fix/lint-dylint-toolchain

Conversation

@zackees

@zackees zackees commented Jun 12, 2026

Copy link
Copy Markdown
Member

Summary

  • Fixes the lint regression introduced in chore(ci): reuse CI artifacts in auto-release, cache dylint toolchain #172: soldr rustup toolchain install placed the dylint nightly in soldr's private toolchain home instead of the setup-soldr-exported RUSTUP_HOME, so the dylint driver build failed with E0463: can't find crate for rustc_driver on all four lint platforms (visible on PR chore(release): bump version to 2.0.12 #173).
  • Installs the nightly with bare rustup (unconditional — the toolchain is not part of any dylint cache paths).
  • Drops the hand-rolled actions/cache step (its ~/.rustup/~/.dylint_drivers paths never matched the managed homes anyway) in favor of setup-soldr's native dylint-cache inputs, gating the cargo install steps on the dylint-cache-hit output.

Refs #170

Test plan

  • actionlint .github/workflows/_lint.yml passes
  • All four lint CI jobs green on this PR

…ative dylint cache

The #172 change routed the dylint nightly install through `soldr rustup`,
which installs into soldr's private toolchain home instead of the
setup-soldr-exported RUSTUP_HOME, so the dylint driver build lost its
rustc-dev components and failed with E0463 on all four lint platforms.

Install the nightly with bare rustup (unconditional — it is not part of
the dylint cache), and replace the hand-rolled actions/cache step with
setup-soldr's native dylint-cache inputs, gating the cargo-dylint /
dylint-link installs on its dylint-cache-hit output.

Refs #170

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@zackees
zackees merged commit ffca6f9 into main Jun 12, 2026
22 checks passed
@zackees
zackees deleted the fix/lint-dylint-toolchain branch June 12, 2026 11:53
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