Add repository.url to legacy JS client - #419
Merged
Merged
Conversation
This fixes npm Trusted Publishing for the `@solana/spl-memo` (`clients/js-legacy`) package. Its `repository` field still pointed at the old `solana-labs/solana-program-library` monorepo, but npm's Trusted Publishing requires `repository.url` to exactly match the GitHub repository configured as the trusted publisher (`solana-program/memo`). This mismatch caused the publish job to fail. The field is updated to the object form used by the working `clients/js` package, with a `directory` key so npm can locate the package within the monorepo for provenance attestation.
lorisleiva
changed the title
repository.url to legacy JS client
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.
This PR fixes npm Trusted Publishing for the
@solana/spl-memo(clients/js-legacy) package. Itsrepositoryfield still pointed at the oldsolana-labs/solana-program-librarymonorepo, but npm's Trusted Publishing requiresrepository.urlto exactly match the GitHub repository configured as the trusted publisher (solana-program/memo). This mismatch caused the publish job to fail.The field is updated to the object form used by the working
clients/jspackage, with adirectorykey so npm can locate the package within the monorepo for provenance attestation.