Changelog History
Page 1
-
v0.11.6 Changes
November 14, 2022🛠 Fixes
⬆️
upgrade
- Ensure precise version setting runs
- ✂ Remove error blocking precise version setting
-
v0.11.5
October 09, 2022 -
v0.11.4 Changes
October 06, 2022🔋 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
- 📦 Modify
-
v0.11.3 Changes
September 28, 2022🛠 Fixes
- 💅 Polished help output
-
v0.11.2 Changes
September 22, 2022🔋 Features
⬆️
upgrade
- ⬆️ Upgrade
workspace.dependencies
(new in Rust 1.64)
- ⬆️ Upgrade
-
v0.11.1 Changes
September 16, 2022🛠 Fixes
⬆️
upgrade
- 🔄 Changed
--compatible
,--incompatible
, and--pinned
from acceptingtrue|false
toallow|ignore
(with aliases for compatibility- While we are still working out how we want to express these options, this at least removes the confusion over
--compatible false
looking like it is the same as--incompatible
.
- While we are still working out how we want to express these options, this at least removes the confusion over
- 🔄 Changed
-
v0.11.0 Changes
September 14, 2022🚀 This release is another step in our effort to find the appropriate
cargo ⬆️ upgrade
workflow for merging intocargo
.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 deprecatecargo update
and replace it withcargo ⬆️ 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 deprecatingcargo ⚡️ update
.🚀 More concretely, the approach taken in this release is a
cargo update
-like 🔒 command that implicitly modifiesCargo.lock
.To this end
- ⬆️
cargo upgrade
now works on the whole workspace exclusively- This also resolves confusion over
--package
,--exclude
, and the positionalPKGID
argument - This also removes any UI barriers for supporting workspace inheritance coming in 1.64
- This also resolves confusion over
- ⚡️
cargo upgrade -p [email protected]
will act as ifcargo 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
- Pass
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
andcargo 🔒 upgrade
and commit theirCargo.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 Changes
July 29, 2022🛠 Fixes
⬆️
upgrade
- Hide "note" column when unused
- 0️⃣ Summarize uninteresting rows by default
-
v0.10.3 Changes
July 27, 2022🛠 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 withcargo add
rm
- ⚡️ Update
--help
to be consistent withcargo add
- ⬆️ Provide table view of upgrades, like
-
v0.10.2 Changes
July 21, 2022🛠 Fixes
⬆️
upgrade
- Only fail on bad lockfile if
--to-lockfile
is set
rm
- Don't duplicate error messages
- Only fail on bad lockfile if