Skip to content

chore: refresh upstream indices - #13

Open
github-actions[bot] wants to merge 1 commit into
trunkfrom
chore/upstream-indices
Open

chore: refresh upstream indices#13
github-actions[bot] wants to merge 1 commit into
trunkfrom
chore/upstream-indices

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 20, 2026

Copy link
Copy Markdown

Automated refresh of upstream indices under shared/references/.

  • WordPress core versions (from api.wordpress.org)
  • Gutenberg releases (from GitHub Releases API)
  • WordPress/ai (canonical AI plugin) releases (from GitHub Releases API)
  • WordPress ↔ Gutenberg mapping (from developer.wordpress.org docs)

If CI fails on this PR, the drift check caught a skill whose
declared canonical release now lags upstream — re-sync that skill
(see docs/upstream-sync.md) as a follow-up.

Summary by Sourcery

Enhancements:

  • Update shared AI plugin release reference data from upstream sources.
@sourcery-ai

sourcery-ai Bot commented Jul 20, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR refreshes the upstream reference index for the canonical WordPress AI plugin releases, updating the local JSON reference to match current data from GitHub Releases and related upstream sources.

File-Level Changes

Change Details Files
Updated the canonical AI plugin releases reference index to reflect the latest upstream data.
  • Refreshed the list of WordPress/ai plugin releases based on the current GitHub Releases feed.
  • Adjusted release metadata (versions, dates, tags, or URLs) where it diverged from upstream.
  • Ensured the JSON structure remains consistent with existing reference index schema under shared/references/.
shared/references/ai-plugin-releases.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant