[wp-meta] [Making WordPress.org] #8214: Plugin/Theme Info API: Include closure reason and permanence for closed packages

[Making WordPress.org]

#8214: Plugin/Theme Info API: Include closure reason and permanence for closed
packages
--------------------------+--------------------
 Reporter:  retlehs       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:
Component:  API           |   Keywords:
--------------------------+--------------------
 The `/plugins/info/1.2/` and `/themes/info/1.2/` endpoints currently
 return `{"error": "closed"}` for all closed packages, with no distinction
 between closure types.

 The WordPress.org HTML pages already display detailed closure information,
 e.g.:

 - "This plugin has been closed as of March 30, 2026 and is not available
 for download. This closure is permanent. Reason: Author Request."
 - "This plugin has been closed as of March 29, 2026 and is not available
 for download. This closure is temporary, pending a full review."

 It would be helpful if the API response included this information, e.g.:

 {{{
 #!json
 {
   "error": "closed",
   "closed_date": "2026-03-30",
   "closed_reason": "author-request",
   "closed_permanent": true
 }
 }}}

 **Use case:** On [https://wp-packages.org WP Packages] we poll the API to
 detect closures and re-openings. Without knowing whether a closure is
 permanent, we must continue polling permanently-closed packages
 indefinitely, generating unnecessary API traffic. A `closed_permanent`
 field would allow us to stop polling packages that will never return.

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