Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pretty simple: this PR upgrades all the Rust dependencies. I ran
cargo upgrade --incompatible allow, followed bycargo update.It looks like
deno_coremoved from https://github.com/denoland/deno_core to https://github.com/denoland/deno since the last release, and in the process started pinning thedeno_errordependency to v0.7.1 exactly. Cargo wasn't happy with that since we were usingdeno_errorv0.7.3. I wasn't sure the best way to handle this, so I decided to just lower our version constraint to v0.7.1, but not pinned to an exact version. That way, ifdeno_coreupdates to a later v0.7.x release, we should be able to update without any issue.