Revert the Reprint exporter (#50369 and follow-ups) - #51179
Merged
Conversation
Reverts three commits: ef955ac Add Reprint exporter outside wpcomsh (#50369) 8ab6a94 Reprint export: guard Host::is_pressable() against older Status packages (#51028) 9bd2221 Reprint export: test compatibility with older Status packages (#51031) #51031 is included because it only tests the guard #51028 added, and it edits files #50369 created. It cannot stand on its own. This drops: - The Reprint exporter, its REST controller and their tests. - Host::is_pressable() from the Status package. Nothing else used it. - exclude-from-classmap support for the root package in the autoloader. No project in the monorepo uses that setting. - The wp-php-toolkit/reprint-exporter dependency from the Jetpack plugin. composer.lock now matches its pre-#50369 content hash. Atomic sites keep exporting through wpcomsh, which this never touched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
github-actions
Bot
added
[Package] Autoloader
[Package] Status
[Plugin] Jetpack
Contributor
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
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:
If you have questions about anything, reach out in #jetpack-developers for guidance! Jetpack plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
github-actions
Bot
added
the
[Status] Needs Author Reply
Code Coverage SummaryCoverage changed in 3 files.
|
github-actions
Bot
removed
[Status] Needs Author Reply
haqadn
added a commit
that referenced
this pull request
Aug 11, 2026
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
wp-php-toolkit/data-liberation/vendor-patched/symfony/polyfill-intl-normalizer/Normalizer.phpas potentially malicious code. That's a false positive, but this gives us a chance to reassess how to ship the changes we need)Related product discussion/links
Does this pull request change what data or activity we track or use?
No
Testing instructions
TBD