Skip to content
This repository was archived by the owner on Feb 5, 2026. It is now read-only.
This repository was archived by the owner on Feb 5, 2026. It is now read-only.

Should this repository be archived? #160

Open

Description

@jonathanbossenger

Since the Abilities API is now merged into WordPress Core (PHP) and Gutenberg (JavaScript), which will likely land in Core for 7.0, should we archive this repository?

Activity

  1. justlevine commented on Jan 29, 2026

    @justlevine
    Contributor

    IMO a very strong yes. Even if we decide to backport from core and polish a little while longer, we can always temporarily unarchive it.

    If/before we do I'd want to do a single docs-polish sweep to point people to the latest/correct sources. (If we don't we should probably do that anyway).

    CC: @Jameswlepage who IIRC was very strongly in the pro-Composer package camp. (Hoping that with Abilities in Core, woo's R-2 support policy and the last 3 months of reported conflicts + breaks changes the old arithmetic )

  2. jeffpaul commented on Jan 29, 2026

    @jeffpaul
    Member
  3. Jameswlepage commented on Feb 1, 2026

    @Jameswlepage
    Contributor

    Yep, I don't see any reason to keep this open anymore. Now that it's in Core, it has served its purpose :)

  4. jeffpaul commented on Feb 4, 2026

    @jeffpaul
    Member

    @dd32 @desrosj are either of you able to help archive this repo (based on the above discussion)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions