Skip to content

fix: revalidate registry catalogs during release readback - #991

Merged
AlexMikhalev merged 1 commit into
mainfrom
codex/registry-cache-revalidation-20261015
Oct 15, 2026
Merged

AlexMikhalev merged 1 commit into
mainfrom
codex/registry-cache-revalidation-20261015

Conversation

@AlexMikhalev

Copy link
Copy Markdown
Contributor

Release readback could keep seeing an old gallery entry after the exact new package had been published. Open VSX returned only 0.1.0 for the default query while the same query with Cache-Control: no-cache returned the newly published 0.1.4. Request revalidation and record that request policy in the receipt.

The exact version, prerelease, trusted-publishing metadata and downloaded payload checks are unchanged. Two captured public responses cover stale-entry refusal and fresh-entry acceptance; the actual network regression passed with all 440 released package files matching and publishedWithTrustedPublishing=true. The captured-fixture test covers parsing, while the paired live requests establish the transport behavior.

Validation: 68 Python tests pass with ResourceWarnings treated as errors, Ruff and git diff --check pass, and an independent reviewer reran the suite. No version bump, package rebuild, tag change, credential or access change. The original failed CI readback is retained; a read-only CI audit of the existing 0.1.4 release will verify the merged fix.

@AlexMikhalev
AlexMikhalev merged commit b9b90ae into main Oct 15, 2026
9 checks passed
@AlexMikhalev
AlexMikhalev deleted the codex/registry-cache-revalidation-20261015 branch October 15, 2026 07:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant