Hey folks - thanks for the candid feedback. I’m continuing to share it internally. I recognize the direct impact this has had on your apps. If you’re facing any specific migration blockers, please share them here and we’ll do our best to help work through them.
@Tom_Chan - thanks for sharing those trace IDs. You were correct, the collection you reported wasn’t using any new Collection model features. It was affected by a known bug where some newly created collections using only legacy-compatible rules were incorrectly classified as incompatible with API versions before 2026-07.
The fix has now shipped, and we reprocessed the affected collections. I’ve confirmed that your collection now returns as expected on API version 2026-04 and earlier. This was separate from the intended behaviour for collections that use features older API versions can’t represent, which still require API version 2026-07 or later.
Please continue to flag any behaviour that doesn’t match that distinction, or anything unexpected associated with the rollout. The context you shared helped us trace, confirm and resolve this bug.
@jed - we’re also working to move the open PR adding 2026-07 REST API support to shopify-api-ruby forward, although I don’t have an exact timeline. In the meantime, one developer has reported that temporarily switching to the PR branch until a new version is released is working smoothly for them.
Hope this helps!