ci(pacquet): pin cargo-dylint to 6.0.0 to unblock CI#11969
Merged
Conversation
trailofbits/dylint 6.0.1 (published 2026-05-26 17:51 UTC) ships
prebuilt cargo-binstall artifacts that bake in a path from the
dylint repo's own CI workspace:
error: failed to get `dylint_driver` as a dependency of package
`dylint_driver-nightly-2026-04-16-x86_64-unknown-linux-gnu`
Caused by:
failed to read `/home/runner/work/dylint/dylint/driver/Cargo.toml`
Caused by:
No such file or directory (os error 2)
Downstream runners don't have that workspace, so the driver bootstrap
fails before any lint runs and the Dylint job goes red on every PR.
6.0.0 (the version main was passing with 90 minutes earlier) is
unaffected. Pin both binaries until upstream cuts 6.0.2.
---
Written by an agent (Claude Code, claude-opus-4-7).
Review Summary by QodoPin cargo-dylint and dylint-link to 6.0.0 to fix CI
WalkthroughsDescription• Pin cargo-dylint and dylint-link to 6.0.0 to fix CI failures • Version 6.0.1 contains broken binstall artifacts with hardcoded paths • Unblocks Dylint job that was failing on all PRs Diagramflowchart LR
A["dylint 6.0.1 release"] -->|"broken binstall artifacts"| B["CI job fails"]
C["Pin to 6.0.0"] -->|"working version"| D["CI job passes"]
File Changes1. .github/workflows/pacquet-ci.yml
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
🔇 Additional comments (1)
📝 WalkthroughWalkthroughThe PR updates the GitHub Actions CI workflow to pin ChangesDylint Tool Version Pinning
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
trailofbits/dylint 6.0.1 (published 2026-05-26 17:51 UTC) ships prebuilt
cargo-binstallartifacts whose driver-bootstrap step references the dylint repo's own CI workspace path:Downstream runners don't have
/home/runner/work/dylint/dylint/, so the bootstrap fails before any lint runs and the Dylint job goes red on every open PR (e.g. #11967, #11968). 6.0.0 — the versionmainwas green on 90 minutes before the release dropped — is unaffected.Pin both
cargo-dylintanddylint-linkto6.0.0until upstream cuts 6.0.2.Test plan
Written by an agent (Claude Code, claude-opus-4-7).
Summary by CodeRabbit