Bump version to 1.2.0-beta.1 - #505

Why

v1.1.0 shipped on 16 September. Sixteen commits since then reach trunk, and this beta is the first build that carries the Gutenberg contribution target (#251): a site can now be a checkout of WordPress/gutenberg, served through Playground as a plugin in a stock WordPress, with a GitHub issue as its work item, pull request checkout from that issue, and a pull request opened against WordPress/gutenberg from the app. The manual pass of that work ran on macOS and on Windows over 18 to 20 September and found six issues; the four that affected the first-run path are fixed on trunk (#489, #493, #496, #500, #504, and #491 for the hint), the rest are on the v1.2.0-beta.2 milestone.

electron-builder derives artifact names from package.json, so the version has to move before the tag and the artifacts exist. A beta is a pre-release, so releases/latest stays on v1.1.0.

What changes

Only the version. All three package-version fields in package.json and package-lock.json move together from 1.1.0 to 1.2.0-beta.1. No dependency versions change, and there is no application behaviour change in this PR.

How to test this

Platforms: any for the suite; macOS and Windows for the artifact checks that follow the merge.

1. npm run lint is clean and npm test passes.
2. node -e "console.log(require('./package.json').version)" prints 1.2.0-beta.1.
3. python3 -c "import json;d=json.load(open('package-lock.json'));print(d['version'], d['packages']['']['version'])" prints 1.2.0-beta.1 1.2.0-beta.1.

What must not have happened: no dependency version may change. git diff must show exactly three changed lines, all of them the root package version.

After merge, the release build must produce artifacts named wordpress-contributor-toolkit-1.2.0-beta.1-*; the asar root must be exactly node_modules, package.json, src, with npm 11 under node_modules/npm and no .codesigning directory; on macOS CFBundleShortVersionString reads 1.2.0-beta.1.

Risks and limitations

No UI change. The risk is a mis-scoped edit in package-lock.json, where dependencies also carry version fields; the replacement was confined to the first 2000 bytes of the file, which hold the two root entries and nothing else, and both files were re-parsed as JSON afterwards.

Verified locally on this branch: lint clean, npm test 1596 pass / 0 fail.

Related

Part of #251. Release notes follow on the pre-release; docs publish for the tag per #487.

🤖 Generated with Claude Code