#52730: build: add release-assets.json expected-asset manifest
Description
Adds script/release/release-assets.json — a structured manifest of the expected release asset names — extracted verbatim from assetsForVersion()'s patterns array in script/release/release.ts (using the exact same extraction Sudowoodo's task-runner/assets.ts regex performs today, so the content is behavior-identical by construction). ${version} placeholders are kept literal; the consumer substitutes them.
Why
Sudowoodo currently fetches release.ts at the release ref and regex-parses the TypeScript source to learn the expected asset list. Moving the list to JSON:
- removes that fragile source-parsing coupling, and
- unblocks deleting the now-dead release orchestration scripts from this repo (follow-up to #52100 — everything except the CI-invoked uploader subtree).
Sibling PRs add the manifest to each supported release branch (the lists differ: 43 and below still include the 32-bit win32-ia32/linux-armv7l assets). A Sudowoodo PR switches the reader to this file; the in-tree scripts get cleaned up after that deploys.
Checklist
- semver/none, no user-facing change
🤖 Generated with Claude Code
Notes: none
Backports
No Backports Requested
This pull request doesn't have any backports requested or created for older release branches.
What are backports?
Backports are copies of changes made to the main branch that are applied to older release branches. They ensure that bug fixes and important changes are available in maintained older versions of Electron.
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron