With Sentry CLI 3.0, we should more clearly define what self-hosted versions we support, as well as what types of changes are considered breaking from a SemVer perspective.

Some ideas are listed below.

• Version support: We should only support the latest self-hosted Sentry version, on the date of the CLI 3.0 release, plus all later self-hosted versions. Backwards-compatibility with older self-hosted versions should not be guaranteed. Only changes which break compatibility with this minimum self-hosted version should be considered breaking from a SemVer perspective
• Breaking changes would include any runtime changes which could make a feature which previously worked against a supported self-hosted version (or Sentry SaaS) stop working (unless this change is needed to fix a bug), e.g. removing a command
  • However, increasing the officially supported self-hosted version is not a breaking change
• Compile-time breaking changes (e.g. additional compile-time dependencies, adding/removing of feature flags, bump of MSRV, etc) will not result in a SemVer bump – though, such changes would generally be made in a minor release