- Keygen v1.1 introduces backwards-compatible breaking changes via API versioning system inspired by Stripe, allowing older versions to function unaffected.
- The main change in v1.1 refactors the distribution API: releases now have many artifacts instead of a one-to-one relationship, moving attributes from releases to artifacts.
- The new publishing flow involves creating a release (draft state), uploading multiple artifacts, explicitly publishing the release, and optionally tagging it (e.g., 'latest').
- To upgrade app integration, first pin all current API requests to v1.0 using the 'Keygen-Version' header, then upgrade to v1.1, replacing the deprecated upgrade action with the new upgrade endpoint.
- Support for the 'arch' attribute should be introduced incrementally after most users upgrade to v1.1 to avoid breaking upgrades from older clients.
- Finally, upgrade the account's pinned version and webhook endpoints to v1.1, though staying on v1.0 indefinitely is optional.