chore: widen windows-sys dependency version range #69
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Ya, that's probably a good move. Thanks! |
Author
|
Thanks for the quick review and merge @fdncred! What's this repo's policy on releases? I was hoping this goes out so I could try to get it into tracing-subscriber before their next release |
|
We usually like to run changes in nushell nightly and dogfood for a little bit before publishing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#66 updated the
windows-sysdependency to0.60.0to allow for ARM64EC support, but ARM64EC support was originally introduced in0.59.0. Since bothwindows-sysandnu-ansi-termare both widely used, it's good to have a larger dependency range to avoid duplicate dependencies in user's buildgraphs (and triggeringclippy::multiple-crate-versions). There's precedent for doing this in many crates: