Collect release information for Bun

[alii]

Summary

Records Bun's release information. I under Bun/Oven will commit to maintaining this in the future and reasonably ensure data is accurate.

Test results and supporting details

n/a?

Related issues

Partially fixes #27599
Related to #23440

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[Elchi3]

So, the browsers/bun.json file in #23440 is smaller. I wonder if we really need to add every single bun release here or just those where the webkit version has been upgraded?

[caugner]

Overall, this looks good to me, but I have some concerns with running the downloaded executable.

[alii]

That's reasonable - we could provide this information on Bun's website as a simple GET route. This would also save CI time on your end, too.

[alii]

I've made https://bun.com/versions.json which would update within a day of a new Bun release.

The last thing to do is to switch the WebKit version from our commit SHAs to the semver-like version number in WebKit's source. Currently this is non-trivial to do as the values aren't easily accessible with just a Bun binary.

With that said, I will explore this now and find a solution. Most likely it will look like fetching the file from GitHub's api and just grepping for the values.

[alii]

So, the browsers/bun.json file in #23440 is smaller. I wonder if we really need to add every single bun release here or just those where the webkit version has been upgraded?

In general WebKit is upgraded in modern (~past 1.5yr) Bun releases. New features or compatibility changes are also often implemented in patches, so I would say it is relevant to be collecting every release number.

WebKit commits data vs Bun releases:

Versions with Shared WebKit Commits:

WebKit Commit	Count	Versions
oven-sh/WebKit@a780bdf	38	v1.0.12 through v1.0.36 (25 versions), v1.1.0 through v1.1.12 (13 versions)
oven-sh/WebKit@13bb88d	6	v1.1.22, v1.1.23, v1.1.24, v1.1.25, v1.1.26, v1.1.27
oven-sh/WebKit@9e3b60e	4	v1.1.44, v1.1.45, v1.2.0, v1.2.1
oven-sh/WebKit@ef31d98	3	v1.2.6, v1.2.7, v1.2.8
oven-sh/WebKit@3845bf3	3	v1.1.40, v1.1.41, v1.1.42
oven-sh/WebKit@353aa20	3	v1.1.13, v1.1.14, v1.1.15
oven-sh/WebKit@b49be54	2	v1.1.19, v1.1.20
oven-sh/WebKit@8f9ae4f	2	v1.1.37, v1.1.38
oven-sh/WebKit@64d04ec	2	v1.1.16, v1.1.17
oven-sh/WebKit@543cca2	2	v1.1.32, v1.1.33
oven-sh/WebKit@4a2db32	2	v1.1.28, v1.1.29
oven-sh/WebKit@3bc4abf	2	v1.1.35, v1.1.36
oven-sh/WebKit@0682071	2	v1.2.9, v1.2.10

Versions with Unique WebKit Commits:

Version	WebKit Commit
v1.1.18	oven-sh/WebKit@615e858
v1.1.21	oven-sh/WebKit@f9a0fda
v1.1.30	oven-sh/WebKit@0a0a383
v1.1.31	oven-sh/WebKit@12e2f46
v1.1.34	oven-sh/WebKit@9b84f43
v1.1.39	oven-sh/WebKit@58549dd
v1.1.43	oven-sh/WebKit@e1a802a
v1.2.2	oven-sh/WebKit@e32c635
v1.2.3	oven-sh/WebKit@763e836
v1.2.4	oven-sh/WebKit@c333de5
v1.2.5	oven-sh/WebKit@abe5e80
v1.2.11	oven-sh/WebKit@11b10bb
v1.2.12	oven-sh/WebKit@c244f56
v1.2.13	oven-sh/WebKit@017930e
v1.2.14	oven-sh/WebKit@eda8b0f
v1.2.15	oven-sh/WebKit@b98e20b
v1.2.16	oven-sh/WebKit@014cad8
v1.2.17	oven-sh/WebKit@397dafc
v1.2.18	oven-sh/WebKit@29bbdff
v1.2.19	oven-sh/WebKit@1098cc5
v1.2.20	oven-sh/WebKit@684d455

[alii]

I've updated the PR to use the GitHub API to fetch WebKit's Versioning file from Bun's fork. I wouldn't expect we'd ever run into rate limiting issues in the future with GitHub's api, since we're only ever updating at most once per release - which is not often anyway.