chore: release packages - #130
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm 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
@channel.io/app-sdk-core@0.25.0
Minor Changes
ecfde4e: Relax six output fields in the commerce (and legacy order) contract that the SDK could not
guarantee:
Claim.createdAt,CommerceOrderItem.claimability, andPayment'sitemsAmount,shippingAmount,discountAmountandrequireRefundBankAccount.Each was declared required while a mall could legitimately have nothing to put there.
Claim.createdAtis a presence-lessdouble, so an unset value is indistinguishable from0andserialization drops the key.
claimabilityis a proto3 message field with implicit presence, so anapp that never computes it emits no key at all — the same reason the four booleans inside it stopped
being required, one level up. The payment fields carry presence, so
0/falsestill serialize;they are relaxed because they are the breakdown of the total, and not every mall separates item
subtotal, shipping and discount, or has a refund bank account concept.
totalAmount— which everymall reports — stays required, alongside
stateandcurrency.Only the canonical schema's
requiredlists change; generated field types are unaffected, so nobuilder or accessor code needs updating. Consumers reading any of these six should treat them as
possibly absent.
@channel.io/app-sdk@0.25.0
Patch Changes
@channel.io/app-sdk-server@0.25.0
Patch Changes
@channel.io/app-sdk-wam@0.25.0
Patch Changes
@basic-example/server@0.0.19
Patch Changes
@basic-example/wam@0.0.19
Patch Changes
@calendar-example/server@0.0.19
Patch Changes
@calendar-example/wam@0.0.19
Patch Changes
@tutorial-example/server@0.0.17
Patch Changes
@tutorial-example/wam@0.0.17
Patch Changes