Skip to content

Sync with upstream v1.9.33 (adds OBFUSCATED_SHIPMENT_ID) - #4

Merged
ProNotion merged 13 commits into
integration/AMZDWfrom
sync/upstream-v1.9.33
Oct 13, 2026
Merged

ProNotion merged 13 commits into
integration/AMZDWfrom
sync/upstream-v1.9.33

Conversation

@ProNotion

@ProNotion ProNotion commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Syncs this branch with upstream/main (v1.9.33).

Why

The v2024-06-19 Finances API now returns OBFUSCATED_SHIPMENT_ID as a related identifier name. Without it in RelatedIdentifierNameEnum, deserialising ListFinancialTransactions responses throws. Upstream abuzuhri#956 adds the value.

What's in it

  • feat(finances): v0 financial events by shipment ID (GET /finances/v0/financialEvents/shipment/{shipmentId}), with NextToken pagination and a rate limit entry.
  • Merge of upstream/main: OBFUSCATED_SHIPMENT_ID, missing IssueCategory enum values, model constructor and Equals recursion fixes, notification speed fix, AWS SDK bumps.

Testing

Built and tested against a consuming application; its unit test suite passes.

abuzuhri and others added 11 commits August 29, 2026 23:25
Amazon started returning OBFUSCATED_SHIPMENT_ID in relatedIdentifierName
on the Finances 2024-06-19 listTransactions response on 10 September 2026.
The enum does not carry it, so StringEnumConverter throws and the whole
page fails to deserialize (abuzuhri#955).

The value is a short opaque token that accompanies SHIPMENT_ID and never
replaces it. It is not in Amazon's published model for this API, as
EVENT_GROUP_ID and SAFET_CLAIM_ID before it were not.

Verified against a live listTransactions response that previously threw.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ributor constructor

Equals(object) cast its argument to an unrelated type in seven models, so
overload resolution bound the call back to Equals(object) itself and the
method recursed unconditionally, for any argument including null. That
kills the process with an uncatchable StackOverflowException as soon as
Json.NET serializes such an instance, because CheckForCircularReference
calls Contains on the serialize stack, which invokes Equals on the objects
it holds. Affected: ItemContributors, ItemContributorRole,
GetFeedsResponseV00, GetReportsResponseV00,
GetMessagingActionsForOrderResponseLinks, OrderedQuantityDetails and
OrderStatus.

GetMessagingActionsForOrderResponseLinks also called itself from the typed
Equals overload; it now compares Self and Actions like the other generated
models.

ItemContributor's constructor discarded both parameters and assigned an
empty role instead of the supplied value and role.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
AsinIdentifier and Audience had empty constructor bodies, Money never
assigned Amount even though it is documented as required, and
OrderAcknowledgementItem dropped vendorProductIdentifier. Callers that
build these models through the constructor lost the values without any
hint; OrderAcknowledgementItem is a request model, so the identifier was
missing from submitAcknowledgement payloads.

Deserialization was unaffected, since Json.NET uses the [JsonConstructor]
parameterless constructors and the property setters.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ingEnumValues

fix: add missing PRODUCT and LISTING values to IssueCategory enum
…d-shipment-id

Add OBFUSCATED_SHIPMENT_ID to RelatedIdentifierNameEnum
…dConstructorInit

fix(models): infinite recursion in Equals overrides and constructors dropping their parameters
@ProNotion
ProNotion force-pushed the sync/upstream-v1.9.33 branch from 03c0246 to 3e953ed Compare October 13, 2026 06:28
Wraps GET /finances/v0/financialEvents/shipment/{shipmentId} with NextToken
pagination and its own rate limit entry.
Brings in OBFUSCATED_SHIPMENT_ID on RelatedIdentifierNameEnum (upstream abuzuhri#956),
missing IssueCategory enum values, model constructor and Equals fixes, and
notification speed fixes.
@ProNotion
ProNotion force-pushed the sync/upstream-v1.9.33 branch from 3e953ed to cae50c9 Compare October 13, 2026 06:29
@ProNotion
ProNotion merged commit dd09145 into integration/AMZDW Oct 13, 2026
@ProNotion
ProNotion deleted the sync/upstream-v1.9.33 branch October 13, 2026 06:31
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.

4 participants