rust-lang / rust-lang/rfcs

RFC: Add `--git-repos` flag to `cargo update`

Open
#3,298 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Markdown
Stars
6.6k
Forks
1.7k
Avg merge
16h 14m
Merged PRs (30d)
1

Description

I've observed a case where a developer was pinning everything inside of Cargo.toml except their Git Repositories for the mere benefit of having an easy method to update all of their git dependencies. All of their internal crates were in git repositories. That is to say all of their versions strings where like =0.1.2. This presents a problem as you have to sacrifice the intended functionality of cargo update which can provide security patches and ease upgrades.

Currently, there is a better way to do this with cargo update -p foo -p bar. It would be nice if we could do cargo update --git-repos which would update only the git repositories such that effectively everything else was ignored (or pinned to the current version).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the cargo update command and the proposed --git-repos flag, but no files, tests, or implementation entry points. Start by researching how cargo update -p selects dependencies and how the RFC process captures command behavior. Done means an accepted design that specifies which dependencies are updated and which remain pinned.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.