Revert v2.0.0 merge (tracking in #17) - #18
Merged
Merged
Conversation
This reverts commit d75a53c, reversing changes made to 29705aa. The v2.0.0 release was withdrawn before any consumers upgraded — the tag and GitHub Release have been deleted. The per-consumer-tables work is preserved on the `feat/per-consumer-tables` branch and tracked by #17. When that branch is merged later, it will need to either: (a) revert this revert first, or (b) be rebased onto main, so Git does not silently skip the changes as already-merged. Refs: #17 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Jun 24, 2026
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
1 participant
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.
Why
The v2.0.0 release was withdrawn before any consumers upgraded — the tag and GitHub Release have already been deleted. This PR walks
mainback to the v1.6.0 state by reverting the merge from #16.The per-consumer-tables work is preserved on the
feat/per-consumer-tablesbranch and tracked by #17. It will be merged later, after the design + migration story have had more eyes on them.What changes
Revert "Merge pull request #16 from WPBoilerplate/release/v2.0.0"— a single, mechanical revert commit. No conflicts.After this lands
Re-merging
feat/per-consumer-tableslater will need one of:git revert <revert-sha>on the feature branch), orOtherwise Git will silently skip the changes as already-merged.
Refs: #17