Repository navigation
Remove release-theme from release docs - #161
Merged
Merged
Conversation
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
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.
Summary
AGENTS.mdstill told agents to runwp-ops release-theme, whileCLAUDE.mdsaid it no longer applies. The script is being removed from wp-ops (imagewize/wp-ops#253), so both files now say the same thing.~/code/nynaeve. Claude or Vibe can write both changelog entries from the branch diff againstmain.mainwork leaves nothing to summarize. This no longer names the script.readme.txt/CHANGELOG.mdparity check, and reworded the drift note to say it came from skipping that check.Release
Version bump to 4.2.2 (patch, docs only) in its own commit:
style.cssVersion:,readme.txtStable tag:and changelog block, andCHANGELOG.md. Parity check passes from 2.3.0 onward. No theme code changes.Tag
v4.2.2after merge.