Sync version number and changelog from 8.2.1 release#3256
Merged
Conversation
Mirrors the changelog and `@since` updates from the 8.2.1 patch release (branch `release/8.2.1`, commit 8b4371d) back to trunk so future releases see the 8.2.1 entry in their changelog history and the `@since` markers introduced by #3094 reflect the version they shipped in. Intentionally does not bump `Version`, `Stable tag`, or `ACTIVITYPUB_PLUGIN_VERSION` — trunk continues to track the next-release version. Pattern follows #3077 (post-8.0.2 sync).
jeherve
added
the
Skip Changelog
pfefferle
approved these changes
May 1, 2026
pfefferle
requested changes
May 1, 2026
These two entries were folded into CHANGELOG.md and readme.txt by `composer changelog:write` on the `release/8.2.1` branch. They still exist on trunk because the patch release didn't merge back, so without this cleanup the next release would pick them up again and duplicate the entries.
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:
8.2.1entry toCHANGELOG.mdandreadme.txtso future releases include it in their history.@since unreleasedmarkers introduced by Cap remote recipient fetches per incoming activity #3094 with@since 8.2.1to reflect the version they shipped in.This mirrors the changelog and
@sinceupdates from the8.2.1release commit (on branchrelease/8.2.1) back to trunk. The 8.2.1 release was published fromrelease/8.2.1and is already deployed to WordPress.org — this PR brings trunk into the same documentary state.Intentionally does not bump
Version,Stable tag, orACTIVITYPUB_PLUGIN_VERSION— trunk continues to track the next-release version.Pattern follows #3077 (post-8.0.2 sync).
Other information:
Testing instructions:
git checkout update/sync-8.2.1-changelogCHANGELOG.mdhas a new## [8.2.1] - 2026-05-01block at the top, mirroring what shipped onrelease/8.2.1, plus the[8.2.1]: ...compare/8.2.0...8.2.1link.readme.txthas a matching### 8.2.1 - 2026-05-01block under== Changelog ==, and thatStable tag:is still8.2.0.activitypub.phpis unchanged (Version: 8.2.0,ACTIVITYPUB_PLUGIN_VERSION = '8.2.0').git grep "@since unreleased" includes/collection/class-remote-actors.php includes/rest/class-inbox-controller.phpreturns no results; the three formerunreleasedmarkers now read@since 8.2.1.