fix(core): add repository/homepage/bugs to package.json#21
Merged
Conversation
The v0.0.5 npm core publish failed with E422 because npm Trusted Publishing's sigstore provenance check expects package.json's repository.url to match the GitHub repo URL. Without the field, the comparison value was "" and provenance validation rejected the upload. Adds the standard repository/homepage/bugs trio so the next workflow_dispatch run on release-core.yml lands cleanly. Pure metadata fix — the published bundle's runtime is unchanged.
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.
Summary
repository,homepage, andbugsfields tocore/package.jsonso npm Trusted Publishing's sigstore provenance check can validate the upload.Why
The v0.0.5 npm core release (run 24958572913) failed with:
```
422 Unprocessable Entity ... Error verifying sigstore provenance bundle:
package.json: "repository.url" is "", expected to match "https://github.com/MolCrafts/molvis"
```
Without the field, the comparison value was `""` and provenance validation rejected the upload. PyPI and VS Marketplace v0.0.5 published successfully — only npm core was blocked.
Plan after merge
`workflow_dispatch` on `release-core.yml`. The workflow uses the default branch ref, so it picks up this fix even though the v0.0.5 tag points to the old commit. Pure metadata fix; runtime is unchanged.
Test plan