Skip to content
DataRecs Docs

Changelog & Versioning Policy

Versioning policy

Section titled “Versioning policy”
  • REST API — the API has no version path prefix (there is no /v1). Backwards-incompatible changes will be introduced via content negotiation or a new endpoint, never by silently changing an existing endpoint’s behavior. Additive changes (new optional fields, new endpoints) can ship at any time.
  • CLI (@datarecs/cli) — follows semantic versioning. npm install -g @datarecs/cli always gets the latest release; pin a version in CI if you need reproducible behavior.
  • Terraform provider — not yet published to the registry (see Terraform Provider for the current dev_overrides install path). Once published, it will follow semantic versioning and standard Terraform provider upgrade practices.

Deprecation policy

Section titled “Deprecation policy”

We aim to give advance notice before removing or changing the behavior of a documented API, CLI command, or Terraform resource/attribute that customers depend on. Until a formal deprecation-window policy is published here, treat any deprecation notice from support or account communications as authoritative.

Changelog

Section titled “Changelog”

No entries yet — this page will list customer-facing changes as they ship.

Next steps

Section titled “Next steps”
  • Support — how to reach us with questions or to report an issue.