2024 04 18 release notes (core)
Last updated
Last updated
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Release version | Release date |
---|---|
Patchworks dashboard (frontend)
Release version | Release date |
---|---|
New features, updates, and enhancements of note are summarised by product area, below:
Type | Summary | Ref # |
---|---|---|
Type | Summary | Ref # |
---|---|---|
Type | Summary | Ref # |
---|---|---|
1.15.0
18th April 2024
1.12.0
18th April 2024
Create app error
CPT-2746
GraphQL cursor pagination method
CPT-2672
Webhook rate limit allowance updates
CPT-2220
De-dupe shape UI
CPT-2767
Error when adding second connector
CPT-2763
Empty route shape UI
CPT-2726
Connector shape - endpoints with variables
CPT-2744
Endpoint body option 'none'
CPT-2748
Endpoint body option 'none'
CPT-1085
Fixed issue where selecting a process flow to include in an app could cause the page to become unresponsive, in certain circumstances. Marketplace apps
A new GraphQL cursor pagination method has been added for use with the Shopify GraphQL API. GraphQL cursor pagination
Rate limit allowances for webhooks now vary by core tier. Core subscription tiers
Fixed UI issue where editing de-dupe shape settings and changing the entity
and data pool
values appeared to discard given values.
De-dupe shape
Fixed issue where adding a second connector to a process flow could result in an error under certain circumstances. Building a process flow
Fixed issue where adding two routes to a route shape and then updating the left route with shapes would cause the entire right side of the canvas to be clickable (rather than just the pending empty shape). Route shape
Fixed issue where selecting an endpoint from connector shape settings caused the page to become unresponsive if the given endpoint had associated variables. Connector shape
Fixed issue where setting the body format
to none
for an endpoint resulted in an invalid format error.
Endpoint body options
Fixed issue where setting the body format
to none
for an endpoint could still result in logs showing that raw body
content was passed in. This could happen in cases where an endpoint was previously defined to include raw body
content and then subsequently changed to none
. Now, when an endpoint is saved with body content set to none
, any existing raw body
content is cleared.
Endpoint body options