Repository navigation
chore: update author, contributors and repository metadata - #4
Merged
Merged
Conversation
Set the author to the current maintainer and move the original author, Simon Knott, into contributors alongside Dylan Brookes and Brandon Bayer so upstream credit is preserved. Point repository at the eridu-tech fork (was upstream blitz-js/superjson); npm validates this against the publishing repository when generating provenance, and it previously warned that the field was auto-corrected on publish. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Updates the package metadata for the
@eridu-tech/superjsonfork.author: Simon Knott ->"Yousif Abdulkarim"(matches the eridu-tech-core reference)contributors: Simon Knott moved here alongside Dylan Brookes and Brandon Bayer, so upstream credit is preserved (MIT fork of blitz-js/superjson)repository: upstreamblitz-js/superjson->git+https://github.com/eridu-tech/superjson.gitWhy the
repositoryfield mattersnpm validates
repositoryagainst the repository that runs the build when generating a provenance attestation, so it must point at this repo for the trusted-publishing flow. It also removes npm's "auto-corrected some errors in your package.json" warning on publish.Verification
package.jsonparses;npm pkg get author contributorsreturns the expected valuesnpm publish --dry-run --access publicis clean (27 files, 16.0 kB, taglatest, public access) with no repository warning