chore(release): v0.24.2 — add the repository field provenance requires - #308
Merged
Conversation
The v0.24.1 publish reached the registry and was rejected: E422 Error verifying sigstore provenance bundle: Failed to validate repository information: package.json: "repository.url" is "", expected to match "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/moshcoder/moshcode" from provenance package.json had no `repository` at all. npm checks the attestation's source repository against that field and refuses the tarball when they disagree — and "" disagrees with everything. It never came up publishing 0.24.0 by hand, because that publish had no --provenance to verify. Bumped to 0.24.2 rather than publishing 0.24.1 from this commit: provenance ties the tarball to the commit it was built from, so publishing 0.24.1 from a commit that is not tagged v0.24.1 would leave an attestation pointing at the wrong place. 0.24.1 stays unpublished — a hole in the sequence, which costs nothing. Also adds `homepage` and `bugs`, which npm shows on the package page and which were likewise missing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ThreatCrush Security Scan92 finding(s) HIGH/CRITICAL: 50 | MEDIUM: 42
…and 42 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
This was referenced Aug 6, 2026
Merged
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.
What broke
The v0.24.1 publish authenticated fine, signed provenance, published the attestation to the transparency log — and was then rejected by the registry:
package.jsonhad norepositoryfield at all. npm checks the attestation's source repository against that field and refuses the tarball when they disagree — and""disagrees with everything.It never surfaced when I published 0.24.0 by hand, because that publish had no
--provenanceto verify.Fix
repository:git+https://github.com/moshcoder/moshcode.git— normalizes to exactly the URL provenance expects (verified)homepageandbugsadded while here; both were missing and npm surfaces them on the package pageWhy 0.24.2 and not 0.24.1
Provenance ties the tarball to the commit it was built from. Publishing 0.24.1 from this commit would leave an attestation pointing at a commit that is not tagged
v0.24.1— misleading to anyone auditing it. So 0.24.1 stays unpublished; a hole in the sequence costs nothing.Verification
moshcode --versionreports 0.24.2repository.urlnormalizes tohttps://github.com/moshcoder/moshcode— asserted, not eyeballedPublishing this release is the last untested step of the pipeline: everything either side of the actual
PUThas now run for real.🤖 Generated with Claude Code