Prune repos published on packagist.org #121
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is intended to resolve the discrepancy between this package index and entries for packages by the same name on packagist.org.
The problem is that since this composer repository is no longer kept up to date, any packages referenced here end up getting stuck on old versions due to the precedence the wp-cli composer repository URL takes over the default
packagist.org
index. See wp-cli/package-command#141 (comment)Releasing these packages from the index will ensure they continue to receive updates and are managed by the official Composer index instead.
I filtered this list using the following script which filters out lines for packages which exist on packagist.org by the exact same name. Perhaps it would make sense to include this in the
scripts
part of this repo for use in the future, but I can always include that in a separate PR.Note: this is probably obvious but merging this would still require the index to be regenerated which I'm not sure is automated but just thought I would mention 馃槃