Update @wordpress/build to 0.16.1

[retrofox]

Fixes #

Proposed changes

• Update @wordpress/build from 0.14.0 to 0.16.1 across all 11 package consumers.
• Regenerate pnpm-lock.yaml with corepack pnpm@11.5.2 install.
• Add changelog entries for all affected packages.

Related product discussion/links

• N/A

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

No.

Testing instructions

• Run corepack pnpm@11.5.2 install and confirm the lockfile is up to date.
• Run corepack pnpm@11.5.2 jetpack build packages/premium-analytics.
• Confirm widget metadata is forwarded to the generated registry:
  grep -n "presentation" projects/packages/premium-analytics/build/widgets/registry.php
• Confirm the output includes 'presentation' => 'full-bleed' for jpa/hello-world.
• Sanity check other consumers:
  • corepack pnpm@11.5.2 jetpack build packages/forms
  • corepack pnpm@11.5.2 --dir projects/packages/forms run typecheck
  • corepack pnpm@11.5.2 jetpack build packages/videopress
  • corepack pnpm@11.5.2 --dir projects/packages/videopress run typecheck
  • corepack pnpm@11.5.2 jetpack build packages/publicize
  • corepack pnpm@11.5.2 --dir projects/packages/publicize run typecheck

Made with Cursor

[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-0-16-1 branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update-wp-build-0-16-1

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update-wp-build-0-16-1

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

[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

[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!

[Nikschavan]

Thank you for this, looks good!

[Nikschavan]

FYI, I also noticed there is a PR - #49271

[retrofox]

Thanks, @Nikschavan. Closing in favor of #49271