Update Rust crate cargo-edit to 0.13.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cargo-edit	dependencies	minor	0.8.0 -> 0.13.0

---

Release Notes

killercup/cargo-edit (cargo-edit)

v0.13.7

Compare Source

Internal

• Dependency updates

v0.13.6

Compare Source

Fixes

• (upgrade) Don't update git dependencies that were excluded

v0.13.5

Compare Source

Fixes

• Add logging

v0.13.4

Compare Source

Fixes

• Add logging
• Add -n as a short for --dry-run

v0.13.3

Compare Source

Fixes

• (upgrade) Provide more context on registry errors

v0.13.2

Compare Source

Fixes

• (upgrade) Don't silence network errors

v0.13.1

Compare Source

Performance

• Changed compilation settings

v0.13.0

Compare Source

Breaking Changes

• (upgrade) Remove of --offline as we don't have local caching for sparse registry

Fixes

• (upgrade) Switched from git to sparse registry for faster runs

v0.12.3

Compare Source

Internal

• Dependency update

v0.12.2

Compare Source

Features

• Stylize help output

v0.12.1

Compare Source

Fixes

• Fix building on nightlies

v0.12.0

Compare Source

Breaking Changes

• (rm) Removed in favor of cargo remove
• (upgrade) --recursive <true|false> now defaults to the same as --compatible <true|false>

Features

• MSRV-aware setting of version requirements with --ignore-rust-version and --rust-version <VER> flags
  • Resolver still won't be MSRV aware
  • Lack of transparency in filtering out incompatible rust-versions (no warnings, no details in errors)

Fixes

• Don't upgrade indirect dependencies with --incompatible allow --compatible deny

v0.11.11

Compare Source

upgrade

• --locked --dry-run should error if there are changes

v0.11.10

Compare Source

Fixes

upgrade

• In summary lists, coalece long lists
• Reduce padding, consuming precious vertical space on large workspaces
• Move unchanged requirements out of table unless --verbose, moving the existing --verbose to --verbose --verbose.

v0.11.9

Compare Source

Fixes

upgrade

• Report dependency tables to stdout, instead of stderr

v0.11.8

Compare Source

Internal

• Dependencies updated

v0.11.7

Compare Source

Fixes

• Improved build times

v0.11.6

Compare Source

Fixes

upgrade

• Ensure precise version setting runs
• Remove error blocking precise version setting

v0.11.5

Compare Source

v0.11.4

Compare Source

Features

set-version

• Modify workspace.package.version and all dependents, when needed

Fixes

set-version

• Update versions in workspace.dependencies in virtual workspaces
• Be more consistent with rest of cargo in output

v0.11.3

Compare Source

Fixes

• Polished help output

v0.11.2

Compare Source

Features

upgrade

• Upgrade workspace.dependencies (new in Rust 1.64)

v0.11.1

Compare Source

upgrade

• --locked --dry-run should error if there are changes

v0.11.0

Compare Source

This release is another step in our effort to find the appropriate cargo upgrade workflow for merging into cargo.

This new iteration is modeled on the idea "if we started from scratch, what
would cargo update look like?". Besides getting us to think outside
the box, I hope that we can deprecate cargo update and replace it with cargo upgrade (caution: this has not been passed by the cargo team). We need
runtime with the proposed behavior with feedback to see how well the idea works
in theory and if it justifies the ecosystem churn of deprecating cargo update.

More concretely, the approach taken in this release is a cargo update-like
command that implicitly modifies Cargo.lock.

To this end

• cargo upgrade now works on the whole workspace exclusively
  • This also resolves confusion over --package, --exclude, and the positional PKGID argument
  • This also removes any UI barriers for supporting workspace inheritance coming in 1.64
• cargo upgrade -p [email protected] will act as if cargo update -p serde --precise 1.0.100 was performed
• Compatible versions are upgraded by default
  • Pass --incompatible or --pinned to upgrade to incompatible versions
  • Disable the default with --compatible false
  • See this PR for context on the trade offs

A side benefit of this approach is that users will get an approximation of
minimal-version resolution so long as they stay within cargo add and cargo upgrade and commit their Cargo.lock file.

Please include in any
feedback:

• An evaluation of current behavior that takes into account the exiting "care abouts" or any additional we don't have listed yet
• An evaluation of how existing or new alternatives would better fit the full set of care abouts

Breaking Changes

upgrade

• Compatible versions are upgraded by default, with opt-out via --compatible false
• Pinned dependencies will be upgraded to compatible versions when --compatible true, reserving --pinned for incompatible upgrades
• Incompatible versions require opting in with -i / --incompatible
• When a version requirement is fully specified, the lock version will modified to use that version
• Exclusively operate on the workspace
• The positional argument for selecting dependencies to upgrade has moved to --package <NAME>
• --package and --exclude now take crate names rather than dependencies names (matters when dependencies are renamed)

Features

upgrade

• --recursive <true|false> for controlling how the lockfile is updated
• Update git dependencies

Fixes

upgrade

• Treat 3.2.x as pinned
• Update lockfile in offline mode
• Don't touch the lockfile in dry-run
• Prefer preserving the original version requirement over compatible version upgrades (in cases where we don't know how to preserve the format)

v0.10.4

Compare Source

Fixes

upgrade

• Hide "note" column when unused
• Summarize uninteresting rows by default

v0.10.3

Compare Source

Fixes

upgrade

• Provide table view of upgrades, like cargo outdated, to raise visibility for why a change isn't made
• Fix where we didn't respect --offline
• Fix --to-lockfile to update non-registry version requirements
• Update lockfile for upgraded requirements
• Update --help to be consistent with cargo add

rm

• Update --help to be consistent with cargo add

v0.10.2

Compare Source

Fixes

upgrade

• Only fail on bad lockfile if --to-lockfile is set

rm

• Don't duplicate error messages

v0.10.1

Compare Source

Features

upgrade

• Note the --pinned flag when pinned dependencies are skipped

Fixes

add

• Provide a failing command to tell people how to get it

v0.10.0

Compare Source

Breaking changes

• Many programmatic APIs changed
• cargo add remove in favor of the version included with cargo 1.62.0
• cargo upgrade skips pinned dependencies by default, run with --pinned to do them all
• cargo upgrade --skip-compatible is now default, run with --to-lockfile to upgrade all
• cargo upgrade now accepts dependency keys rather than crate names
• cargo upgrade now preserves version req precision
• cargo upgrade --allow-prerelease was removed to match cargo add

Fixes

All

• Align console messages
• Allow using --manifest-path with --pkgid
• Allow relative paths with --manifest-path

upgrade

• Positional arguments are now dependency keys, allowing forcing of renamed dependencies to upgrade
• Make compatible upgrades and precision preservation work together
• Cleaned up output
• Preserve user formatting of dependencies
• Don't confuse dependencies

Features

upgrade

• Always preserve version req precision
• With --verbose, see why dependencies didn't upgrade
• Error if upgrades possible with --locked
• Allow multiple occurrences of --pkgid

rm

• Add --target flag
• Add --dry-run flag

v0.9.1

Compare Source

Fixes

set-version

• Don't overwrite updated dependencies with stale data when modifying multiple packages

v0.9.0

Compare Source

In large part, this release is a test-bed for changes proposed as part of the
path to merging cargo-add into cargo. See
internals
for more background on the changes.

Breaking Changes

• Many programmatic APIs changed
• Feature flag vendored-libgit2 is activated by default

cargo-add

• Removed --upgrade <policy>
• Removed --sort
• Removed --allow-prerelease
• Removed cargo add <git-url>, requiring cargo add --git <git-url>
• Removed --path <path> in favor of cargo add <path>
• Removed --vers <version-req> in favor of cargo add <name>@&#8203;<version-req>
• --git support is now feature gated as we work out how to expose it

Features

cargo-add

• Lists available features
• Warn when adding non-existent features
• git --tag and --rev support
• --default-features flag for when updating an existing entry
• --no-optional flag for when updating an existing entry
• Allow , to separate --features
• Added -F short flag for --features
• cargo add serde +derive feature activation
• --dry-run support

Fixes

General

• TOML 1.0 compliant parser
• Use stderr for user messages
• Improve detection for enabling colored output
• Handle empty cargo config source table

cargo-add

• Allow --registry with name@version and path dependencies
• Don't panic on --target= (ie empty target)
• Cleaned up "Adding" message
• Improve overwrite behavior (re-adding the same dependency)
• Allow using both --manifest-path and --package
• Remove invalid dependency activation
• When adding an existing dependency to another table, reuse the existing source information (e.g. version requirement)

cargo-rm

• Don't create empty feature tables
• Remove dep activation when no longer optional

cargo-upgrade

• Preserve version requirement precision (behind a feature flag)

cargo-set-version

• Allow --metadata to override version metadata
• Improve dependent detection

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.