Skip to content

citool: update rust crates - #161197

Open
xtqqczze wants to merge 2 commits into
rust-lang:mainfrom
xtqqczze:deps/lockfiles
Open

citool: update rust crates#161197
xtqqczze wants to merge 2 commits into
rust-lang:mainfrom
xtqqczze:deps/lockfiles

Conversation

@xtqqczze

Copy link
Copy Markdown
Contributor

No description provided.

@rustbot rustbot added A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Aug 16, 2026
@Mark-Simulacrum

Copy link
Copy Markdown
Member

Can you look for and adjust usage of citool in CI to actually pass --locked? I don't think we do that today in at least some places (https://triage.rust-lang.org/gha-logs/rust-lang/rust/95227692674?pr=161197#L2026-08-16T21:12:18.8117107Z), which means we're not necessarily using the committed lockfile.

It's technically a separate change but I think it makes sense to apply here if we're bumping dependencies. I assume you cut this as just general housekeeping rather than for a particular intended dependency bump?

@xtqqczze

Copy link
Copy Markdown
Contributor Author

My intention was to bump cc following its recent update, but I noticed it made sense to bump all the dependencies instead. The --locked flag makes sense too.

@xtqqczze
xtqqczze marked this pull request as ready for review August 16, 2026 22:22
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 16, 2026
@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Aug 16, 2026
@rustbot

rustbot commented Aug 16, 2026

Copy link
Copy Markdown
Collaborator

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: infra-ci
  • infra-ci expanded to 6 candidates
  • Random selection from Mark-Simulacrum, jdno, jieyouxu, marcoieni, ubiratansoares

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants