Environments and releases

Environments and releases provide delivery context for quality, issues, and agents.

Environments

An environment is a named target such as:

• staging
• production
• preview-pr-128

Environment fields:

Field	Purpose
Name	Human-readable name
Slug	Stable identifier used by API and CLI
Host	Target URL or hostname
Type	static or dynamic
Origin	manual or auto

Releases

A release is a product version record. Releases are usually created by CI/CD, the CLI, or the REST API.

tiden release create \
  --product-id <product-id> \
  --version my-app@1.2.3 \
  --environment production \
  --url https://github.com/acme/app/releases/tag/v1.2.3

Release creation is idempotent for a product, version, and environment. Sending the same release again updates the existing record.

--build-sha (buildSha in the REST API) names the full commit SHA the release was built from. The release's Quality Gate is then captured from the test results reported for that commit; see Release captures.

--released-at (releasedAt in the REST API) is optional and takes an RFC 3339 timestamp. When you omit it, the release time is the time of the announce.

Announce each deploy from CI so Tiden records releases that ship without errors and captures each release's Quality Gate. See Announce releases for the rules and a GitHub Actions step.

Auto-created environments

If release creation references an unknown environment slug, Tiden can create an auto-origin environment for that slug. You can later enrich it with a name, host, and description.

Release detail

The release detail page connects version context to issues and quality gate state. Use the same release string in your telemetry SDK so runtime errors can be attributed to the release.