[ryanwelcher]

Why

41 commits have reached trunk since v1.2.1, and milestone v2.0.0-beta.1 has 77 closed issues and none open. The main changes are the redesign on the WordPress Design System (#591), a settings dialog with language, theme, PHP version and debug flags (#638 to #651), and translation of the whole interface (#634 to #664). This is a beta: it ships with --prerelease, so releases/latest stays on v1.2.1.

electron-builder names the artifacts after package.json, so the version has to move before the tag and artifacts exist.

What changes

• The version. The three root version fields in package.json and package-lock.json move from 1.2.1 to 2.0.0-beta.1. No dependency versions change.
• The first shipped translations. npm run i18n:download added a catalog for each of the seven locales at 80% or more on translate.wordpress.org. None was removed, and no right-to-left locale was held back.

Locale	Translated	Strings
cs	94%	1001
en-ca	100%	1062
en-gb	100%	1062
gl	100%	1062
hu	100%	1062
nl	100%	1062
pl	96%	1028

How to test this

Platforms: any for steps 1 to 3. The artifact checks need macOS for Info.plist and Windows for the .exe.

Starting state: this branch checked out with node_modules installed. Run every command from the repository root.

1. npm run lint is clean and npm test passes.
2. node -e "console.log(require('./package.json').version)" prints 2.0.0-beta.1.
3. python3 -c "import json;d=json.load(open('package-lock.json'));print(d['version'], d['packages']['']['version'])" prints 2.0.0-beta.1 2.0.0-beta.1.
4. On the Buildkite build for the current head, the artifacts are named wordpress-contributor-toolkit-2.0.0-beta.1-*. The app.asar root holds exactly node_modules, package.json and src, with npm 11 under node_modules/npm and no .codesigning. On macOS, CFBundleShortVersionString reads 2.0.0-beta.1.
5. In the installed app, set the language to Dutch in the settings and relaunch. The interface is in Dutch.

What must not have happened: no dependency version may change. git diff trunk -- . ':!src/languages' shows exactly three changed lines, all of them the root version.

Risks and limitations

npm test run from an interactive terminal fails two integration tests on macOS. That is a test bug, fixed separately in #680. It does not affect CI or the app.

Related

Milestone v2.0.0-beta.1. Release notes follow on the release.

---

Review outcome (required — see AGENTS.md)

0 [fix here] · 0 [follow-up]. Automatic checks only, as in #533: this change has no logic to review.

• Review: completed, deterministic layer, in session; head 9853082 / base 5d5f701 (trunk). npm run lint passes, npm test passes (2098 tests, 0 failures, 2 skipped), both files are valid JSON, and the diff outside src/languages/ is the three root version fields. Outcome: nothing to fix.
• Since review: none.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: WordPress/contributor-toolkit/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: a38aecfa-6825-48b8-9f3e-6ba000a15727

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}