Closed t8 closed 3 years ago
@zhmushan I think there is a possibility:
When deno releases a new version, ry will do a PR
After merging the PR, wait for CI to complete and then publish to Github Release.
In this short period of time, a new version has been added to Release.md
, but in fact, it has not been released in Github Release, so it may cause 404.
We may need a fallback mechanism, if the latest version does not exist, install the previous version
We can:
queryLatestMatch()
That makes a lot of sense. Thanks for such a quick response! Looking forward to the solution.
This is happening again, both on @master and @v2
This is happening again, both on @master and @v2
In this short period of time, a new version has been added to Release.md, but in fact, it has not been released in Github Release, so it may cause 404.
as I say before. Deno v1.5.0 just release a minute before.
Just wait for a moment. it will works when Deno v1.5.0 released on Github
close this since #74 has been merged
We're finding this issue sporadically on one of our cron workflows. It doesn't happen often, but when it does, the CI fails. Here is a link to the specific error:
https://github.com/nestdotland/std/runs/933459310?check_suite_focus=true
Any ideas as to what the underlying issue may be?
Thanks in advance!
Tate