Opened 4 years ago

Closed 4 months ago

#5393 closed enhancement (reported-upstream)

Add to Packagist

Reported by: clarinetlord's profile clarinetlord Owned by:
Milestone: Priority: normal
Component: Version Control Keywords:


Transferred from:
Currently, the WordPress Develop repo is not on Packagist, even though it now has a composer.json file (thanks to In order to use as a dependency, for example to use as a foundation to building an automated testing suite for a theme or plugin, you need to manually add the Github URL as an additional repository definition in your project's composer.json file. Normally this wouldn't be much of an issue, but due to the large number of branches and tags, Composer has to search the entire repo to generate a list of tags and branches available on every install/update, which takes several minutes! Adding WordPress Develop to Packagist (to be alongside, would parse and cache branches and tags as they are released via the Packagist Github hook.

Change History (2)

#1 @dd32
4 years ago

Hi @clarinetlord,

While the WordPress Meta team manages the infrastructure, we're not the best team to do this, instead, I'd probably redirect you back to the Core Team to figure it out - even though they sent you here

#2 @coffee2code
4 months ago

  • Resolution set to reported-upstream
  • Status changed from new to closed

Closing this as reported-upstream since this seems to be tracked in which is a better place for it than meta.trac.

Note: See TracTickets for help on using tickets.