Can someone tell me how to fix CI to pass?

The failing CI job is right to fail: it's indicating that pulling in the new library requires new vetting. One of the core team members will have to do a cargo vet.

I'm tagged as reviewer here but I have some high-priority stuff on my plate at the moment so it may not be until sometime next week when I get to this, sorry!

Understand. Thank you!

@tamaroning I think this needs a Cargo.lock update as well (see the CI failures); would you mind doing that by doing cargo check or cargo build and then adding the updates as a new commit? (Please do not alter my vet commit; 0da9d0b needs to remain on this branch.)

Hi, I ran cargo update at your commit but nothing in Cargo.lock changed.
Do you mean cargo update?

Hi, I ran cargo update at your commit but nothing in Cargo.lock changed. Do you mean cargo update?

No, I didn't mean cargo update -- that pulls in new versions that require more vets. Would you mind force-pushing back to the prior commit to remove your latest one? (i.e., start from 0da9d0b again)

Please see the CI job failure here: that is showing that after running several cargo check commands on different crates, the lockfile is modified. You'll need to reproduce that and then create a new, separate commit on top with those changes.

Hi, I reset my local branch to 0da9d0b and ran all cargo check ...s and ./ci/vendor-wit.sh in the Monolith checks CI, but could not reproduce the diff in Cargo.lock.
Am I missing something?

Hmm, I wasn't able to reproduce that either. I re-triggered the CI jobs to see if it was some transient version issue (e.g. maybe a release of smallvec happened partway through the run or something?).

OK, that didn't work, and the new failures don't seem reproducible either. I think at this point I need to ask our resident CI herder @alexcrichton (when he's back in office) for help...

To reproduce the error you'll want to run a git rebase against the main branch. CI tests the merge of whatever main happens to be at the time the CI job starts with this PR. I'd love if we could turn that off, but github actions doesn't have a configuration knob for that I'm aware of...

Thank you. I rebased the branch and could update Cargo.lock.