Closed Unpublished closed 1 year ago
Thanks, TIL about cargo SemVer compatible updates. Let me repurpose this PR so you can benefit for dev of anstyle :)
Otherwise we can just close it
I'm not too worried about duplicate dependencies for anstyle developers (our build times are fairly quick) and I've been trying to keep our Cargo.lock
file to match the minimums for our version requirements so we make sure our version requirements are valid (e.g. we successfully test with a newer dependency but someone pulls one of the anstyle crates in and has an older version of that dependency in their tree, causing a breakage).
I think I'm going to go ahead and close this.
Could you expand on the motivation?
anstream
s version requirement shouldn't matter to callers but what gets put in their lock file. Is this trying to improve things foranstream
development? In that case, I'm seeing more entries in the lock file, not less.