Updates for Deno v1.38

[bartlomieju]

Summary

Changes for compat data for Deno v1.38

Test results and supporting details

The blog post with detailed changes will be available at https://deno.com/blog/v1.38

Related issues

Fixes #21151

[Elchi3]

@bartlomieju thanks for your PR! Do you know if there is data for Deno releases available programmatically? We are trying to automate updating this file and we have done so for other engines. (See #21137 for how a bot now takes care of updates). Would be cool to set this up for Deno, too!

[Elchi3]

LGTM! 👍

[bartlomieju]

Hey @Elchi3, sorry for a slow response. Currently we don't have a way to programatically get this data, besides checking type declarations available in the given version. We use that to generate documentation automatically, so I guess we could diff these declarations to see what's changed. Is there some README I could look at too see how the update script works?

[teoli2003]

Hi!

There is no README, but I can describe what is needed as I wrote the scripts for Chrome (Android/Desktop + Webview), Firefox (Android/Desktop), and Edge.

What we want to achieve

We want to automatically create a PR when a new tool is released (and, for the major browsers, when a new public Beta is released). The PR update automatically the browser versions files: firefox.json, firefox-android.json, webview.json, edge.json, deno.json, … The review of the PR and its merging is done by humans.

What information we need

For Deno, we need to be able to fill these fields:

• A version number that is the key.
• release_date: the release date of a given version
• release_notes: the structure is trivial and can be deduced from the version number: https://github.com/denoland/deno/releases/tag/v1.38.0
• engine. This is hardcoded to V8.
• engine_version.

Where the information should be

We need a way to query this information, either via an API, or by reading files on the web (on GitHub, it works well; I did it for some data relating to Edge).

• How do we detect a new version? The script can read it from https://raw.githubusercontent.com/denoland/deno/main/Releases.md
• How do we detect the release date? From https://raw.githubusercontent.com/denoland/deno/main/Releases.md
• Engine_version: <--- This is the part I don't know how. A GitHub file?

Doing the script

I can write the script (if I have the missing information), and have you review it.

Other info

The current scripts are living at https://github.com/mdn/browser-compat-data/tree/main/scripts/update-browser-releases (and are run automatically once a day)

[bartlomieju]

@teoli2003 I'm so sorry, but I missed your response. If you are still interested in writing the script I will definitely provide all the help and context needed. This would be great if we could automate the process.

Engine_version: <--- This is the part I don't know how. A GitHub file?

I can expose this information at a URL, similarly how we expose the latest version at https://dl.deno.land/canary-latest.txt