Repository navigation
Add repository field to package.json (fixes E422 provenance on publish) - #5
Merged
Merged
Conversation
npm OIDC provenance validation requires package.json repository.url to match the GitHub repo from the sigstore provenance bundle; the generated package.json has no repository field, so publish failed with E422: "package.json: repository.url is "", expected to match https://github.com/flipdishbytes/api-client-javascript from provenance"
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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
2 participants
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.
Why
The publish run to master failed with:
npm OIDC provenance validation requires
repository.urlin package.json to match the GitHub repo. The generated package.json has no repository field (unlike@flipdish/api-client-typescript, which has one — same format used here).What
"repository": {"type": "git", "url": "git+https://github.com/flipdishbytes/api-client-javascript.git"}to package.json.Note
The generator (openapi-generator javascript template) does not emit this field — after the next Zeus regeneration it will disappear again unless the generator is fixed. Tracking that in the generator-repo work (Part 3).
Summary by CodeRabbit