> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackra.figentra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support, versioning and end-of-life

> How Stackra versions its packages, what 0.x means, how deprecations run, and the support terms.

## Versions

* **One version for everything.** Every `@stackra/*` package releases at the same version (the changesets `fixed`
  group), and `@stackra-pro/*` releases at that same version
  ([0453](https://docs.stackra.figentra.com/adr/0453-the-stackra-registry-one-npm-compatible-store-on-cloudflare-and-our-own-licence-engine.md) decision
  18\). Install matching versions of all Stackra packages; mixing versions is not supported.
* **Semantic versioning.** A patch fixes, a minor adds, a major breaks.
* **0.x.** Before `1.0.0`, as semver allows, a minor release may break an API. Every breaking release carries a
  written release note (what changes for you, the steps to take, how to verify and roll back;
  [0013](https://docs.stackra.figentra.com/adr/0013-versioning-and-release.md) decision 5).
* **A version is never replaced.** A published version is immutable, also after a deprecation, and the registry
  refuses unpublishing. A fix is a new version.

## Dist-tags

| Tag | Holds |
| - | - |
| `latest` | the current release |
| `next` | a prerelease leading to the next release (`0.1.0-next.<n>`); never moves `latest` |
| `canary` | snapshot builds for early testing ([0177](https://docs.stackra.figentra.com/adr/0177-package-distribution-npmjs-and-keygen.md) decision 7) |

## Deprecation

A deprecated API keeps working for one minor release before `1.0.0`, and for one major release after
([0177](https://docs.stackra.figentra.com/adr/0177-package-distribution-npmjs-and-keygen.md) decision 6). A deprecated package version shows npm's
deprecation warning with the version to move to.

## Changes and upgrades

What changed in each release is in each package's changelog: see [Changelog](https://docs.stackra.figentra.com/customers/changelog.md).

## Security fixes

Report a vulnerability privately, as [Security overview](https://docs.stackra.figentra.com/customers/security.md#reporting-a-vulnerability) says. Our
policy acknowledges a report within three business days (`SECURITY.md`). A fix ships as a new version; there is no
in-place patch of a published version.

## Support terms

> [!WARNING]
>
> **Owner to supply (STA-1576, STA-1574).** Nothing below is decided yet; until it is, there is no
> service level.

| Term | Value |
| - | - |
| Support channels (where to ask, by plan) | *owner to supply* |
| Response times by severity | *owner to supply* |
| Which versions receive fixes (support window) | *owner to supply* |
| End-of-life dates per release line | *owner to supply* |
| Long-term support | starts at the first on-prem contract (0177 decision 6); terms *owner to supply* |
| Uptime of the registry and status page | *owner to supply* (status page: STA-1574) |
| Single-tenant restore as a support operation, by plan | *owner to supply* ([0353](https://docs.stackra.figentra.com/adr/0353-data-residency-a-region-fixed-at-sign-up-a-login-directory-that-only-routes-and-copies-within-a-jurisdiction.md) decision 8 leaves it to the product) |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.