Current record
No public release entries have been announced.
There are no announced release entries to review here yet. You can inspect the current machine-readable contracts and supporting documentation; future entries will identify changes announced for external integrations.
Entry format
Look for the affected contract, required action and timing.
What changed?
Platform API, Shopify API, outbound webhooks, provider ingress, documentation or an integration connector.
Is it compatible?
Additive, corrective, deprecated or breaking, with the affected versions and operations named.
What must clients do?
Required migration steps, compatibility considerations or confirmation that no client action is needed.
When does it apply?
Announcement date, environment availability, deprecation window and production effective date.
Compatibility policy
Version boundaries protect existing clients.
- Additive
- Optional fields and new operations may be added within
v1. Clients should ignore response fields they do not use. - Corrective
- Documentation or behavior may be corrected to match the published contract without changing the versioned resource shape.
- Deprecated
- An operation planned for removal will receive a published replacement and effective timeline before a version boundary is retired.
- Breaking
- Removing a field or operation, changing a required type or making an optional request field required needs a new version boundary.
Use documented fields, avoid exhaustive assumptions about future optional fields, and review this changelog before production upgrades.