This repository has been archived by the owner on Sep 14, 2023. It is now read-only.
chore: fix deno workflow errors #944
Merged
Conversation
This file contains 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
ryanleecode
force-pushed
the
chore/update-deno-1.33
branch
from
44cbacc
to
6b160c3
Compare
ryanleecode
changed the title
ryanleecode
force-pushed
the
chore/update-deno-1.33
branch
from
6b160c3
to
e46f238
Compare
kratico
reviewed
Apr 28, 2023
kratico
reviewed
Apr 28, 2023
kratico
reviewed
Apr 28, 2023
kratico
reviewed
Apr 28, 2023
tjjfvi
approved these changes
Apr 28, 2023
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pins the deno version to
1.32.5because 1.33 has introduced many breaking changing and we are unable to pinpoint whether workkflow errors are because of capi or because of a bug in the latest upgrade.Added an issue to keep track of when we need to upgrade: #945