Skip to content

USF-3972: Order backwards incompatibilities #874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
bdenham wants to merge 5 commits into
base: release
Choose a base branch
from
Draft

USF-3972: Order backwards incompatibilities #874

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7cebf37
Completed USF-3972 docs
bdenham May 9, 2026
65d9594
update based on pm review skill
bdenham May 9, 2026
37e2439
Merge branch 'release' into order-incompatibility
bdenham May 13, 2026
b97958a
Merge branch 'release' into order-incompatibility
bdenham May 13, 2026
8724e01
Merge branch 'release' into order-incompatibility
bdenham May 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion src/content/docs/releases/changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -671,7 +671,17 @@ import Link from '@components/Link.astro';
- **Login as Customer**: Added Login as Customer feature support ([#248](https://github.com/magento-commerce/storefront-compatibility/pull/248)).

**v4.7.12**
- **Guest order cancel with comments**: Resolved an internal server error when calling `requestGuestOrderCancel` on orders that include order comments. The error was introduced when the Order drop-in added `OrderComments` support and the new `comments` field appeared in order responses; the SCP `requestGuestOrderCancel` mutation did not handle the presence of that field, causing a 500 error on cancel requests ([#275](https://github.com/magento-commerce/storefront-compatibility/pull/275)).
- **Guest order cancel with comments**: Resolved an internal server error when calling `requestGuestOrderCancel` on orders that include order comments. The cancellation flow was writing status history entries without an explicit UTC `created_at` timestamp; when the Order drop-in requested `comments { message timestamp }`, the null timestamp caused the GraphQL resolver to return a 500 error. This fix is required for a safe Order drop-in v3.3.0 upgrade on Adobe Commerce 2.4.7 deployments. See the [April 2026 suite notes](/releases/) for the full context ([#275](https://github.com/magento-commerce/storefront-compatibility/pull/275)).
Copy link
Copy Markdown
Contributor

@deepak-soni1 deepak-soni1 May 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bdenham There are some mismatches in the release dates, and different versions appear to be grouped together. Additionally, PR links are exposed, as shown in the shared screenshot. We already addressed this issue with the following PR:
https://github.com/commerce-docs/microsite-commerce-storefront/pull/843/changes

Image Image

Copy link
Copy Markdown
Collaborator Author

@bdenham bdenham May 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will revert this change.

</ChangelogEntry>

<ChangelogEntry
date="2026-04-13"
title="Storefront Compatibility Package v4.8.18"
components={['Storefront Compatibility Package']}
>
The Storefront Compatibility Package has been updated with the following changes. This release accompanies the Order drop-in v3.3.0 release; see the [April 2026 suite notes](/releases/) for the full context.

- **Guest order cancel with comments**: Resolved an internal server error when calling `requestGuestOrderCancel` on orders that include order comments. The cancellation flow was writing status history entries without an explicit UTC `created_at` timestamp; when the Order drop-in requested `comments { message timestamp }`, the null timestamp caused the GraphQL resolver to return a 500 error. Upgrading the Order drop-in to v3.3.0 without this SCP version causes guest cancellation to fail on Adobe Commerce 2.4.8 deployments ([#268](https://github.com/magento-commerce/storefront-compatibility/pull/268)).
Copy link
Copy Markdown
Contributor

@deepak-soni1 deepak-soni1 May 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we remove the PR link from here as well?

Copy link
Copy Markdown
Collaborator Author

@bdenham bdenham May 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR links are there because management wanted to make them available, even thought they are private. I'm not sure why anymore, but for now, I'll leave them.

</ChangelogEntry>

<ChangelogEntry
Expand Down
5 changes: 3 additions & 2 deletions src/content/docs/releases/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ Shoppers can view and remove saved payment cards from their My Account page usin

<Aside type="caution" title="Breaking changes">
- **Product Recommendations v4**: The drop-in switches to the `getRecommendationsUnitsByIds` GraphQL query. If you call the legacy `getRecommendations` function directly, update your integration to use the new API before upgrading to v4.
- Order v3.3.0 (Order Comments): Guest order cancellation stops working if you upgrade the [Order drop-in](/dropins/order/) to v3.3.0 without also updating the Storefront Compatibility Package (SCP). This affects Adobe Commerce on-premises and Adobe Commerce on Cloud deployments only. Order v3.3.0 adds a `comments` field to order responses; without a matching SCP update, the `requestGuestOrderCancel` mutation returns an internal server error. Update the SCP to v4.7.12 (for Adobe Commerce 2.4.7) or v4.8.18 or later (for Adobe Commerce 2.4.8; the April 2026 suite was verified with v4.8.19) at the same time as you upgrade the Order drop-in.
</Aside>

### Highlights
Expand Down Expand Up @@ -90,7 +91,7 @@ The Drop-in SDK (`@dropins/tools`) was upgraded to 1.8.1 in this release with th
|-----------|--------------|
| [**Cart**](/dropins/cart/) v3.2.0 | No user-facing changes in this release |
| [**Checkout**](/dropins/checkout/) v3.2.1 | Full `additionalData` forwarded to `setPaymentMethodOnCart`, enabling vault and other payment methods that require extra fields ([#311](https://github.com/adobe-commerce/storefront-checkout/pull/311)). |
| [**Order**](/dropins/order/) v3.3.0 | New `OrderComments` container displays order-level comments (timestamp and message) for guest and authenticated users ([#68](https://github.com/adobe-commerce/storefront-order/pull/68), [#87](https://github.com/adobe-commerce/storefront-order/pull/87)). |
| [**Order**](/dropins/order/) v3.3.0 | New `OrderComments` container displays order-level comments (timestamp and message) for guest and authenticated users ([#68](https://github.com/adobe-commerce/storefront-order/pull/68), [#87](https://github.com/adobe-commerce/storefront-order/pull/87)). Requires a matching SCP update — see breaking changes. |
| [**Product Details Page**](/dropins/product-details/) v3.0.3 | New `formatValue` prop on [`ProductAttributes`](/dropins/product-details/containers/product-attributes/) for custom numeric attribute value formatting. Numeric attributes (weight, dimensions, custom fields) now render at the display precision configured in Commerce Admin instead of raw database values ([#65](https://github.com/adobe-commerce/storefront-pdp/pull/65)). |
| [**User Account**](/dropins/user-account/) v3.3.0 | New `PaymentMethods` container: lists stored cards (`customerPaymentTokens` query) with brand, masked number, and expiry badge; removes a card via `deletePaymentToken` mutation with confirmation modal. New `PaymentCard` reusable component. `fieldIdPrefix` on `Addresses` now correctly propagated to form field IDs, preventing duplicate HTML IDs when shipping and billing forms render on the same page. Customer dropdown custom attributes prefill correctly from the API ([#51](https://github.com/adobe-commerce/storefront-account/pull/51), [#55](https://github.com/adobe-commerce/storefront-account/pull/55), [#56](https://github.com/adobe-commerce/storefront-account/pull/56), [#57](https://github.com/adobe-commerce/storefront-account/pull/57), [#58](https://github.com/adobe-commerce/storefront-account/pull/58)). |
| [**User Auth**](/dropins/user-auth/) v3.2.0 | No user-facing changes in this release |
Expand Down Expand Up @@ -119,7 +120,7 @@ The Drop-in SDK (`@dropins/tools`) was upgraded to 1.8.1 in this release with th

### Known issues

There are no known issues for this release suite.
- If you already upgraded the Order drop-in to v3.3.0 without a matching SCP update, guest order cancellation returns an internal server error. See the breaking changes section above for the required SCP versions to restore guest cancellation.

### Component compatibility

Expand Down
Loading