Sign in

Deprecations

Stable

How features are retired in SPG99 and what that means for users of the stable environment.

Updated: March 5, 2026

Feature retirement in SPG99 should be predictable for the user. This is especially important for the stable contract: production scenarios must not break unexpectedly.

What a normal deprecation path looks like

  1. A feature or route is marked as deprecated.
  2. The documentation gets a notice and a recommended migration path.
  3. The change is added to the changelog and API changelog, if it affects integrations.
  4. The user is given a transition period.
  5. Only after that is the old feature retired.

What matters for a stable user

  • removing or changing a stable contract should not happen without a visible transition window;
  • every deprecation should come with a clear replacement path;
  • preview features may change faster than stable ones.

What the user should do

  • follow the changelog and API changelog;
  • do not build new production scenarios on features explicitly marked as deprecated;
  • plan automation and runbook updates in advance if the deprecation affects your routes or CLI procedures.
Why SPG99ArchitectureRoadmapDocumentationBlog