Add a repository for cargo-lockfile-sync

[oli-obk]

Originally suggested in rust-lang/rust#57443

This project is a custom crate that is independent of rustc, but will keep our toml files in sync with the lock files (rationale, see linked issue). Instead of putting that code in-tree, I want it to start out of tree immediately, since it's generally useful.

[oli-obk]

@rfcbot pr merge

I propose we start out of tree immediately instead of pulling it out of tree later. Thus, this project starts out with no code, just an empty project with licenses and a README. The code already exists, but can only be added to an existing project by the author (see linked issue for details).

[rfcbot]

Team member @oli-obk has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Zoxc
• @cramertj
• @eddyb
• @estebank
• @michaelwoerister
• @nagisa
• @nikomatsakis
• @oli-obk
• @petrochenkov
• @pnkfelix
• @varkor

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

[Zoxc]

It seems like this tool wouldn't fall under the compiler team.

[petrochenkov]

Why is updating versions in Cargo.tomls useful?

I assumed that they are supposed to be coarse-grained like regex = "1" (unless a specific bug-fix release regex = "1.X" is required for correct work).

[oli-obk]

Why is updating versions in Cargo.tomls useful?

The original problem was that there are PRs that update just the lockfile, which seemed wrong to me. One example is rust-lang/rust#57435 where a version bump was necessary, but not reflected in the Cargo.toml. I don't know how many other such minimum version requirements are encoded solely in the Cargo.lock without the minimum version being specified in the Cargo.toml.

It seems like this tool wouldn't fall under the compiler team.

Is this more infra then?

[rfcbot]

🔔 This is now entering its final comment period, as per the review above. 🔔

psst @oli-obk, I wasn't able to add the final-comment-period label, please do so.

[eddyb]

I forgot to mention that cargo-edit might be a good place to put this.

[rfcbot]

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

The RFC will be merged soon.

psst @oli-obk, I wasn't able to add the finished-final-comment-period label, please do so.

[eddyb]

Come to think more of it, this seems perfectly fine for the cargo upgrade component of cargo-edit.
I probably should've cc'd @killercup from the start, oops.
Nevermind, @oli-obk already opened killercup/cargo-edit#297.