Next Release: changelog and version packages - #641
Open
github-actions[bot] wants to merge 2 commits into
Open
Conversation
clavery
force-pushed
the
changeset-release/main
branch
from
August 28, 2026 20:24
02b5e82 to
396adcf
Compare
clavery
requested review from
patricksullivansf,
wei-liu-sf and
yhsieh1
as code owners
August 28, 2026 20:24
Contributor
Author
📘 Docs previewYour documentation changes are published at: https://d3uhw92m2zac57.cloudfront.net/pr-641/ Commit This preview updates on every push and is removed when the PR is closed. |
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@salesforce/b2c-cli@1.23.3
Patch Changes
#642
a0214e4- Allow SLAS clientget,update,delete, andopencommands to use the configured SLAS client ID when their positional client ID is omitted, while keeping the positional value as an explicit override. (Thanks @clavery!)Updated dependencies [
a0214e4]:@salesforce/b2c-dx-mcp@2.1.3
Patch Changes
a0214e4]:@salesforce/b2c-tooling-sdk@1.24.3
Patch Changes
a0214e4- Allow SLAS clientget,update,delete, andopencommands to use the configured SLAS client ID when their positional client ID is omitted, while keeping the positional value as an explicit override. (Thanks @clavery!)b2c-vs-extension@1.1.5
Patch Changes
a0214e4]:@salesforce/b2c-dx-docs@0.3.24
Patch Changes
a0214e4- Allow SLAS clientget,update,delete, andopencommands to use the configured SLAS client ID when their positional client ID is omitted, while keeping the positional value as an explicit override. (Thanks @clavery!)@salesforce/b2c-agent-plugins@1.8.6
Patch Changes
46ab439- Lead SCAPI checkout guidance with the documented order payment-instrument authorization, placement, and failure lifecycle while retaining single-phase order hook orchestration as an option. (Thanks @clavery!)#642
a0214e4- Allow SLAS clientget,update,delete, andopencommands to use the configured SLAS client ID when their positional client ID is omitted, while keeping the positional value as an explicit override. (Thanks @clavery!)