This has bothered me about `cargo new` and `cargo init` for a while that
the output is read backwards, for example:
```diff
--- i/tests/testsuite/cargo_init/path_contains_separator/stderr.log
+++ w/tests/testsuite/cargo_init/path_contains_separator/stderr.log
@@ -1,3 +1,3 @@
+ Creating binary (application) package
warning: the path `[ROOT]/case/test:ing/.` contains invalid PATH characters (usually `:`, `;`, or `"`)
It is recommended to use a different name to avoid problems.
- Created binary (application) package
```
refactor(shell): Use new fancy anstyle API
### What does this PR try to resolve?
Simplifies working with colored output
### How should we test and review this PR?
### Additional information
CC `@joshtriplett`
refactor: remove unnecessary Option in `Freshness::Dirty`
### What does this PR try to resolve?
This avoids reading and parsing JSON fingerprint files if the detailed
rebuild reason is not requested.
This also encodes `Freshness::Dirty(None)` better with a new variant `DirtyReason::FreshBuild`.
doc: Replace version with `latest` for jobserver link
### What does this PR try to resolve?
I prefer the link with `latest`, it will always jump to the latest version link for crate.
There is a bot called renovate to update the version for crate, So it's ok to use `latest` link.
### How should we test and review this PR?
### Additional information
docs(ref): Try to improve reg auth docs
### What does this PR try to resolve?
My end-goal *was* to discourage the use of `cargo:token` but it immediately failed for me and I need to look into that further.
So this is the smaller steps I made along the way.
### How should we test and review this PR?
### Additional information
For config.md, my expectation is to warn users about `cargo:token` right after the discussion on keeping tokens secret.
I want to find a way to talk about this on the "your first publish" page but that needs to wait until we smooth things out.
fix(config): Deprecate non-extension files
### What does this PR try to resolve?
In #7295 (released in 1.39), we said we'd want to warn on use of
`.cargo/config` after about 6 months. Over 4 years later, we are now
getting that warning.
This is important for addressing user confusion, like in
https://www.reddit.com/r/rust/comments/19fd5q2/cargoconfig/
### How should we test and review this PR?
It'll be important to look at the individual commits as one updates tests from using `.cargo/config` to `.cargo/config.toml` which touches a lot of code.
I added a test for `.cargo/config` in a separate commit so you can see how the output changes.
### Additional information
Discussed on [zulip](https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/Deprecating.20credential.20provider.20default.3F)
I thought the recommendation was doing the opposite of what I expected
until I dug further.
While this is covered in the config docs, we should explicitly call it
out.
In #7295 (released in 1.39), we said we'd want to warn on use of
`.cargo/config` after about 6 months. Over 4 years later, we are now
getting that warning.
This is important for addressing user confusion, like in
https://www.reddit.com/r/rust/comments/19fd5q2/cargoconfig/
fix(cli): Improve errors related to cargo script
### What does this PR try to resolve?
Fixes#13332
### How should we test and review this PR?
See tests in last commit to see how this changes error messages.
This is a lot of duplication with minor tweaking that will go away on stabilization
### Additional information
External subcommands are already able to inherit the jobserver from
env since #10511. However, users reported that they've expected
`cargo run` to behave the same as external subcommands.
A popular example "cargo-xtask" pattern is used as scripting to run
arbitrary tasks. Users may want to invoke `cargo run` from Make and
expect some parallelism. This PR provides such an ability to the
general `target.<...>.runner`, which affects `cargo test`,
`cargo bench`, and `cargo run`.
Note that this PR doesn't create any jobserver client if there is no
existing jobserver from the environment. Nor `-j`/`--jobs` would create
a new client. Reasons for this decision:
* There might be crates don't want the jobserver to pollute their
file descriptors, although they might be rare
* Creating a jobsever driver with the new FIFO named pipe style is not
yet supported as of `jobserver@0.1.26`. Once we can create a named
pipe-based jobserver, it will be less risky and inheritance by
default can be implemented.
