Deprecate Pullquote Block
#73228
Merged
Deprecate Pullquote Block
#73228
+61
−261
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
t-hamano
added
[Type] Code Quality
t-hamano
requested review from
ajitbohra,
ellatrix,
fabiankaegy and
juanmaguitar
as code owners
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @timwright12, @mapk, @sarahmonster. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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. |
|
Size Change: -141 B (-0.01%) Total Size: 2.41 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in 62391cb. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/19328176595
|
This was referenced Nov 13, 2025
Contributor
|
I think this PR should have included an update to the block-library changelog. It can be quite an impactful change, and it's also missing from the 22.2 whats new CC @bph |
Contributor
Author
|
@dsas Thanks for the suggestion. What would you like to mention? At the very least, if users already use pullquote blocks, they'll be aware that they're now deprecated. 
If we were to publish any documentation, I think the best place for it would be in the 7.0 dev notes. |
Contributor
|
If users are editing content containing pullquotes then they'll be aware. If they're working on a new page, then they won't see the pullquote block and will be confused. In that regards, the 7.0 release notes is ok. I was expecting to see it in the 22.2 whats new post tbh, but it wasn't mentioned there at all, and I guess the reason for that is because there was no changelog entry. |
Contributor
Author
I think the What's new articles mainly focus on feature enhancements and improvements. As far as I know, deprecation changes have rarely been covered.
|
Contributor
|
Sorry, I must've somehow missed that after reading twice, thank you. |
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.
PullquoteBlock #72028What?
#72028 has been approved, and I have merged the latest trunk into that branch, but somehow the CIs don't run, and the message about resolving conflicts doesn't disappear.
This PR is equal to #72028, so I would like to merge it once CI passes.