docs(ci-cd): correct the Packagist verification section — wrong endpoint, wrong diagnosis - #381
Merged
Merged
Conversation
…ng the wrong endpoint The section I added a few hours ago said Packagist was not publishing our tags and blamed a missing GitHub App. That diagnosis was wrong, and the way it was reached is the part worth keeping. Packagist serves metadata from two places that do not update together: repo.packagist.org/p2/... is what COMPOSER reads and it is current; packagist.org/packages/....json is what the WEBSITE reads and it lags, here by more than half an hour. I queried the second one, saw a stale version, and built a story around a 202 delivery and an uninstalled GitHub App to explain a failure that was not occurring. Measured: v1.7.0 tagged and pushed; the web endpoint still showed v1.6.0 as newest; the p2 endpoint already had v1.7.0; and resolved to v1.7.0 (b9c6520) the whole time. The section now gives the one-line p2 check Composer itself would make, and names the three things that are not evidence: a ping delivery, an HTTP 202, and package.time — which is the creation timestamp and never moves.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The section added in #375 claimed Packagist was not publishing our tags and blamed a missing GitHub App. That was wrong.
Packagist serves metadata from two endpoints that do not update together:
repo.packagist.org/p2/…packagist.org/packages/….jsonI queried the second, saw a stale version, and built a story around a
202webhook delivery and an uninstalled GitHub App to explain a failure that was not happening.Measured:
v1.7.0tagged and pushed → web endpoint still showedv1.6.0→ p2 endpoint already hadv1.7.0→composer require conduction/hydra-gates:^1.0resolved to v1.7.0 (b9c6520) throughout.The section now gives the one-line p2 check and names the three things that are not evidence: a
pingdelivery, an HTTP202, andpackage.time(creation timestamp, never moves).