Skip to content

Update wc-calypso-bridge to 2.11.5#47487

Merged
dlind1 merged 2 commits intotrunkfrom
update/wpcomsh-to-use-wc-calypso-bridge-2.11.5
Mar 9, 2026
Merged

Update wc-calypso-bridge to 2.11.5#47487
dlind1 merged 2 commits intotrunkfrom
update/wpcomsh-to-use-wc-calypso-bridge-2.11.5

Conversation

@dlind1
Copy link
Copy Markdown
Contributor

@dlind1 dlind1 commented Mar 6, 2026

Fixes TRA-33

Relates to Automattic/wc-calypso-bridge#1598

Proposed changes:

Before:
Screenshot 2026-03-06 at 16 11 24

After:
Screenshot 2026-03-06 at 16 11 36

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

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

Testing instructions:

  • Apply this PR using the Jetpack Beta plugin.
  • Install the WooCommerce plugin.
  • Switch the user locale to a popular non-English one (Spanish, Turkish etc.)
  • Make sure that the translation files are installed, navigate to /wp-admin/admin.php?page=wc-admin and confirm that strings like "Add your products..." are translated.

Changelog

  • Generate changelog entries for this PR (using AI).

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 6, 2026

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 (WordPress.com Site Helper), and enable the update/wpcomsh-to-use-wc-calypso-bridge-2.11.5 branch.

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
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 6, 2026

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!


Wpcomsh plugin:

  • Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2)

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

@github-actions github-actions bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Mar 6, 2026
@jp-launch-control
Copy link
Copy Markdown

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

@dlind1 dlind1 marked this pull request as ready for review March 6, 2026 14:57
Copilot AI review requested due to automatic review settings March 6, 2026 14:57
@dlind1 dlind1 requested a review from m1r0 March 6, 2026 14:59
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the wpcomsh plugin’s Composer dependency on automattic/wc-calypso-bridge to pick up upstream fixes included in 2.11.5 (per the linked wc-calypso-bridge PRs and TRA-33).

Changes:

  • Bump automattic/wc-calypso-bridge from 2.11.4 to 2.11.5 in composer.json.
  • Update composer.lock to the corresponding v2.11.5 reference.
  • Add a wpcomsh changelogger entry documenting the bump.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File Description
projects/plugins/wpcomsh/composer.json Updates the required wc-calypso-bridge version to 2.11.5.
projects/plugins/wpcomsh/composer.lock Locks wc-calypso-bridge to v2.11.5 (updated reference/dist URL/content hash).
projects/plugins/wpcomsh/changelog/update-wpcomsh-to-use-wc-calypso-bridge-2.11.5 Adds changelogger entry for the dependency update.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Copy Markdown
Member

@m1r0 m1r0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and all looks good! 🚀

Image

@dlind1 dlind1 merged commit b99ebee into trunk Mar 9, 2026
75 checks passed
@dlind1 dlind1 deleted the update/wpcomsh-to-use-wc-calypso-bridge-2.11.5 branch March 9, 2026 13:06
@github-actions github-actions bot removed [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Status] In Progress labels Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants