[B/C Break] Use the v2 metadata for package metadata, misc. dependency updates, new API endpoints #22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Great! Could you make the tests pass as well? Feel free to drop everything below PHP 8.2 and make use of modern PHP features if needed 👍 |
- Listing popular packages - Getting the dev branch package metadata - Getting a package's download stats
mbabker
changed the title
Contributor
Author
|
@freekmurze I've gone ahead and done a bunch of updates to get this package up-to-date and the CI's passing on my fork - https://github.com/mbabker/packagist-api/actions/runs/13741661886 - so we should be good here. |
Member
|
Stellar work, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Per https://packagist.org/apidoc the v1 metadata endpoint is deprecated and stopped receiving updates as of February 1 and will be removed entirely later this year. This PR therefore updates the client to use the v2 metadata endpoint instead.
This will require a new major version because the data structure between the two metadata endpoints is slightly different and consuming applications will need to update their code.
As suggested, this also bumps the required PHP version to PHP 8.2, uses Pint and Rector to do some automated refactoring, and updates the CI configuration to match what's happening in some of the other Spatie repositories.
I've also gone ahead and added support for other endpoints that weren't previously covered, which will allow consumers to: