Skip to content

Conversation

@grzegorz-cp
Copy link
Contributor

Proposed changes:

Backports changes for inspect 2.0.0-a.9

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

N/a

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

No

Testing instructions:

Proofread changes.

Copilot AI review requested due to automatic review settings January 9, 2026 03:31
@grzegorz-cp grzegorz-cp added [Status] Needs Review This PR is ready for review. [Type] Janitorial labels Jan 9, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 9, 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 a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ 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!


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

Copy link
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 backports changes from the inspect plugin version 2.0.0-a.9 release back to trunk. The changes include version number updates across configuration files and consolidated changelog entries.

  • Version bumped from 2.0.0-a.7 to 2.0.0-a.9 across all plugin files
  • Changelog updated with new features (IDC revalidation, WordPress 6.9 support), dependency updates, and bug fixes
  • Individual changelog entry files removed after consolidation

Reviewed changes

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

Show a summary per file
File Description
projects/plugins/inspect/readme.txt Updated stable tag to 2.0.0-a.9 and added changelog entry for the new version
projects/plugins/inspect/package.json Bumped version to 2.0.0-a.9
projects/plugins/inspect/jetpack-inspect.php Updated plugin version header to 2.0.0-a.9
projects/plugins/inspect/composer.json Updated autoloader suffix to reflect new version
projects/plugins/inspect/CHANGELOG.md Added 2.0.0-a.9 release entry with change details and comparison link
projects/plugins/inspect/changelog/* Removed 13 individual changelog entry files that were consolidated into the release

@jp-launch-control
Copy link

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

@grzegorz-cp grzegorz-cp merged commit 4e01332 into trunk Jan 9, 2026
80 checks passed
@grzegorz-cp grzegorz-cp deleted the prerelease branch January 9, 2026 03:45
@grzegorz-cp grzegorz-cp self-assigned this Jan 9, 2026
@github-actions github-actions bot removed the [Status] Needs Review This PR is ready for review. label Jan 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.

2 participants