atmos describe edition
Use this command to show whether the project is pinned to an edition (a date anchor for defaults), where the pin came from, the resolved anchor date, and every default the pin keeps at its pre-change value.
Learn how to pin your project's defaults to a date anchor with the top-level edition setting in your atmos.yaml.
Usage
atmos describe edition [flags]
Description
The atmos describe edition command reports the effect of the active edition pin:
- pinned — whether an edition is set at all
- edition — the raw pin as you wrote it (e.g.
2025-09) - resolved_date — the fully resolved anchor date (partial dates round to the end of the period they name)
- granularity — how much of the date the pin specified:
year,month, orday - source — where the pin came from:
flag(--edition),env(ATMOS_EDITION), orconfig(atmos.yaml) - overrides — every default the pin rolls back, with the pinned (effective) value, the latest default you would get by unpinning, and the journal entries behind the change
Without a pin, it reports pinned: false with no overrides — the project follows the latest defaults.
Flags
--format, -f string- Output format:
yamlorjson(default:yaml)
Examples
Show the active pin and its effect:
atmos describe edition
Output as JSON:
atmos describe edition --format=json
Preview the effect of a pin without changing your configuration, using the --edition global flag:
atmos --edition=2026-01 describe edition
Example Output
In each override, from_value is the default your pinned project actually uses, and to_value is the latest default the project would get by unpinning.
Use atmos list editions to browse the full journal of default changes, or to diff two editions with --from and --to.
See Also
editionconfiguration — Pin your project's defaults to a date anchoratmos list editions— Browse the journal of default changes, or diff two editions