[juanmaguitar]

Why

This is the stable 1.1.0. v1.1.0-beta.1 shipped on 12 September and v1.1.0-beta.2 on 14 September; between them they were downloaded 33 times across macOS, Windows and Linux, and no issue was filed against either. The v1.1.0 milestone is closed, 21 of 21.

Shipping sooner rather than later is itself part of the reasoning: a site created by 1.0 cannot be written to by 1.1, so every day 1.0.1 remains the stable release is another day of sites being created that the next version can only read.

Four commits reach this tag that no beta carried: the Linux target list narrowed to the one artifact that is actually published and probed (#467), the apply panel moved above the site's other tickets (#472), the applied-patch record now travelling with carried work (#473), and the sidebar heading renamed (#482). Three of the four are visible on screen, so the artifact gets a manual pass before the release is published rather than the packaging check alone.

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-*), 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.1.0-beta.2 to 1.1.0. 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.
3. python3 -c "import json;d=json.load(open('package-lock.json'));print(d['version'], d['packages']['']['version'])" prints 1.1.0 1.1.0.

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-*, and the first line of a fresh app log must read app 1.1.0.

Risks and limitations

No UI change. The risk is a mis-scoped edit in package-lock.json, where dependencies also carry version strings; 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.

Unlike the betas, this tag becomes releases/latest, so it is what the README badge and every "download the toolkit" link resolve to.

Related

Same shape as #397 (v1.0.1), #457 (v1.1.0-beta.1) and #466 (v1.1.0-beta.2). The Gutenberg stack for v1.2.0 is held as a draft at #468 until this tag is pushed, so it cannot reach trunk and ship inside a release it has never been tested in; #479 waits for the same reason.

---

Review outcome (required — see AGENTS.md)

Version-only change, three lines. Verified locally on this branch: npm run lint clean, npm test 1454 pass, 0 fail, 2 expected skips; 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_0121dia1RzfskutrzA8iSK1K

[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: 34758324-5a93-4fe6-a016-340e1516fbe2

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