versioned-install-data-dir-outside-releases
When using a versioned release layout (releases/<version>/ with a current/ symlink), the data directory must live outside releases/ at the install root level — not inside any specific version folder. Data inside releases/<version>/data/ is destroyed on every upgrade. This pattern applies to any stateful tool (xint, MCP servers, etc.) using symlink-based versioning.
Related
- xint-requires-bun-runtime-not-node
- docker
- trigger-dev-self-hosted-preferred-over-cloud-for-claude-code
- salesforce
- claude-code-as-ops-team-changes-aws-architecture-decision
- xint-data-directory-must-survive-version-upgrades
- xint-data-dir-must-be-outside-releases
- xint-versioned-install-with-symlink-pattern
- xint-data-dir-writes-to-release-internal-by-default
- versioned-release-installs-require-external-data-dir
- xint-runtime-data-dir-symlink-required
- xint-runtime-data-writes-to-release-internal-dir-by-default
- xint-installation-layout-with-versioned-releases-and-persist
- xint-installation-layout-versioned-releases-with-symlink
- xint-versioned-install-layout-pattern