Skip to content

fix: normalize npm 12 registry responses - #23

Merged
witqq merged 1 commit into
masterfrom
fix/npm12-registry-response
Sep 5, 2026
Merged

fix: normalize npm 12 registry responses#23
witqq merged 1 commit into
masterfrom
fix/npm12-registry-response

Conversation

@witqq

@witqq witqq commented Sep 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • normalize npm 12 single-field registry JSON as either a string or a one-element array
  • reuse the same strict HTTPS URL parser in preflight and final verification
  • poll newly published versions for up to two minutes before the final exact-byte comparison

Verification

  • live npm 12 registry response for @witqq/spreadsheet@0.6.0 normalizes to its exact HTTPS tarball URL
  • actionlint passes
  • npm run check:workflows passes
  • git diff --check passes

All six v0.6.0 packages were published with provenance by run 33993863690. This change makes the final immutable byte verification compatible with npm 12 and registry propagation.

Made with Moira

Accept the observed one-element JSON array and wait for newly published versions to become visible before comparing exact registry bytes.
@witqq
witqq merged commit 3f4af02 into master Sep 5, 2026
1 check passed
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