[wp-meta] [Making WordPress.org] #6465: Add support for `ancestor` block.json property

[Making WordPress.org]

#6465: Add support for `ancestor` block.json property
------------------------------+-------------------------
 Reporter:  dd32              |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  needs-patch
------------------------------+-------------------------
 [https://wordpress.slack.com/archives/C1LBM36LC/p1661946027751319 As
 reported in Slack], the block directory validator is rejecting plugins
 which use the new WordPress 6.0+ `ancestor` property instead of the more
 limiting `parent` property.

 This results in plugins that may be eligible for the block directory being
 rejected as containing multiple blocks.

 This also appears to cause the plugins listing to list all of the blocks,
 rather than just the parent blocks.

 Here's an example block.json for a block that was detected as being a non-
 child block from the Slack thread:
 https://plugins.trac.wordpress.org/browser/gutena-forms/trunk/build/form-
 field/block.json?rev=2777775

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6465>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org