@W-22247284@ feat: add --distribution-type flag to package create and update - #1284
Merged
sshyamala-sfdc merged 2 commits intoSep 3, 2026
Conversation
…247284) Add an optional --distribution-type flag to `package create` and `package update`, and surface the distribution type in `package list` (verbose, API 68.0+). The flag accepts PublicSecure or Limited only; the library gates the value at API version 68.0 and rejects backend-only values (Public, Private). On create, omitting the flag lets the backend default the distribution type based on the package type. - --distribution-type flag on create and update (Flags.custom enum) - Distribution Type column in package list - flag messages, command-snapshot, schemas - unit tests asserting flag passthrough, omission, and invalid-value rejection - pin @salesforce/packaging to 5.0.9-spi.6 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…hemas Picks up the library change that removes Private from DistributionType. Regenerated schemas no longer list Private in the DistributionType enum for package list and package version report output. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
btrn11
approved these changes
Sep 3, 2026
sshyamala-sfdc
deleted the
t/packaging-distribution/w-22247284/package-distribution-type
branch
September 3, 2026 20:27
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.
What & why
Adds an optional
--distribution-typeflag tosf package createandsf package update, and surfaces the distribution type insf package list(W-22247284).This is the plugin half of the feature. The business logic, validation, and types live in
@salesforce/packaging; this PR pins the prerelease that ships them (5.0.9-spi.6) and wires up the command surface.Library PR: forcedotcom/packaging#926
Behavior
--distribution-typeacceptsPublicSecureorLimitedonly (oclif enum).PublicandPrivateare backend-only states and are rejected.package list --verboseshows a Distribution Type column at API 68.0+.Changes
--distribution-typeflag onpackage createandpackage update(Flags.custom<SettableDistributionType>({ options: ['PublicSecure', 'Limited'] })), wired into their options.DistributionTypeadded topackage list'sPackage2Result, record mapping, and verbose display column.package_create.md/package_update.md.command-snapshot.jsonentries for create + update; schemas updated (package-list.json,package-version-report.json).@salesforce/packagingto5.0.9-spi.6.Validation
yarn buildclean against the published5.0.9-spi.6(unlinked, real package).snapshot:compareandschema:compareboth report "No changes have been detected."🤖 Generated with Claude Code