feat: add package trust link request command (W-23970567) - #1270
Open
sshyamala-sfdc wants to merge 6 commits into
Open
feat: add package trust link request command (W-23970567)#1270sshyamala-sfdc wants to merge 6 commits into
sshyamala-sfdc wants to merge 6 commits into
Conversation
Add the beta "sf package link request" command that requests a Public Secure trust link from a connected authoring org to a Verified Partner Business Org. The command is hidden and marked beta, consistent with the bundle commands. Includes messages, unit tests, and the command snapshot entry. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…970567@ Move the beta command from "sf package link request" to "sf package trust link request": relocate the command under the new trust/link topic, rename messages, schema, and command snapshot, and update the test to match the new PackageTrustLink library API. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add tests asserting the command logs the output message with the verified org ID and trust link ID, and that a library error propagates out of run() without logging success. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sshyamala-sfdc
changed the title
Point @salesforce/packaging at the packaging-distribution/spi branch so CI resolves a packaging build that contains PackageTrustLink, instead of the published 5.0.8 which predates the trust-link API. Temporary until a packaging prerelease is published; revert to a pinned version before merge. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The git dependency resolves to codeload.github.com, which the repo's yarn-lockfile-check (lockfile-lint --allowed-hosts npm yarn) rejects, gating every CI job. Restore @salesforce/packaging to ^5.0.4 and the clean lockfile. A published packaging prerelease is required instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Pin the packaging prerelease published from the SPI branch so CI resolves a registry tarball that contains PackageTrustLink, instead of the older published 5.0.4 which predates the trust-link API. Lockfile resolves via the public npm registry so it passes yarn-lockfile-check. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
4 tasks
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
Adds the beta
sf package trust link requestcommand that requests a Public Secure trust link from a connected authoring org to a Verified Partner Business Org (PBO).Details
package trust link requestwith--verified-org/-i(required,00DSalesforce ID) plus standard--target-org/--api-version.hidden = trueandstate = 'beta', consistent with thebundlecommands, so it does not surface inpackage -hwhile in beta. Following that convention, notrustsubtopic is declared inpackage.json.PackageTrustLink.requestin the packaging library.schemas/package-trust-link-request.json), command-snapshot entry, and unit tests (success, flag pass-through, output logging, library-error propagation, invalid-org rejection).Testing
yarn buildandyarn testpass (snapshot + json-schema + deprecation-policy checks clean).W-23970567
🤖 Generated with Claude Code