Pavan K Sunkara
Pavan K Sunkara
Started adding upgrade scripts from v0.2. Unfortunately, we don't have the same for v1 releases.
We also had `.ansi_color()` in the old API. Whatever you did, I see everyone needing to do it. That means, we need to simplify the verbosity of it.
Even simplifying the `anstream::AutoStream::choice(&std::io::stderr())` to `stderr().choice()` to return `ColorChoice` is better, because we want the end-users of `anstream` to prefer using `stdout()` and `stderr()` directly in most common use cases...
> To even answer the question we currently are, we'd need to pass the choice down into the type I have seen you mention this more than once, but I...
> If we wanted to have the same behavior of AutoStream::choice, we'd need to take choice and store it inside AutoStream so we could return it. Yup, when I was...
I will try to make a PR then and see if anything pops up.
Some crates are skipped in publishing because they have no changes. Is it because of that? Can you also please paste the output of `cargo ws plan -al`?
@jkelleyrtp Any update on this?
I just wanted to let you know I'm closing this for now. I will open it if I get more information.
> Also in some of the workspaces I've checked, I still encountered issues with dependency resolution. Can you please describe them? > it doesn't seem to work with first-time-ever publishing...