Backport changelog: file the states.php entry under 7.1 - #82674
draganescu wants to merge 1 commit into
Conversation
The core patch for #81908 was filed under 7.2 when the fix targeted the next major release. It has since been committed as changeset 63474, backported to the core 7.1 branch, and cherry-picked to wp/7.1 in #82383, so it ships in WordPress 7.1.1. File it under 7.1 to keep the sync issue for 7.2 from listing an already-shipped backport. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DP49q1JdSxUhzFFE7ga2DS
draganescu
added
the
[Type] Project Management
|
I have cherry-picked and backported numerous PRs in the past, but to my understanding, such changes are not necessary. The backport changelog directory should simply be determined by which core version is targeted at the time the PR is merged, regardless of whether the PR is actually backported. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Closing per t-hamano's guidance in #82383 (comment) — the backport-changelog directory just tracks plugin/core sync, and the 7.2 filing is fine as it is. |
2 participants
What?
Moves
backport-changelog/7.2/13051.mdtobackport-changelog/7.1/.Why?
The entry tracks the core patch for #81908 (WordPress/wordpress-develop#13051) and was filed under 7.2 when the fix targeted the next major release. Since then the fix was slated for WordPress 7.1.1: the core patch was committed as changeset 63474 and backported to the core
7.1branch, and the Gutenberg PR was cherry-picked towp/7.1in #82383.Filing the entry under
7.1keeps the 7.2 backport sync issue from listing an already-shipped backport. The same move was applied on thewp/7.1cherry-pick branch in #82383 (de457f2).How to test
File move only — no code changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01DP49q1JdSxUhzFFE7ga2DS