Bump the version to 1.1.0-beta.1

[juanmaguitar]

Why

v1.0.1 shipped on 21 August. Trunk carries 45 commits since, and this is the beta for 1.1.0, published so contributors can test it before the stable tag. The headline is the bundled Git: the app ships its own Git binary and every checkout operation runs on it, so a contributor no longer needs Git installed (#401 to #411, #418, #420). It also ships the packaging allow-list (#450) and the fixes closed under the v1.1.0 milestone.

The version reaches two places a contributor sees, and both must carry the real build: electron-builder embeds it in the artifact names (wordpress-contributor-toolkit-1.1.0-beta.1-*), and src/logging.js writes app <version> as the log's first line, so a problem report names the build it came from. That is why the bump merges before the tag.

What changes

Only the version. All three package-version fields in package.json and package-lock.json move together from 1.0.1 to 1.1.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 or Windows for the artifact check that follows the merge.

In the repository root:

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

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

After merge, the release build must produce artifacts named wordpress-contributor-toolkit-1.1.0-beta.1-*, and the first line of a fresh app log must read app 1.1.0-beta.1.

Risks and limitations

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

Related

Same shape as #244 (v1.0.0-beta.1) and #397 (v1.0.1).

---

Review outcome (required — see AGENTS.md)

Version-only change, three lines. Verified locally on this branch: npm run lint clean, npm test 1316 pass, 0 fail; git diff --stat shows two files, three insertions, three deletions; both JSON files parse. Nothing to fix, nothing deferred.

Screenshots or recording

Nothing on screen changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_0123opUnXoxs1CAN7YQ7q8KU

[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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 9ca03a57-9dfa-4a0c-b924-bced3926ee97

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

---

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.}