-
Notifications
You must be signed in to change notification settings - Fork 10
Bump dependencies #1586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump dependencies #1586
Conversation
Phylum OSS Supply Chain Risk Analysis - FAILEDThis repository analyzes the risk of new dependencies. An If you see this comment, one or more dependencies have failed Phylum's risk analysis. Package:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some updates related to deno_node and winapi are causing failures in CI...looks like it is unrelated to first-party cli code updates. We might need to update to a newer version of deno_runtime to fix this...but I don't really know how best to do that. The last time deno was updated...in #1505...it required a lot of additional changes. @cd-work might know...
maxrake
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I clicked the wrong button the first time.
Phylum OSS Supply Chain Risk Analysis - INCOMPLETEThe analysis contains 3 package(s) Phylum has not yet processed, |
9552096 to
18d71b5
Compare
Phylum OSS Supply Chain Risk Analysis - INCOMPLETEThe analysis contains 2 package(s) Phylum has not yet processed, |
cd-work
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @maxrake.
Had to downgrade resolve-conf to remove its windows dependency.
Phylum OSS Supply Chain Risk Analysis - INCOMPLETEThe analysis contains 1 package(s) Phylum has not yet processed, |
maxrake
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is still one unprocessed dependency...but otherwise, LGTM.
This change seeks to replicate the one made in #1586, where `resolve-conf` was downgraded to remove its `windows` dependency. This is the command that was used to do so: ```sh cargo update --package resolv-conf --precise 0.7.0 ```
This change seeks to replicate the one made in #1586, where `resolve-conf` was downgraded to remove its `windows` dependency. This is the command that was used to do so: ```sh cargo update --package resolv-conf --precise 0.7.0 ```
* Bump dependencies * Downgrade `resolv-conf` This change seeks to replicate the one made in #1586, where `resolve-conf` was downgraded to remove its `windows` dependency. This is the command that was used to do so: ```sh cargo update --package resolv-conf --precise 0.7.0 ``` --------- Co-authored-by: Charles Coggins <maxrake@users.noreply.github.com>
Bump dependencies for all SemVer-compatible updates.