cargo/CHANGELOG.md

Changelog

Cargo 1.41 (2019-01-30)

5da4b4d4...HEAD

Added

Changed

Fixed

Cargo 1.40 (2019-12-19)

1c6ec66d...rust-1.40.0

Added

• (Nightly only): The mtime-on-use feature may now be enabled via the unstable.mtime_on_use config option. #7411
• Added http.ssl-version config option to control the version of TLS, along with min/max versions. #7308
• (Nightly only): Added support for named profiles. #6989
• 🔥 Compiler warnings are now cached on disk. If a build generates warnings, re-running the build will now re-display the warnings. #7450
• (Nightly only): Added -Zpanic-abort-tests to allow building and running tests with the "abort" panic strategy. #7460
• Added --filter-platform option to cargo metadata to narrow the nodes shown in the resolver graph to only packages included for the given target triple. #7376

Changed

• Cargo's "platform" cfg parsing has been extracted into a separate crate named cargo-platform. #7375
• (Nightly only): Changed build-std to use --sysroot. #7421
• (Nightly only): Various fixes and enhancements to -Ztimings. #7395 #7398 #7397 #7403 #7428 #7429
• Dependencies extracted into Cargo's cache no longer preserve mtimes to reduce syscall overhead. #7465
• Windows: EXE files no longer include a metadata hash in the filename. This helps with debuggers correlating the filename with the PDB file. #7400
• Wasm32: .wasm files are no longer treated as an "executable", allowing cargo test and cargo run to work properly with the generated .js file. #7476
• crates.io now supports SPDX 3.6 licenses. #7481
• Improved cyclic dependency error message. #7470
• Bare cargo clean no longer locks the package cache. #7502
• cargo publish now allows dev-dependencies without a version key to be published. A git or path-only dev-dependency will be removed from the package manifest before uploading. #7333
• (Nightly only): Profile overrides have renamed the syntax to be [profile.dev.package.NAME]. #7504
• --features and --no-default-features in the root of a virtual workspace will now generate an error instead of being ignored. #7507
• Generated files (like Cargo.toml and Cargo.lock) in a package archive now have their timestamp set to the current time instead of the epoch. #7523
• The -Z flag parser is now more strict, rejecting more invalid syntax. #7531

Fixed

• Fixed an issue where if a package had an include field, and Cargo.lock in .gitignore, and a binary or example target, and the Cargo.lock exists in the current project, it would fail to publish complaining the Cargo.lock was dirty. #7448
• Fixed a panic in a particular combination of [patch] entries. #7452
• Windows: Better error message when cargo test or rustc crashes in an abnormal way, such as a signal or seg fault. #7535
• (Nightly only): Fixed warnings for unused profile overrides in a workspace. #7536

Cargo 1.39 (2019-11-07)

e853aa97...1c6ec66d

Added

• Config files may now use the .toml filename extension. #7295
• (Nightly only): Basic support for building the standard library directly from Cargo has been added. (docs) #7216
• The --workspace flag has been added as an alias for --all to help avoid confusion about the meaning of "all". #7241
• The publish field has been added to cargo metadata. #7354
• (Nightly only): Added -Ztimings feature to generate an HTML report on the time spent on individual compilation steps. This also may output completion steps on the console and JSON data. (docs) #7311
• (Nightly only): Added ability to cross-compile doctests. (docs) #6892

Changed

• Display more information if parsing the output from rustc fails. #7236
• TOML errors now show the column number. #7248
• cargo vendor no longer deletes files in the vendor directory that starts with a .. #7242
• cargo fetch will now show manifest warnings. #7243
• cargo publish will now check git submodules if they contain any uncommitted changes. #7245
• In a build script, cargo:rustc-flags now allows -l and -L flags without spaces. #7257
• When cargo install replaces an older version of a package it will now delete any installed binaries that are no longer present in the newly installed version. #7246
• A git dependency may now also specify a version key when published. The git value will be stripped from the uploaded crate, matching the behavior of path dependencies. #7237
• The behavior of workspace default-members has changed. The default-members now only applies when running Cargo in the root of the workspace. Previously it would always apply regardless of which directory Cargo is running in. #7270
• libgit2 updated pulling in all upstream changes. #7275
• Bump home dependency for locating home directories. #7277
• zsh completions have been updated. #7296
• SSL connect errors are now retried. #7318
• The jobserver has been changed to acquire N tokens (instead of N-1), and then immediately acquires the extra token. This was changed to accommodate the cc crate on Windows to allow it to release its implicit token. #7344
• The scheduling algorithm for choosing which crate to build next has been changed. It now chooses the crate with the greatest number of transitive crates waiting on it. Previously it used a maximum topological depth. #7390
• RUSTFLAGS are no longer incorporated in the metadata and filename hash, reversing the change from 1.33 that added it. This means that any change to RUSTFLAGS will cause a recompile, and will not affect symbol munging. #7459

Fixed

• Git dependencies with submodules with shorthand SSH URLs (like git@github.com/user/repo.git) should now work. #7238
• Handle broken symlinks when creating .dSYM symlinks on macOS. #7268
• Fixed issues with multiple versions of the same crate in a [patch] table. #7303
• Fixed issue with custom target .json files where a substring of the name matches an unsupported crate type (like "bin"). #7363
• Fixed issues with generating documentation for proc-macro crate types. #7159
• Fixed hang if Cargo panics within a build thread. #7366
• Fixed rebuild detection if a build.rs script issues different rerun-if directives between builds. Cargo was erroneously causing a rebuild after the change. #7373
• Properly handle canonical URLs for [patch] table entries, preventing the patch from working after the first time it is used. #7368
• Fixed an issue where integration tests were waiting for the package binary to finish building before starting their own build. They now may build concurrently. #7394
• Fixed accidental change in the previous release on how --features a b flag is interpreted, restoring the original behavior where this is interpreted as --features a along with the argument b passed to the command. To pass multiple features, use quotes around the features to pass multiple features like --features "a b", or use commas, or use multiple --features flags. #7419

Cargo 1.38 (2019-09-26)

4c1fa54d...23ef9a4e

Added

• 🔥 Cargo build pipelining has been enabled by default to leverage more idle CPU parallelism during builds. #7143
• The --message-format option to Cargo can now be specified multiple times and accepts a comma-separated list of values. In addition to the previous values it also now accepts json-diagnostic-short and json-diagnostic-rendered-ansi which configures the output coming from rustc in json message mode. #7214
• Cirrus CI badges are now supported on crates.io. #7119
• (Nightly only): Added cargo fix --clippy which will apply machine-applicable fixes from Clippy. #7069
• A new format for Cargo.lock has been introduced. This new format is intended to avoid source-control merge conflicts more often, and to generally make it safer to merge changes. This new format is not enabled at this time, though Cargo will use it if it sees it. At some point in the future, it is intended that this will become the default. #7070
• Progress bar support added for FreeBSD. #7222
• (Nightly only): Added -Z binary-dep-depinfo flag to add change tracking for binary dependencies like the standard library. #7137 #7219

Changed

• The -q flag will no longer suppress the root error message for an error from Cargo itself. #7116
• The Cargo Book is now published with mdbook 0.3 providing a number of formatting fixes and improvements. #7140
• The --features command-line flag can now be specified multiple times. The list of features from all the flags are joined together. #7084
• (Nightly only): cargo clippy-preview will always run, even if no changes have been made. #7157
• Package include/exclude glob-vs-gitignore warnings have been removed. Packages may now use gitignore-style matching without producing any warnings. #7170
• Cargo now shows the command and output when parsing rustc output fails when querying rustc for information like cfg values. #7185
• cargo package/cargo publish now allows a symbolic link to a git submodule to include that submodule. #6817
• Improved the error message when a version requirement does not match any versions, but there are pre-release versions available. #7191

Fixed

• (Nightly only): Fixed exponential blowup when using CARGO_BUILD_PIPELINING. #7062
• Fixed using the wrong directory when updating git repositories when using the git-fetch-with-cli config option, and the GIT_DIR environment variable is set. This may happen when running cargo from git callbacks. #7082
• Fixed dep-info files being overwritten for targets that have separate debug outputs. For example, binaries on -apple- targets with .dSYM directories would overwrite the .d file. #7057
• Fix [patch] table not preserving "one major version per source" rule. #7118
• Ignore --remap-path-prefix flags for the metadata hash in the cargo rustc command. This was causing the remap settings to inadvertently affect symbol names. #7134
• Fixed cycle detection in [patch] dependencies. #7174
• Fixed cargo new leaving behind a symlink on Windows when core.symlinks git config is true. Also adds a number of fixes and updates from upstream libgit2. #7176
• macOS: Fixed setting the flag to mark the target directory to be excluded from backups. #7192
• Fixed cargo fix panicking under some situations involving multi-byte characters. #7221
• (Nightly only): Fixed passing args to clippy in cargo clippy-preview. #7162

Cargo 1.37 (2019-08-15)

c4fcfb72...9edd0891

Added

• Added doctest field to cargo metadata to determine if a target's documentation is tested. #6953 #6965
• (Nightly only): Added compiler message caching. The -Z cache-messages flag makes cargo cache the compiler output so that future runs can redisplay previous warnings. #6933
• 🔥 The cargo vendor command is now built-in to Cargo. This command may be used to create a local copy of the sources of all dependencies. #6869
• 🔥 The "publish lockfile" feature is now stable. This feature will automatically include the Cargo.lock file when a package is published if it contains a binary executable target. By default, Cargo will ignore Cargo.lock when installing a package. To force Cargo to use the Cargo.lock file included in the published package, use cargo install --locked. This may be useful to ensure that cargo install consistently reproduces the same result. It may also be useful when a semver-incompatible change is accidentally published to a dependency, providing a way to fall back to a version that is known to work. #7026
• 🔥 The default-run feature has been stabilized. This feature allows you to specify which binary executable to run by default with cargo run when a package includes multiple binaries. Set the default-run key in the [package] table in Cargo.toml to the name of the binary to use by default. #7056

Changed

• cargo package now verifies that build scripts do not create empty directories. #6973
• A warning is now issued if cargo doc generates duplicate outputs, which causes files to be randomly stomped on. This may happen for a variety of reasons (renamed dependencies, multiple versions of the same package, packages with renamed libraries, etc.). This is a known bug, which needs more work to handle correctly. #6998
• Enabling a dependency's feature with --features foo/bar will no longer compile the current crate with the foo feature if foo is not an optional dependency. #7010
• If --remap-path-prefix is passed via RUSTFLAGS, it will no longer affect the filename metadata hash. #6966
• libgit2 has been updated to 0.28.2, which Cargo uses to access git repositories. This brings in hundreds of changes and fixes since it was last updated in November. #7018
• Cargo now supports absolute paths in the dep-info files generated by rustc. This is laying the groundwork for tracking binaries, such as libstd, for rebuild detection. (Note: this contains a known bug.) #7030
• (Nightly only): -Z mtime-on-use no longer touches intermediate artifacts. #7050

Fixed

• Fixed how zsh completions fetch the list of commands. #6956
• "+ debuginfo" is no longer printed in the build summary when debug is set to 0. #6971
• Fixed cargo doc with an example configured with doc = true to document correctly. #7023
• Don't fail if a read-only lock cannot be acquired in CARGO_HOME. This helps when CARGO_HOME doesn't exist, but --locked is used which means CARGO_HOME is not needed. #7149
• Reverted a change in 1.35 which released jobserver tokens when Cargo blocked on a lock file. It caused a deadlock in some situations. #7204

Cargo 1.36 (2019-07-04)

6f3e9c36...c4fcfb72

Added

• (Nightly only): Added -Z install-upgrade feature to track details about installed crates and to update them if they are out-of-date. #6798
• (Nightly only): Added the public-dependency feature which allows tracking public versus private dependencies. #6772
• Added more detailed documentation on target auto-discovery. #6898
• (Nightly only): Added build pipelining via the build.pipelining config option (CARGO_BUILD_PIPELINING env var). #6883
• 🔥 Stabilize the --offline flag which allows using cargo without a network connection. #6934 #6871

Changed

• publish = ["crates-io"] may be added to the manifest to restrict publishing to crates.io only. #6838
• macOS: Only include the default paths if DYLD_FALLBACK_LIBRARY_PATH is not set. Also, remove /lib from the default set. #6856
• cargo publish will now exit early if the login token is not available. #6854
• HTTP/2 stream errors are now considered "spurious" and will cause a retry. #6861
• (Nightly only): The publish-lockfile feature has had some significant changes. The default is now true, the Cargo.lock will always be published for binary crates. The Cargo.lock is now regenerated during publishing. cargo install now ignores the Cargo.lock file by default, and requires --locked to use the lock file. Warnings have been added if yanked dependencies are detected. #6840
• Setting a feature on a dependency where that feature points to a required dependency is now an error. Previously it was a warning. #6860
• The registry.index config value now supports relative file: URLs. #6873
• macOS: The .dSYM directory is now symbolically linked next to example binaries without the metadata hash so that debuggers can find it. #6891
• The default Cargo.toml template for now projects now includes a comment providing a link to the documentation. #6881
• Some improvements to the wording of the crate download summary. #6916 #6920
• ✨ Changed RUST_LOG environment variable to CARGO_LOG so that user code that uses the log crate will not display cargo's debug output. #6918
• Cargo.toml is now always included when packaging, even if it is not listed in package.include. #6925
• Package include/exclude values now use gitignore patterns instead of glob patterns. #6924
• Provide a better error message when crates.io times out. Also improve error messages with other HTTP response codes. #6936

Performance

• Resolver performance improvements for some cases. #6853
• Optimized how cargo reads the index JSON files by caching the results. #6880 #6912 #6940
• Various performance improvements. #6867

Fixed

• More carefully track the on-disk fingerprint information for dependencies. This can help in some rare cases where the build is interrupted and restarted. #6832
• cargo run now correctly passes non-UTF8 arguments to the child process. #6849
• Fixed bash completion to run on bash 3.2, the stock version in macOS. #6905
• Various fixes and improvements to zsh completion. #6926 #6929
• Fix cargo update ignoring -p arguments if the Cargo.lock file was missing. #6904

Cargo 1.35 (2019-05-23)

6789d8a0...6f3e9c36

Added

• Added the rustc-cdylib-link-arg key for build scripts to specify linker arguments for cdylib crates. #6298
• (Nightly only): cargo clippy-preview is now a built-in cargo command. #6759

Changed

• When passing a test filter, such as cargo test foo, don't build examples (unless they set test = true). #6683
• Forward the --quiet flag from cargo test to the libtest harness so that tests are actually quiet. #6358
• The verification step in cargo package that checks if any files are modified is now stricter. It uses a hash of the contents instead of checking filesystem mtimes. It also checks all files in the package. #6740
• Jobserver tokens are now released whenever Cargo blocks on a file lock. #6748
• Issue a warning for a previous bug in the TOML parser that allowed multiple table headers with the same name. #6761
• Removed the CARGO_PKG_* environment variables from the metadata hash and added them to the fingerprint instead. This means that when these values change, stale artifacts are not left behind. Also added the "repository" value to the fingerprint. #6785
• cargo metadata no longer shows a null field for a dependency without a library in resolve.nodes.deps. The dependency is no longer shown. #6534
• cargo new will no longer include an email address in the authors field if it is set to the empty string. #6802
• cargo doc --open now works when documenting multiple packages. #6803
• cargo install --path P now loads the .cargo/config file from the directory P. #6805
• Using semver metadata in a version requirement (such as 1.0.0+1234) now issues a warning that it is ignored. #6806
• cargo install now rejects certain combinations of flags where some flags would have been ignored. #6801
• (Nightly only): The build-override profile setting now includes proc-macros and their dependencies. #6811
• Resolver performance improvements for some cases. #6776
• (Nightly only): Optional and target dependencies now work better with -Z offline. #6814

Fixed

• Fixed running separate commands (such as cargo build then cargo test) where the second command could use stale results from a build script. #6720
• Fixed cargo fix not working properly if a .gitignore file that matched the root package directory. #6767
• Fixed accidentally compiling a lib multiple times if panic=unwind was set in a profile. #6781
• Paths to JSON files in build.target config value are now canonicalized to fix building dependencies. #6778
• Fixed re-running a build script if its compilation was interrupted (such as if it is killed). #6782
• Fixed cargo new initializing a fossil repo. #6792
• Fixed supporting updating a git repo that has a force push when using the git-fetch-with-cli feature. git-fetch-with-cli also shows more error information now when it fails. #6800
• --example binaries built for the WASM target are fixed to no longer include a metadata hash in the filename, and are correctly emitted in the compiler-artifact JSON message. #6812

Cargo 1.34 (2019-04-11)

f099fe94...6789d8a0

Added

• 🔥 Stabilized support for alternate registries. #6654
• (Nightly only): Added -Z mtime-on-use flag to cause the mtime to be updated on the filesystem when a crate is used. This is intended to be able to track stale artifacts in the future for cleaning up unused files. #6477 #6573
• Added documentation on using builds.sr.ht Continuous Integration with Cargo. #6565
• Cargo.lock now includes a comment at the top that it is @generated. #6548
• Azure DevOps badges are now supported. #6264
• (Nightly only): Added experimental -Z dual-proc-macros to build proc macros for both the host and the target. #6547
• Added a warning if --exclude flag specifies an unknown package. #6679

Changed

• cargo test --doc --no-run doesn't do anything, so it now displays an error to that effect. #6628
• Various updates to bash completion: add missing options and commands, support libtest completions, use rustup for --target completion, fallback to filename completion, fix editing the command line. #6644
• Publishing a crate with a [patch] section no longer generates an error. The [patch] section is removed from the manifest before publishing. #6535
• build.incremental = true config value is now treated the same as CARGO_INCREMENTAL=1, previously it was ignored. #6688
• Errors from a registry are now always displayed regardless of the HTTP response code. #6771

Fixed

• Fixed bash completion for cargo run --example. #6578
• Fixed a race condition when using a local registry and running multiple cargo commands at the same time that build the same crate. #6591
• Fixed some flickering and excessive updates of the progress bar. #6615
• Fixed a hang when using a git credential helper that returns incorrect credentials. #6681
• Fixed resolving yanked crates with a local registry. #6750

Cargo 1.33 (2019-02-28)

8610973a...f099fe94

Added

• compiler-artifact JSON messages now include an "executable" key which includes the path to the executable that was built. #6363
• The man pages have been rewritten, and are now published with the web documentation. #6405
• (Nightly only): Allow using registry names in [patch] tables instead of just URLs. #6456
• cargo login now displays a confirmation after saving the token. #6466
• A warning is now emitted if a [patch] entry does not match any package. #6470
• cargo metadata now includes the links key for a package. #6480
• (Nightly only): cargo metadata added the registry key for dependencies. #6500
• "Very verbose" output with -vv now displays the environment variables that cargo sets when it runs a process. #6492
• --example, --bin, --bench, or --test without an argument now lists the available targets for those options. #6505
• Windows: If a process fails with an extended status exit code, a human-readable name for the code is now displayed. #6532
• Added --features, --no-default-features, and --all-features flags to the cargo package and cargo publish commands to use the given features when verifying the package. #6453

Changed

• If cargo fix fails to compile the fixed code, the rustc errors are now displayed on the console. #6419
• (Nightly only): Registry names are now restricted to the same style as package names (alphanumeric, - and _ characters). #6469
• (Nightly only): cargo login now displays the /me URL from the registry config. #6466
• Hide the --host flag from cargo login, it is unused. #6466
• (Nightly only): cargo login --registry=NAME now supports interactive input for the token. #6466
• (Nightly only): Registries may now elide the api key from config.json to indicate they do not support API access. #6466
• Build script fingerprints now include the rustc version. #6473
• macOS: Switched to setting DYLD_FALLBACK_LIBRARY_PATH instead of DYLD_LIBRARY_PATH. #6355
• RUSTFLAGS is now included in the metadata hash, meaning that changing the flags will not overwrite previously built files. #6503
• When updating the crate graph, unrelated yanked crates were erroneously removed. They are now kept at their original version if possible. This was causing unrelated packages to be downgraded during cargo update -p somecrate. #5702
• TOML files now support the 0.5 TOML syntax.

Fixed

• cargo fix will now ignore suggestions that modify multiple files. #6402
• cargo fix will now only fix one target at a time, to deal with targets which share the same source files. #6434
• (Nightly only): Fixed panic when using --message-format=json with metabuild. #6432
• Fixed bash completion showing the list of cargo commands. #6461
• cargo init will now avoid creating duplicate entries in .gitignore files. #6521
• (Nightly only): Fixed detection of publishing to crates.io when using alternate registries. #6525
• Builds now attempt to detect if a file is modified in the middle of a compilation, allowing you to build again and pick up the new changes. This is done by keeping track of when the compilation starts not when it finishes. Also, #5919 was reverted, meaning that cargo does not treat equal filesystem mtimes as requiring a rebuild. #6484

Cargo 1.32 (2019-01-17)

339d9f9c...8610973a

Added

• (Nightly only): Allow usernames in registry URLs. #6242
• Registries may now display warnings after a successful publish. #6303
• Added a glossary to the documentation. #6321
• Added the alias c for cargo check. #6218
• (Nightly only): Added "compile_mode" key to the build-plan JSON structure to be able to distinguish running a custom build script versus compiling the build script. #6331

Changed

• 🔥 HTTP/2 multiplexing is now enabled by default. The http.multiplexing config value may be used to disable it. #6271
• Use ANSI escape sequences to clear lines instead of spaces. #6233
• Disable git templates when checking out git dependencies, which can cause problems. #6252
• Include the --update-head-ok git flag when using the net.git-fetch-with-cli option. This can help prevent failures when fetching some repositories. #6250
• When extracting a crate during the verification step of cargo package, the filesystem mtimes are no longer set, which was failing on some rare filesystems. #6257
• crate-type = ["proc-macro"] is now treated the same as proc-macro = true in Cargo.toml. #6256
• An error is raised if dependencies, features, target, or badges is set in a virtual workspace. Warnings are displayed if replace or patch is used in a workspace member. #6276
• Improved performance of the resolver in some cases. #6283 #6366
• .rmeta files are no longer hard-linked into the base target directory (target/debug). #6292
• A warning is issued if multiple targets are built with the same output filenames. #6308
• When using cargo build (without --release) benchmarks are now built using the "test" profile instead of "bench". This makes it easier to debug benchmarks, and avoids confusing behavior. #6309
• User aliases may now override built-in aliases (b, r, t, and c). #6259
• Setting autobins=false now disables auto-discovery of inferred targets. #6329
• cargo verify-project will now fail on stable if the project uses unstable features. #6326
• Platform targets with an internal . within the name are now allowed. #6255
• cargo clean --release now only deletes the release directory. #6349

Fixed

• Avoid adding extra angle brackets in email address for cargo new. #6243
• The progress bar is disabled if the CI environment variable is set. #6281
• Avoid retaining all rustc output in memory. #6289
• If JSON parsing fails, and rustc exits nonzero, don't lose the parse failure message. #6290
• (Nightly only): --out-dir no longer copies over build scripts. #6300
• Fixed renaming a project directory with build scripts. #6328
• Fixed cargo run --example NAME to work correctly if the example sets crate_type = ["bin"]. #6330
• Fixed issue with cargo package git discovery being too aggressive. The --allow-dirty now completely disables the git repo checks. #6280
• Fixed build change tracking for [patch] deps which resulted in cargo build rebuilding when it shouldn't. #6493

Cargo 1.31 (2018-12-06)

36d96825...339d9f9c

Added

• 🔥 Stabilized support for the 2018 edition. #5984 #5989
• 🔥 Added the ability to rename dependencies in Cargo.toml. #6319
• 🔥 Added support for HTTP/2 pipelining and multiplexing. Set the http.multiplexing config value to enable. #6005
• (Nightly only): Added --registry flag to cargo install. #6128
• (Nightly only): Added registry.default configuration value to specify the default registry to use if --registry flag is not passed. #6135
• (Nightly only): Added --registry flag to cargo new and cargo init. #6135
• Added http.debug configuration value to debug HTTP connections. Use CARGO_HTTP_DEBUG=true RUST_LOG=cargo::ops::registry cargo build to display the debug information. #6166
• CARGO_PKG_REPOSITORY environment variable is set with the repository value from Cargo.toml when building . #6096

Changed

• cargo test --doc now rejects other flags instead of ignoring them. #6037
• cargo install ignores ~/.cargo/config. #6026
• cargo version --verbose is now the same as cargo -vV. #6076
• Comments at the top of Cargo.lock are now preserved. #6181
• When building in "very verbose" mode (cargo build -vv), build script output is prefixed with the package name and version, such as [foo 0.0.1]. #6164
• If cargo fix --broken-code fails to compile after fixes have been applied, the files are no longer reverted and are left in their broken state. #6316

Fixed

• Windows: Pass Ctrl-C to the process with cargo run. #6004
• macOS: Fix bash completion. #6038
• Support arbitrary toolchain names when completing +toolchain in bash completion. #6038
• Fixed edge cases in the resolver, when backtracking on failed dependencies. #5988
• Fixed cargo test --all-targets running lib tests three times. #6039
• Fixed publishing renamed dependencies to crates.io. #5993
• Fixed cargo install on a git repo with multiple binaries. #6060
• Fixed deeply nested JSON emitted by rustc being lost. #6081
• Windows: Fix locking msys terminals to 60 characters. #6122
• Fixed renamed dependencies with dashes. #6140
• Fixed linking against the wrong dylib when the dylib existed in both target/debug and target/debug/deps. #6167
• Fixed some unnecessary recompiles when panic=abort is used. #6170

Cargo 1.30 (2018-10-25)

524a578d...36d96825

Added

• 🔥 Added an animated progress bar shows progress during building. #5995
• Added resolve.nodes.deps key to cargo metadata, which includes more information about resolved dependencies, and properly handles renamed dependencies. #5871
• When creating a package, provide more detail with -v when failing to discover if files are dirty in a git repository. Also fix a problem with discovery on Windows. #5858
• Filters like --bin, --test, --example, --bench, or --lib can be used in a workspace without selecting a specific package. #5873
• cargo run can be used in a workspace without selecting a specific package. #5877
• cargo doc --message-format=json now outputs JSON messages from rustdoc. #5878
• Added --message-format=short to show one-line messages. #5879
• Added .cargo_vcs_info.json file to .crate packages that captures the current git hash. #5886
• Added net.git-fetch-with-cli configuration option to use the git executable to fetch repositories instead of using the built-in libgit2 library. #5914
• Added required-features to cargo metadata. #5902
• cargo uninstall within a package will now uninstall that package. #5927
• (Nightly only): Added metabuild. #5628
• Added --allow-staged flag to cargo fix to allow it to run if files are staged in git. #5943
• Added net.low-speed-limit config value, and also honor net.timeout for http operations. #5957
• Added --edition flag to cargo new. #5984
• Temporarily stabilized 2018 edition support for the duration of the beta. #5984 #5989
• Added support for target.'cfg(…)'.runner config value to specify the run/test/bench runner for config-expressioned targets. #5959

Changed

• Windows: cargo run will not kill child processes when the main process exits. #5887
• Switched to the opener crate to open a web browser with cargo doc --open. This should more reliably select the system-preferred browser on all platforms. #5888
• Equal file mtimes now cause a target to be rebuilt. Previously only if files were strictly newer than the last build would it cause a rebuild. #5919
• Ignore build.target config value when running cargo install. #5874
• Ignore RUSTC_WRAPPER for cargo fix. #5983
• Ignore empty RUSTC_WRAPPER. #5985

Fixed

• Fixed error when creating a package with an edition field in Cargo.toml. #5908
• More consistently use relative paths for path dependencies in a workspace. #5935
• cargo fix now always runs, even if it was run previously. #5944
• Windows: Attempt to more reliably detect terminal width. msys-based terminals are forced to 60 characters wide. #6010
• Allow multiple target flags with cargo doc --document-private-items. 6022