Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Deno 2.0/2.1 releases #25750

Merged
merged 1 commit into from
Jan 23, 2025
Merged

Add Deno 2.0/2.1 releases #25750

merged 1 commit into from
Jan 23, 2025

Conversation

philhawksworth
Copy link
Contributor

Summary

Updates the releases data for Deno to include the missing releases of v2.0, and v2.1

Information validated against the Deno release notes available:

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@github-actions github-actions bot added data:browsers Data about browsers (versions, release dates, etc). This data is used for validation. size:s [PR only] 7-24 LoC changed labels Jan 23, 2025
@caugner
Copy link
Contributor

caugner commented Jan 23, 2025

Thank you!

Note that we automatically update releases for Chrome/Edge/Firefox/Safari, see: https://github.com/mdn/browser-compat-data/tree/main/scripts/update-browser-releases

So if there is a reliable API or similar to automatically update the Deno releases, that would be awesome!

@caugner caugner changed the title Update deno releases data Add Deno 2.0/2.1 releases Jan 23, 2025
@caugner caugner merged commit bbd77df into mdn:main Jan 23, 2025
8 checks passed
@mdn-bot mdn-bot mentioned this pull request Jan 23, 2025
@caugner
Copy link
Contributor

caugner commented Jan 23, 2025

@philhawksworth Is there a way to programmatically determine the V8 version of a Deno version, other than checking the GitHub release for a mention of "upgrade V8 to x.y" and using the V8 version of the previous release if not?

@philhawksworth
Copy link
Contributor Author

Not currently, @caugner.

We could consider exposing all the information required to scrape/subscribe to in a similar way to the browser engines in your examples as you mentioned here. Currently the major and minor releases that would surface here are not terribly frequent, so we'll weigh up when the right time is to automate this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:browsers Data about browsers (versions, release dates, etc). This data is used for validation. size:s [PR only] 7-24 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants