Repository navigation
Repair wp/6.0 branch Actions: Remove the navigation menu edit permission e2e test - #84292
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
|
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. |
6217d20 to
9aab5c5
Compare
9aab5c5 to
4d3f6bc
Compare
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
4d3f6bc to
b63fd71
Compare
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
b63fd71 to
8a73684
Compare
8a73684 to
9d401a4
Compare
Part of #82933.
What?
Removes the "Navigation › Permission based restrictions › shows a warning if user does not have permission to edit or update navigation menus" e2e test from
packages/e2e-tests/specs/editor/blocks/navigation.test.js. The other test in thatdescribeblock, for a user without permission to create navigation menus, is kept.Why?
The test fails on every run on this branch, on all 3 attempts, in "Admin - 3". It times out waiting for the "You do not have permission to edit this Menu. Any changes made will not be saved." notice.
.wp-env.jsonon this branch runs WordPress fromWordPress/WordPress#6.0-branch, which now includes the WordPress 6.0.11 security change WordPress/WordPress@80f65db ("REST API: Increase the specificity of capability checks for collections when theeditcontext is in use"). With it, a collection request made withcontext=editonly returns the posts the user can edit. The test creates a navigation menu as an Administrator, then inserts a Navigation block as a Contributor, who can read but not edit that menu. The block requests the menus withcontext=edit, so the Administrator's menu is no longer in the list, the block never selects it, and the notice the test waits for is never shown.Trunk removed this test in #41306 (10594b1), and
wp/6.1and newer don't have it. Pinning WordPress to 6.0.10 would make it pass again, but would test against a version without the 6.0.11 security fixes.How?
Deletes the test. No imports or helpers became unused.
Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.
🤖 Generated with Claude Code