Skip to content

chore: release packages - #115

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: release packages#115
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

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.24.0

Minor Changes

  • 494c902: Replace the getExchangeableItems output with exchangeableItems, which carries the variants an
    order item can be exchanged for. The previous items only listed which order items were
    exchangeable, so there was no way to learn the variantId that requestExchangeOrder's
    afterExchangeItems requires — the exchange flow could not be implemented from the contract alone.
    Each variant carries its additionalAmount, human-readable options, and stock: stockQuantity is
    left unset when a variant does not track inventory, so 0 (sold out) stays distinguishable from
    unlimited, with useInventory telling the two apart.

    items is removed rather than kept alongside: no app implements commerce getExchangeableItems in
    either production or exp, and no task calls it, so nothing consumes the field today.

    OrderClaimability gains four reason fields — nonCancelableReason, nonReturnableReason,
    nonExchangeableReason, nonShippingAddressChangeableReason. The booleans alone cannot explain
    why a claim is unavailable, which malls do report and tasks need in order to tell the customer.
    Commerce and order extensions share the type, so both getOrders outputs carry them.

  • 3e4e4b1: Widen the commerce order contract with fields malls already return but the contract could not
    carry — payment.taxAmount, item sku/taxLines/unfulfilledQuantity/requiresShipping/selling
    plan, and order adminUrl/note/display statuses/billingAddress/shippingLines/transactions/
    metafields/customAttributes. OrderTransaction exists so cash-on-delivery and deferred payment
    can be told apart, which payment.methods alone cannot express.

    OrderClaimability's four booleans now carry explicit presence. A proto3 plain bool cannot tell
    false from unset, so JSON serialization dropped every false and an item that allowed no claim
    at all was emitted as claimability: {}, contradicting the schema that advertises those fields as
    required. Generated field types change from bool to an optional boolean, so code that builds
    OrderClaimability through struct literals needs updating; accessors are unchanged.

  • 65d4196: Stop dropping order-contract fields whose zero value is a real value. protojson omits a field
    without presence when it holds the zero value, so fields the contract declares as required went
    missing in common situations — claims on an order with no claims, shippingAmount on free
    shipping, success: false on a failed action. The declaration and the wire format disagreed, and
    consumers read undefined where the contract promised a value.

    Given presence so the value is emitted (still required) — zero and false are real values here:

    • CommerceResultBody.success
    • OrderPayment.totalAmount / itemsAmount / shippingAmount / discountAmount /
      requireRefundBankAccount
    • CommerceOrderItem.amount
    • CommerceExchangeableVariant.additionalAmount

    The Go types change from float64/bool to *float64/*bool, so an app that fills these must
    set them through a pointer. Leaving one unset omits the key exactly as before.

    Dropped from required — these are repeated fields, and protobuf does not allow optional on
    them, so an empty list is indistinguishable from an absent one:

    • Order.claims / Order.fulfillments
    • OrderPayment.methods
    • OperationOptions.required / OperationOptions.optional

    The last two are shared by the order and commerce extensions, so both contracts change.

Patch Changes

  • 0ff5a85: Export Go aliases for the commerce order value types added alongside the widened order contract —
    TaxLine, Attribute, ShippingLine, Transaction, and Metafield. Their generated code lives
    under an internal package, so without an alias an app could see the fields in the schema but had no
    way to construct the values.

    A test walks the proto descriptors reachable from the order contract and fails when one of those
    messages has no alias in the commerce package, so adding a message without exporting it is caught
    rather than discovered by the first app that needs the value.

  • 2862b3d: Add the optional numeric errorCode field to MessagingSendResult so messaging apps can return a
    stable failure reason from onMediumMessageCreated. The runtime can persist the code on the failed
    Channel message and pass it to getMediumMessageErrorReason for a safe user-facing explanation.

@channel.io/app-sdk@0.24.0

Patch Changes

  • Updated dependencies [494c902]
  • Updated dependencies [3e4e4b1]
  • Updated dependencies [65d4196]
  • Updated dependencies [0ff5a85]
  • Updated dependencies [2862b3d]
    • @channel.io/app-sdk-core@0.24.0
    • @channel.io/app-sdk-server@0.24.0
    • @channel.io/app-sdk-wam@0.24.0

@channel.io/app-sdk-server@0.24.0

Patch Changes

  • Updated dependencies [494c902]
  • Updated dependencies [3e4e4b1]
  • Updated dependencies [65d4196]
  • Updated dependencies [0ff5a85]
  • Updated dependencies [2862b3d]
    • @channel.io/app-sdk-core@0.24.0

@channel.io/app-sdk-wam@0.24.0

Patch Changes

  • Updated dependencies [494c902]
  • Updated dependencies [3e4e4b1]
  • Updated dependencies [65d4196]
  • Updated dependencies [0ff5a85]
  • Updated dependencies [2862b3d]
    • @channel.io/app-sdk-core@0.24.0

@basic-example/server@0.0.16

Patch Changes

  • Updated dependencies [494c902]
  • Updated dependencies [3e4e4b1]
  • Updated dependencies [65d4196]
  • Updated dependencies [0ff5a85]
  • Updated dependencies [2862b3d]
    • @channel.io/app-sdk-core@0.24.0
    • @channel.io/app-sdk-server@0.24.0

@basic-example/wam@0.0.16

Patch Changes

  • @channel.io/app-sdk-wam@0.24.0

@calendar-example/server@0.0.16

Patch Changes

  • Updated dependencies [494c902]
  • Updated dependencies [3e4e4b1]
  • Updated dependencies [65d4196]
  • Updated dependencies [0ff5a85]
  • Updated dependencies [2862b3d]
    • @channel.io/app-sdk-core@0.24.0
    • @channel.io/app-sdk-server@0.24.0

@calendar-example/wam@0.0.16

Patch Changes

  • @channel.io/app-sdk-wam@0.24.0

@tutorial-example/server@0.0.14

Patch Changes

  • Updated dependencies [494c902]
  • Updated dependencies [3e4e4b1]
  • Updated dependencies [65d4196]
  • Updated dependencies [0ff5a85]
  • Updated dependencies [2862b3d]
    • @channel.io/app-sdk-core@0.24.0
    • @channel.io/app-sdk-server@0.24.0

@tutorial-example/wam@0.0.14

Patch Changes

  • @channel.io/app-sdk-wam@0.24.0

@channeltalk

channeltalk Bot commented Sep 4, 2026

Copy link
Copy Markdown

@github-actions
github-actions Bot requested a review from ririro93 September 4, 2026 07:45
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from a55c7af to 98360de Compare September 6, 2026 15:36
@github-actions
github-actions Bot requested review from jyjy1229 and removed request for ririro93 September 6, 2026 15:36
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 98360de to 0bd288c Compare September 7, 2026 08:26
@github-actions
github-actions Bot requested review from ririro93 and removed request for jyjy1229 September 7, 2026 08:26
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 0bd288c to 4be98aa Compare September 8, 2026 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants