Renovate: allow @wordpress/theme 2.x for wp-build's peer range

[retrofox]

Proposed changes

@wordpress/build 0.22.0 keeps its optional peer dependency on @wordpress/theme at >=0.8.0 <2.0.0, while the rest of the August 26 release train (@wordpress/ui 0.21, @wordpress/boot 0.21) requires @wordpress/theme ^2.0.0. With strictPeerDependencies: true.

The next bundled @wordpress/* Renovate round cannot install: every wp-build project (12 of them, all pinning build + theme) fails with ERR_PNPM_PEER_DEP_ISSUES, the bot's lockfile step dies, and the PR arrives with a stale lock, the same failure mode as the August 17 round.

This adds a peerDependencyRules.allowedVersions entry in pnpm-workspace.yaml for @wordpress/build>@wordpress/theme (>=0.8.0 <3.0.0).

The range is safe: wp-build only loads two optional plugins from theme (postcss-plugins/postcss-ds-token-fallbacks, esbuild-plugins/esbuild-ds-token-fallbacks) and theme 2.0.0 still exports both; its only breaking change is TypeScript declaration resolution (TypeScript 5+, we are on 6). Same shape as WordPress/gutenberg#80089, which widened the range for theme 1.x; the 2.x widening is being proposed upstream, and this rule can go once a wp-build release carries it.

Related product discussion/links

• Update Bundled @wordpress/* monorepo #51303 (previous bundled round) and the Renovate Dependency Dashboard Renovate Dependency Updates #23363, where the next round is waiting.
• wp-build: Allow @wordpress/theme 1.x peer versions WordPress/gutenberg#80089 (precedent for theme 1.x).

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• pnpm install --frozen-lockfile on this branch: the rule alone changes nothing in the lockfile.
• Simulate the round: in projects/packages/scan/package.json set @wordpress/theme to 2.0.0 and @wordpress/build to 0.22.0, then run pnpm install --lockfile-only.
  On trunk, it fails with ERR_PNPM_PEER_DEP_ISSUES: unmet peer @wordpress/theme; on this branch, it resolves. Revert the two files afterward.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the update/wp-build-allow-theme-2 branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/wp-build-allow-theme-2

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/wp-build-allow-theme-2

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[anomiex]

We normally do these sorts of overrides in .pnpmfile.cjs instead.

[retrofox]

Moved to .pnpmfile.cjs, next to the existing @wordpress/theme peer widening.

[simison]

Let's also fix things like these upstream:

• Build: allow wp-theme 2.x peer deps WordPress/gutenberg#82139

Seems like it was just an oversight and not intentionally restricted.

[retrofox]

Let's also fix things like these upstream:

Thanks for opening that in core. Linked it from the description.

[anomiex]

Seems reasonable to me. Thanks for filing upstream.