tdharris
commented
1 month ago I very much agree, I too was affected by outages caused by what is summarized above and here: https://github.com/denoland/deploy_feedback/issues/724. I initially was hoping to pin the Deno version until this was sorted out, but couldn't find that capability. This is definitely needed. Running on latest for runtime might be convenient and appealing, but there always comes a time where breaking changes are introduced in a patch version release - I duplicated this starting with deno 1.45.3. I had to fork, fix and deploy and then undo that same fix a day later once the original breaking change was reverted, perhaps after internal deno deploy monitoring showed many outages. This capability would be very much appreciated as something similar will undoubtedly happen again.
What problem are you trying to solve?
It seems that Deno 1.46 introduced some changes to how
file://URLs are handled, which has caused some projects using deno_blog on slightly older versions to not run on Deno Deploy unless the dependencies are updated in accordance with the latest version.Describe the solution you'd like
My suggestions are as follows:
Ability to choose the Deno version in the deploy dashboard: It would be helpful to have the option to select from previous X versions of Deno. If any of my projects are using a version that will no longer be available in the near future, I would appreciate an email notifying me to upgrade.
It could also be a field in
deno.jsoncthat deploy can read automatically, instead of having to configure this via the UI for each project.Describe alternatives you've considered
Searched the documentation to see if it was already available or not.
Documentation, Adoption, Migration Strategy
No response