search

denoland / deploy_feedback

For reporting issues with Deno Deploy
https://deno.com/deploy
74 stars 5 forks source link

List current runtime version #764

Open natepmay opened 1 week ago

natepmay commented 1 week ago

What problem are you trying to solve?

Hello. I'm running into this issue in the Deno runtime, which was merged last week and appears in Deno v. 2.1.0. It appears not to be reflected in Deno Deploy though, which is consistent with comments I've seen you posting that Deploy is still on the 1.x runtime. I'm wondering if there's any way to know when the runtime for Deploy will be ugraded to 2.1.0 or above? My project is blocked by this particular bug.

Describe the solution you'd like

It would be great if the dashboard told me what version the runtime is in. Also just hoping the upgrade to 2.1.0 will happen soon.

Describe alternatives you've considered

The error is within a package so I would have to fork that package to try to fix it. Rather than doing that I may just choose a different deployment other than Deno Deploy since this is a small project.

Documentation, Adoption, Migration Strategy

Maybe in the Overview part of the project dashboard, just list the runtime version.

magurotuna commented 1 week ago

Hi @natepmay, we are working on upgrading the runtime on Deno Deploy to v2.x and hoping to get it done within December. In order to know what the current version is, you can use navigator.userAgent that will return Deno/1.46.3 as of now. See also https://github.com/denoland/deploy_feedback/issues/705

natepmay commented 6 days ago

Great--thanks for the update.