Skip to content

Ensure all mentions of cargo-install are --locked#21592

Merged
gankra-oai merged 2 commits intomainfrom
gankra/lock-more
May 7, 2026
Merged

Ensure all mentions of cargo-install are --locked#21592
gankra-oai merged 2 commits intomainfrom
gankra/lock-more

Conversation

@gankra-oai
Copy link
Copy Markdown
Contributor

There's already a preference for this in the codebase, but a few of them have drifted away. Generally --locked is preferred to reduce exposure to supply-chain attacks (and just generally improve reproducibility).

In an ideal world these dependencies would maybe even be pinned to versions but Cargo is kinda bad at that for devtools. Still better to use --locked than not.

@gankra-oai gankra-oai requested a review from ww-oai May 7, 2026 21:48
@gankra-oai gankra-oai requested a review from a team as a code owner May 7, 2026 21:48
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 7, 2026

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@gankra-oai
Copy link
Copy Markdown
Contributor Author

I have read the CLA Document and I hereby sign the CLA

github-actions Bot added a commit that referenced this pull request May 7, 2026
@gankra-oai
Copy link
Copy Markdown
Contributor Author

Realized the one change I made to core was spurious as it's not a real invocation of cargo install (and I don't think any other the tests in there need that treatment either).

@gankra-oai gankra-oai merged commit 80a8563 into main May 7, 2026
26 checks passed
@gankra-oai gankra-oai deleted the gankra/lock-more branch May 7, 2026 22:30
@github-actions github-actions Bot locked and limited conversation to collaborators May 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants