← Changelog
UpdatedApps

A rollback brings the files back with the build, and runs from the CLI and API

Rolling back production now puts its files back as that deploy had them, schemas and settings included, as a new version, so the records API reads what the running code was written against instead of the latest schemas. The Deploys row shows what changed, a Shopify app's configuration is released again from the restored files, and records stay as they are. ib-apps rollback returns to the deploy before the live one (--to <deploy> for another), and POST /v1/apps/:app/rollback does the same.

Every deploy from today on keeps production's file set at the version it made, which is what a rollback restores. Rolling back to a deploy from before today changes the build only, as it always did, and the message says so. Rolling back to a rollback works the same way.

More in Rolling back.