Hey @flavio-b - thanks for checking on this.
I did some digging here and it looks like shopify_app 23.x already depends on shopify_api ~> 16.0, and that range includes 16.3.0. Based on that, I don’t expect the 2026-07 REST support to need a separate shopify_app change, though I’m confirming that with the team that maintains these gems.
The shopify_api release containing that support hasn’t been published yet. Once it is, it’s my understanding that apps using shopify_app 23.x should be able to pick it up through the existing dependency. I’ll follow up here when I have more on this.
Thanks @Wes-Dev-Shopify! We usually get the shopify_api update as a dependency of shopify_app when that gets its update, but it can take several weeks for it to be released, which delays our ability to migrate. For example, the last two versions were released a couple of weeks after the new API was already in production:
It would be ideal if the unstable API was put on “freeze mode” at least 2 weeks before going live, and at the same time the gems be released with official support for the upcoming version. ex: On June 15, 2026, you’d release the gems with full support for 2026-07.
We don’t use the Collections API for a lot, but this was a very surprising change that did break our app for a few customers. We’re on 2026-04 and weren’t planning on migrating versions anytime soon.
We need an “emergency” upgrade, but no way to do that the official way. It wouldn’t be a problem if a current stable version didn’t have any breaking changes, but if that’s something that can happen going forward, it’s crucial for us to be able to prepare beforehand. I hope that makes sense.
The problem with the collection thing is not about the release cycle. The problem is rather that for some reasons that still puzzle me, Shopify ranked it as a “non breaking” change. From here they release it as any other patch.
I understand the issue is not the API release cycle per se.
It normally wouldn’t be a problem for us to wait a few weeks, or even months, to upgrade from 2026-04 to 2026-07.
But we think 2026-07 presents a different territory. It may happen again in future versions, especially if there’s a big change in the schema.
We just want to be able to migrate 2 weeks before the launch of a new version, to avoid any issues. I’d ask Shopify to please consider releasing the new gem versions at least a couple of weeks before unstable goes live, so we can complete the migration always before the deadline.
Hey @flavio-b - thanks for clarifying. shopify_api 16.3.0 is now available on RubyGems and includes 2026-07 REST API support (cc: @jed). Apps already using shopify_app 23.x don’t need a separate shopify_app release. To update it, run:
bundle update shopify_api
Then set config.api_version = "2026-07" in config/initializers/shopify_app.rb.
I’ve also shared your feedback about making official gem support available early enough for apps to test and migrate before stable API releases. Thanks for sharing that context. While there are no guarantees, it’s helpful to hear how the timing affects your migration planning.
One point of clarification as well: unstable is updated continuously, and features can be added or removed at any time with no guarantee of release.
Hope this helps!
I mirror the concerns of @Tronquin here, to resolve this issue we basically had to update to the latest API version in a mad rush to restore the application. It was a very awkward position that we were put in. This sort of change should have been handled in a more controlled and considered manner with a lot more forward notice and sign posting.
