-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blocks: Update '__experimentalHasContentRoleAttribute' deprecation #65616
Blocks: Update '__experimentalHasContentRoleAttribute' deprecation #65616
Conversation
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. |
Size Change: -3 B (0%) Total Size: 1.77 MB
ℹ️ View Unchanged
|
Thanks for the follow-up |
Flaky tests detected in f092c92. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11014594053
|
There was a conflict while trying to cherry-pick the commit to the wp/6.7 branch. Please resolve the conflict manually and create a PR to the wp/6.7 branch. PRs to wp/6.7 are similar to PRs to trunk, but you should base your PR on the wp/6.7 branch instead of trunk.
|
Thanks for this. I thought we'd (collectively) agreed in the PR that was the way to play it. My mistake. |
That's useful context. Thanks 👍 |
…65616) Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
…65616) Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
What?
This is a follow-up to #65484.
PR removes alternative suggestion from
__experimentalHasContentRoleAttribute
selector deprecation.Why?
The suggested alternative is a private API. Public API deprecations shouldn't recommend private APIs, as they make deprecation unactionable for consumers.
Testing Instructions
None.