Repository navigation
fix: verify downstream prerelease catalog routes - #992
Merged
Merged
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
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 registry audit could report 0.1.4 missing even when normal editor installation obtained that exact release: Cursor's general catalog query returned 0.1.0, while its documented latest-prerelease query returned 0.1.4. After an absent exact version, the verifier now uses Cursor's documented latest-channel flags or Windsurf's released-client latest-resource metadata route. Historical exact-version discovery remains first.
Every fallback still requires the exact publisher, extension, universal version, prerelease channel, allowed download origin and all qualified extension payload bytes. Raw discovery responses and HTTP failures are retained; HTTP errors stop without automatic retries and record Retry-After without retaining incidental response headers. No packages, release tags, publishing credentials or access boundaries change.
Validation: 71 Python tests pass with ResourceWarning treated as an error. Captured public responses prove Cursor's stale/current metadata distinction; resource-envelope tests retain wrong-version and missing-channel refusals. A fresh anonymous Cursor run found 0.1.4 through the fallback and downloaded an exact match for all 440 qualified extension files. Windsurf returned HTTP 429 with Retry-After after the earlier deadline; that failure is retained and the verifier stops without an HTTP retry. Native host qualification remains separate.