NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1414 by repository stars
Latest stable
v1.234.0
Last release 10 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Some releases are documented
notes for 32 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
2417 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
test: Improve coverage for mock AWS auth provider credential and identity flows @Copilot
<details>
<summary>test: Improve coverage for mock AWS auth provider credential and identity flows @Copilot (#2511)</summary>
</details>
<details>
<summary>feat(cli): add discovery metadata for core commands @osterman (#3466)</summary>
</details>
<details>
<summary>feat(cli): add discovery metadata for supporting commands @osterman (#3467)</summary>
</details>
<details>
<summary>docs: demonstrate CI failure annotations locally @osterman (#3472)</summary>
</details>
<details>
<summary>fix(ci): stabilize quality reporting and CI dependencies @osterman (#3476)</summary>
</details>
<details>
<summary>Add runnable CDK examples with casts for the CDK tutorial @osterman (#3481)</summary>
examples/cdk-cloudformation and examples/cdk-terraform applications that use the native CloudFormation and Terraform components against the local Floci AWS emulator, with lifecycle casts, smoke checks, and CDK tutorial links.</details>
<details>
<summary>chore(review): encourage extracting legacy catch-all packages @osterman (#3521)</summary>
internal/exec and pkg/utils to be extracted into owning packages, using thin adapters where needed.</details>
<details>
<summary>chore: bump Claude Code plugin version to v1.233.2 @cloudposse-releaser[bot] (#3528)</summary>
v1.233.2.</details>
<details>
<summary>fix(release): recognize landed native stack members @osterman (#3536)</summary>
</details>
<details>
<summary>fix(ci): re-check quality:ready PRs whose head status fails @osterman (#3539)</summary>
quality:ready pull requests whose head commit has a combined status of failure or error, even when the report is current and the commit is more than 24 hours old. It does not select quality:not-ready pull requests or combined pending statuses.website/ pnpm overrides for dompurify, follow-redirects, and launch-editor to patched releases and regenerate pnpm-lock.yaml.</details>
<details>
<summary>feat(policy): add validation engines and shared runtime context @osterman (#3461)</summary>
</details>
<details>
<summary>fix(yaml): require explicit function tags with edition compatibility @osterman (#3463)</summary>
2026-10-20 now require explicit YAML function tags, preserving tag identity through loading, merging, templates, deferred evaluation, and serialization. edition: "2026-10-19", condition shorthand, and explicit evaluation APIs retain legacy behavior, while quoted !env, !exec, and !unset values remain literal.</details>
<details>
<summary>feat(cli): add --docs and --example command discovery @osterman (#3468)</summary>
--docs, --docs=md (also --docs=markdown), and --example: help and usage errors show documentation URLs, --docs can open or render them, and --example selects and initializes runnable examples with installation and overwrite confirmations. Discovery works before normal project validation, preserves aliases, --chdir, custom flag ownership, and initialization behavior, and generates linked documentation indexes from resolved navigation.</details>
<details>
<summary>Add Fogg migration and CDK guides with CloudFormation improvements @osterman (#3471)</summary>
region and duration-based timeout settings are supported, with Doctor migrations enforcing legacy minute values.</details>
<details>
<summary>feat(starlark): add modules, records, and typed configuration @osterman (#3505)</summary>
module.load(path) and struct(**fields) to automation scripts, with cached imports, frozen exports, cycle detection, cancellation, and parallel loading.stdlib/config, supporting inline or local/HTTPS JSON Schemas, defaults, bounds, optional fields, lists, enums, immutable dot-access records, source diagnostics, and config1.merge(config2) with configurable list strategies.</details>
<details>
<summary>feat(yaml): support bounded parallel exec evaluation @osterman (#3527)</summary>
settings.functions.exec.max_concurrency to bound concurrent evaluation of ordinary !exec expressions; the default 1 preserves serial evaluation. Results remain in their original positions, outstanding commands are canceled after failure, function policy is checked before launch, and --skip=exec behavior is unchanged.</details>
<details>
<summary>fix(terraform): run lifecycle hooks in prepared workdirs @osterman (#3462)</summary>
init and test runs, executing them in prepared workdirs while preserving resolved paths and credentials for after-hooks. Test fixtures can start before authentication without being overwritten, and tool-version discovery is scoped to each project's configuration.</details>
<details>
<summary>fix: preserve Helm repository auth and AWS ambient context @osterman (#3470)</summary>
AWS_PROFILE, and explicit managed credential overrides.</details>
<details>
<summary>fix(stacks): resolve inherited metadata.component directories @osterman (#3508)</summary>
metadata.component values before backend generation while preserving explicit overrides, legacy component selection, and disabled metadata inheritance. This keeps execution directories aligned with inherited component metadata.</details>
<details>
<summary>fix(terraform): run tests without generating a backend @osterman (#3514)</summary>
auto_generate_backend_file is enabled, avoiding the backend_type is required error for provider-free test modules and preserving existing backend files.</details>
<details>
<summary>fix(secret): allow stack secrets without a component @osterman (#3517)</summary>
secret set NAME=value -s <stack> and secret validate -s <stack> to operate on stack-scoped declarations without an unrelated component, while retaining the component requirement for instance-scoped operations.</details>
<details>
<summary>feat(duration): human-readable minutes/hours in resource-usage summary @osterman (#3529)</summary>
duration.Format in pkg/duration and use it for local resource summaries and Native CI Terraform summaries. Durations of at least a minute now render as combinations such as 34m 47s or 1h 2m 3s, while sub-minute values retain their existing format and boundary rounding avoids displaying 60.0s.</details>
<details>
<summary>chore(deps): bump github.com/posthog/posthog-go from 1.12.6 to 1.17.4 @dependabot[bot] (#2764)</summary>
github.com/posthog/posthog-go from 1.12.6 to 1.17.4.</details>
<details>
<summary>build(deps): bump al.essio.dev/pkg/shellescape from 1.6.0 to 1.6.1 @dependabot[bot] (#3425)</summary>
al.essio.dev/pkg/shellescape from 1.6.0 to 1.6.1.</details>
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
…reports credential diagnostics, and avoids deprecated token inputs.
<details>
<summary>chore(ci): raise patch coverage target to 90%; fix PTY resize race @osterman (#3441)</summary>
os.Stdin is reassigned.</details>
<details>
<summary>chore: bump Claude Code plugin version to v1.233.0 @cloudposse-releaser[bot] (#3444)</summary>
v1.233.0.</details>
<details>
<summary>Add runnable examples to command documentation @osterman (#3448)</summary>
</details>
<details>
<summary>fix(ci): repair benchmark provenance and failed license scans @osterman (#3451)</summary>
main branch instead of GitHub's cached pull-request base SHA, preserving merge-parent and artifact provenance checks.NOTICE unchanged, while successful empty scans and usable partial reports retain their existing behavior.</details>
<details>
<summary>ci: unify runner hardening, DNS repair, and shared allowlists @osterman (#3493)</summary>
.github/allowlist.yaml provides reusable, validated, deduplicated endpoint policies with OS-specific background-service and update rules; the action loads policies from its pinned repository revision without checkout or runtime npm installation.</details>
<details>
<summary>fix(release): improve feedback and reserve sequential RC tags @osterman (#3500)</summary>
</details>
<details>
<summary>Fix repository metadata URLs in release milestone checks @osterman (#3501)</summary>
repos/<owner>/<repo> without a trailing slash, while nested resource and query URLs remain unchanged. This fixes the default-branch lookup used by Release milestones / enforce, which previously received HTTP 404 from GitHub.</details>
<details>
<summary>ci: bump scorecard-action to v2.5.0 for $/ action support @osterman (#3503)</summary>
ossf/scorecard-action from v2.4.4 to v2.5.0, pinned by full commit SHA, so Scorecard recognizes same-repository uses: $/.github/actions/... references and no longer recreates the related false-positive pinned-dependency alerts.</details>
<details>
<summary>fix(release): validate action inputs and show live RC progress @osterman (#3504)</summary>
gh run watch --exit-status, retain final API verification, identify RC requests explicitly, and show live release progress.</details>
<details>
<summary>fix(release): restore attestations and notes, warm release caches @osterman (#3506)</summary>
</details>
<details>
<summary>Make documentation examples easy to try @osterman (#3447)</summary>
TryExample component, with shared Install Atmos and named example tabs such as Dev Container and Build Geodesic.atmos policy check now defaults to terminal-friendly text; use --format text|json or ATMOS_POLICY_CHECK_FORMAT to select output. JSON remains available with its existing fields on stdout, while the default summary is written to stderr.</details>
<details>
<summary>fix: <code>!terraform.state</code> honors <code>remote_state_backend</code> (read-only role) @aknysh (#3450)</summary>
!terraform.state now reads a component's remote_state_backend and remote_state_backend_type when configured, including read-only role and sse_customer_key overrides, and falls back to backend and backend_type otherwise. The change affects in-process state reads only; terraform plan and terraform apply are unchanged.</details>
<details>
<summary>fix: enforce milestone releases and verified artifact publication @osterman (#3474)</summary>
atmos release check, atmos release cut, and atmos release candidate; the next milestone defines the version, local confirmation binds the commit SHA, and GitHub Actions owns tagging and publication.</details>
chore(ci): raise patch coverage target to 90%; fix PTY resize race @osterman
<details>
<summary>chore(ci): raise patch coverage target to 90%; fix PTY resize race @osterman (#3441)</summary>
os.Stdin changes.</details>
<details>
<summary>chore: bump Claude Code plugin version to v1.233.0 @cloudposse-releaser[bot] (#3444)</summary>
</details>
<details>
<summary>Add runnable examples to command documentation @osterman (#3448)</summary>
</details>
<details>
<summary>fix(ci): repair benchmark provenance and failed license scans @osterman (#3451)</summary>
main branch rather than GitHub’s cached PR base SHA, preserving merge-parent and artifact provenance checks.NOTICE unchanged on failure while preserving successful empty and usable partial reports.</details>
<details>
<summary>ci: unify runner hardening, DNS repair, and shared allowlists @osterman (#3493)</summary>
.github/allowlist.yaml across block-mode jobs. The downloaded action repository supplies validated policies and diagnostics without checkout or runtime npm installation, while recovery preserves resolver state, Docker DNS, firewall rules, and final reporting.</details>
<details>
<summary>fix(release): improve feedback and reserve sequential RC tags @osterman (#3500)</summary>
</details>
<details>
<summary>Fix repository metadata URLs in release milestone checks @osterman (#3501)</summary>
repos/<owner>/<repo> without a trailing slash, while nested resource and query URLs remain unchanged. This fixes the default-branch lookup used by atmos release milestone enforcement.</details>
<details>
<summary>ci: bump scorecard-action to v2.5.0 for $/ action support @osterman (#3503)</summary>
ossf/scorecard-action from v2.4.4 to v2.5.0, pinned by full commit SHA, so Scorecard recognizes same-repository uses: $/.github/actions/... references and stops reporting them as false-positive pinned-dependency alerts.</details>
<details>
<summary>fix(release): validate action inputs and show live RC progress @osterman (#3504)</summary>
gh run watch --exit-status, and identify RC requests explicitly.</details>
<details>
<summary>fix(release): restore attestations and notes, warm release caches @osterman (#3506)</summary>
</details>
<details>
<summary>Make documentation examples easy to try @osterman (#3447)</summary>
TryExample component with copyable setup commands, shared Install Atmos tabs, named example tabs, and runnable quick starts for changelog posts and example pages.atmos policy check defaults to terminal-friendly text and supports explicit --format text|json or ATMOS_POLICY_CHECK_FORMAT.--format json; JSON remains on stdout and the default text summary is written to stderr.</details>
<details>
<summary>fix: <code>!terraform.state</code> honors <code>remote_state_backend</code> (read-only role) @aknysh (#3450)</summary>
!terraform.state now reads through a component’s remote_state_backend and remote_state_backend_type when configured, falling back to backend and backend_type otherwise. This supports read-only remote-state credentials, including sse_customer_key, without changing terraform plan or terraform apply.</details>
<details>
<summary>fix: enforce milestone releases and verified artifact publication @osterman (#3474)</summary>
atmos release check/cut/candidate; milestone versioning, local SHA confirmation, label compatibility, milestone ordering, and release summaries are now enforced through Mage operations and the quality gate.</details>
{"repository":"cloudposse/atmos","version":"v1.233.2","run_id":"40095233031","commit":"f1c31395fb8e5762ea247075a4e35e30b9ec9d93"}
{"repository":"cloudposse/atmos","version":"v1.233.2","run_id":"40095233031","commit":"f1c31395fb8e5762ea247075a4e35e30b9ec9d93"}
{"repository":"cloudposse/atmos","version":"v1.233.2","run_id":"40041249948","commit":"f1c31395fb8e5762ea247075a4e35e30b9ec9d93"}
{"repository":"cloudposse/atmos","version":"v1.233.2","run_id":"40041249948","commit":"f1c31395fb8e5762ea247075a4e35e30b9ec9d93"}
fix(release): validate action inputs and show live RC progress
fix(release): validate action inputs and show live RC progress
fix(ci): install native dependencies before release contract tests
fix(release): reject unsupported watcher credentials before dispatch
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Co-authored-by: cloudposse-releaser[bot] <163353533+cloudposse-releaser[bot]@users.noreply.github.com>
Co-authored-by: cloudposse-releaser[bot] <163353533+cloudposse-releaser[bot]@users.noreply.github.com>
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Updated AI configuration, usage, and troubleshooting guidance. Legacy permission booleans remain supported as deprecated aliases.
<details>
<summary>fix(ci): stop quality gate flipping to not-ready in merge queue @osterman (#3439)</summary>
</details>
<details>
<summary>fix(website): support deep links to example chapters @osterman (#3435)</summary>
</details>
<details>
<summary>docs(skills): document native PR stack repair and review @osterman (#3399)</summary>
</details>
<details>
<summary>docs: propose explicit teardown for deleted components @osterman (#3415)</summary>
</details>
<details>
<summary>docs: simplify CloudFormation YAML examples @osterman (#3411)</summary>
aws/cloudformation YAML key without quotes. Both quoted and unquoted forms remain valid, with the unquoted form preferred.</details>
<details>
<summary>docs: clarify toolchain locks and secrets demo masking @osterman (#3428)</summary>
.tool-versions.</details>
<details>
<summary>docs: clarify component data sharing and lifecycle workflows @osterman (#3414)</summary>
terraform destroy --affected and filtering with --query.!secret.</details>
<details>
<summary>docs: refresh homepage casts and Atmos adoption guidance @osterman (#3409)</summary>
</details>
<details>
<summary>docs: clarify custom components and Starlark implementations @osterman (#3419)</summary>
example component type.example component.atmos example deploy-app --stack dev.</details>
<details>
<summary>fix: report quality gates for stacked pull requests @osterman (#3421)</summary>
</details>
<details>
<summary>fix(ci): quality gate for fork PRs; add draft and conflict gates @osterman (#3398)</summary>
owner:branch when commits/{sha}/pulls returns nothing (shared githubapi.OpenPRsForHead helper, reused by the existing event selector).!pr.Draft override and draft footer/guidance) and No merge conflicts (mergeable=false or dirty; an uncomputed mergeable is treated as unavailable evidence so the published report is kept and retried).magefiles/README.md gate list and a docs/fixes record.</details>
<details>
<summary>Refresh generated CLI recordings after feature graduation @osterman (#3393)</summary>
gcp, sbom, and store.auth login --webflow option.</details>
<details>
<summary>fix(ci): stop auto-updating Dependabot/Renovate PRs behind main @austenstone (#3366)</summary>
</details>
<details>
<summary>feat(cloudformation): generation workdirs, sources, and downloader (split from #3251) @osterman (#3324)</summary>
</details>
<details>
<summary>docs(cloudformation): add native aws/cloudformation component PRD @osterman (#2997)</summary>
</details>
<details>
<summary>docs(cloudformation): phase 1 docs, examples, and fix-log (split from #2999) @osterman (#3156)</summary>
</details>
<details>
<summary>feat(cloudformation): core lifecycle verbs (split from #2999) @osterman (#3157)</summary>
</details>
<details>
<summary>docs(cloudformation): phase 1 docs and examples (split from #3157) @osterman (#3322)</summary>
</details>
<details>
<summary>feat(cloudformation): add changesets, drift detection, fmt/list/source verbs [EXPERIMENTAL] @osterman (#3000)</summary>
!aws.cloudformation.output to reference deployed stack outputs in configuration.</details>
<details>
<summary>feat(cloudformation): add stack sets, tree/logs/watch, and backend management [EXPERIMENTAL] @osterman (#3001)</summary>
</details>
<details>
<summary>docs(cloudformation): phase 4 docs, screengrabs, examples, and fix-log @osterman (#3136)</summary>
--stack.</details>
<details>
<summary>feat(cloudformation): migration guide, inline templates, and field-test fixes [EXPERIMENTAL] @osterman (#3137)</summary>
--labels filters across commands.</details>
<details>
<summary>docs(cloudformation): phase 4 docs, examples, and skills (split from #3137) @osterman (#3323)</summary>
</details>
<details>
<summary>feat(cloudformation): stack_policy.body and account-safe outputs @osterman (#3251)</summary>
--force is needed.</details>
<details>
<summary>Add branded per-page social cards to the website @osterman (#3388)</summary>
</details>
<details>
<summary>Add reusable edition behavior gates @osterman (#3377)</summary>
</details>
<details>
<summary>fix(ci): publish quality gate for fork PRs; fix self-feeding reconciler @osterman (#3383)</summary>
</details>
<details>
<summary>fix(ci): tap homebrew/core with --force in release bump @aknysh (#3370)</summary>
homebrew/core with Homebrew 7.x, preventing the release step from failing.</details>
<details>
<summary>docs: align CI and automation guides with field-test fixes @osterman (#3337)</summary>
</details>
<details>
<summary>docs: clarify Scripting guides and migrate URLs @osterman (#3321)</summary>
</details>
<details>
<summary>Add the embedded Starlark runtime and command APIs @osterman (#3264)</summary>
</details>
<details>
<summary>docs: add Automation Functions and language references @osterman (#3274)</summary>
errors.build helper for reporting script failures with structured details.</details>
<details>
<summary>docs: align automation guides and add CLI acceptance cases @osterman (#3296)</summary>
</details>
<details>
<summary>fix(ci): share CI reporting workflow and limit recovery scans @osterman (#3376)</summary>
main updated within the past 24 hours; manual checks cover all open pull requests to main.</details>
<details>
<summary>chore: bump Claude Code plugin version to v1.232.0 @<a href="https://github.com/apps/cloudposse-releaser">cloudposse-releaser[bot]</a> (#3369)</summary>
</details>
<details>
<summary>fix(ci): quiet Quality Gate comment; skip CodeRabbit gate for bot PRs @osterman (#3375)</summary>
<details> block, like "All other benchmarks". The headline and per-snapshot warning lines stay visible above it.github.com/cloudposse/atmos/ module prefix from benchmark metric names. Rows now read tests/benchmarks/CLI/DescribeAffected/... (sec/op).user.type == "Bot"): Renovate, Dependabot, the github-actions token, cloudposse-releaser[bot]. Evidence reads "Not required: PR opened by automation (<login>)".cloudposse-releaser[bot]).</details>
<details>
<summary>fix(templates): honor configured delimiters in step templates @osterman (#3436)</summary>
{{ }} for step templates.</details>
<details>
<summary>feat(templates): add gomplate experimental mode option @hashfunc (#3412)</summary>
experimental Gomplate setting for enabling experimental template functions, such as net.CIDRHost. It defaults to off and can be configured globally or overridden per stack. Stacks inherit the global value when no override is set.</details>
<details>
<summary>feat(config): CLI-config import DX — optional/required, conditional loading, optional MCP servers @aknysh (#3433)</summary>
skip_if_missing: true warns and skips failures, while legacy string imports remain optional.</details>
<details>
<summary>feat: add CEL policy engine, plan gates, and native CI hooks @osterman (#3371)</summary>
--from-plan support for applying saved Terraform plans.</details>
<details>
<summary>feat: add policy selectors, affected gates, Starlark, and library @osterman (#3384)</summary>
policy.d/ by default, with ATMOS_POLICY_DIR available to override the location.</details>
<details>
<summary>feat: enforce policy admission, source security, and GitHub approvals @osterman (#3365)</summary>
ci context to view CI data or field paths without exposing values.--explain to show policy decisions and evaluation details on stderr.</details>
<details>
<summary>feat: add policy library explorer and usage guides @osterman (#3387)</summary>
</details>
<details>
<summary>feat(ci): annotate failed commands and policy denials @osterman (#3403)</summary>
</details>
<details>
<summary>feat: control cast playback duration and preserve Unicode @osterman (#3418)</summary>
</details>
<details>
<summary>feat(auth): AWS credential_process support (atmos as helper + helper identity) @osterman (#3249)</summary>
credential_process format for CLI profiles and SDK-based tools.atmos auth user configure now supports selecting an AWS user identity directly and uses the configured credential store.</details>
<details>
<summary>Add declarative skills and unified AI tool approvals @osterman (#3352)</summary>
ai ask.chat, ask, and exec, with clearer approval choices and unattended-run policies.</details>
<details>
<summary>Add cached CI review labels and boolean label selectors @osterman (#3395)</summary>
!ci.labels YAML function to return sorted review labels or check whether all specified labels match exactly and case-sensitively. Supports GitHub Actions and GitHub Enterprise, including merge-queue pull requests.preview: true, for filtering components and stacks.</details>
<details>
<summary>feat(git): publish GitOps target deliveries through pull requests @bonddim (#3355)</summary>
</details>
<details>
<summary>feat(ai): interactive atmos ai ask with approvals, choices, follow-ups @osterman (#3350)</summary>
atmos ai ask supports interactive tool approvals, AI-directed questions, progress updates, and terminal follow-up prompts.ai.tools.mode: require_confirmation prompts for approval, allow skips prompts while honoring blocked tools, and yolo bypasses permission checks.</details>
<details>
<summary>feat(docs): support native Terraform objects in README templates @osterman (#3404)</summary>
</details>
<details>
<summary>Graduate mature Atmos features with evidence and documentation @osterman (#3390)</summary>
ci.enabled. Newer Auth providers and integrations may have less production history.</details>
<details>
<summary>docs(cloudformation): generation workdirs docs, casts, and skills (split from #3251) @osterman (#3325)</summary>
</details>
<details>
<summary>feat(steps): publish artifacts to S3 and Git targets @osterman (#3290)</summary>
publish step for sending local files and directories to S3 or Git, using named or inline targets. Results report changed and unchanged files, and dry runs validate configuration without publishing.</details>
<details>
<summary>feat(cloudformation): Rain migration parity, include eval, short-form intrinsics @osterman (#3317)</summary>
--skip-hooks.!include supports opt-in function evaluation with | eval, while preserving CloudFormation intrinsic tags; short-form intrinsics are supported in inline templates.!env variables without defaults resolve to an empty string and log a warning.tree shows deployed nested-stack hierarchies.</details>
<details>
<summary>feat(cloudformation): native CI and field-tested lifecycle hardening @osterman (#3100)</summary>
</details>
<details>
<summary>feat(ci): per-store identity for planfile storage @aknysh (#3401)</summary>
</details>
<details>
<summary>feat(ci): fork-aware gate, report templates, container image comments @osterman (#3308)</summary>
</details>
<details>
<summary>fix(ci): fork gate from the event payload, commit comments, container comment hygiene @osterman (#3318)</summary>
</details>
<details>
<summary>fix(automation): wire the ci module into every host and harden script inputs @osterman (#3319)</summary>
atmos.tf alias and improved standalone script discovery, including case-insensitive extensions and more flexible shebangs.--chdir is used. Ctrl-C runs deferred cleanup, and help exits before later script actions.</details>
<details>
<summary>Introduce Atmos Automation Language across commands and hooks @osterman (#3266)</summary>
</details>
<details>
<summary>Add declarative script interfaces and automation documentation @osterman (#3261)</summary>
</details>
<details>
<summary>feat(steps): !literal step fields and reliable custom-command inputs @osterman (#3275)</summary>
!literal support for step fields and declared environment values, allowing template-like text to pass through unchanged.</details>
<details>
<summary>Expose automation steps, decoded query results, and execution controls @osterman (#3278)</summary>
data.config get, stack config get, and stack get support --format/-f with raw and json output.</details>
<details>
<summary>Run embedded Starlark steps in Git hooks @osterman (#3283)</summary>
</details>
<details>
<summary>feat: compute stack values with !starlark @osterman (#3286)</summary>
!starlark expressions in stack manifests to compute typed configuration from merged component context. Expressions can reference other computed values, with dependency cycles reported as errors.</details>
<details>
<summary>fix: harden automation inputs, steps, hooks, and stack values @osterman (#3295)</summary>
</details>
<details>
<summary>feat(automation): ci module for reporting from scripts @osterman (#3307)</summary>
</details>
<details>
<summary>fix: support oci:// in !include via a shared OCI getter; fix git:: token injection @jorrite (#3381)</summary>
!include and !include.raw, allowing files to be selected from within an artifact.</details>
<details>
<summary>Fix prompt masking, script output, and component lookup errors @osterman (#3434)</summary>
</details>
<details>
<summary>feat(auth): cap Azure PIM activation duration at role policy maximum @AdamMagued (#3253)</summary>
</details>
<details>
<summary>fix(archive): resolve linked git worktrees for mtime git/epoch @arcaven (#2824)</summary>
</details>
<details>
<summary>fix(doctor): field-test fixes for dispatch, dependency repairs, and checks @osterman (#3392)</summary>
atmos doctor now reports dependency issues with clearer locations and verifies that dependency repairs preserve effective dependencies, including inherited ones.depends_on declarations and can migrate them when effective dependencies remain unchanged.--affected guidance is clearer, and interrupted runs provide a summary.</details>
<details>
<summary>fix: add regression testing and restore upgrade compatibility @osterman (#3405)</summary>
--labels values now preserve literal quotes and are parsed consistently across commands and configuration sources.PATH settings.eval text no longer triggers command execution.</details>
<details>
<summary>Shared foundations for atmos doctor: resolvers, precedence, affected @osterman (#3373)</summary>
</details>
<details>
<summary>fix(stacks): let !unset remove a whole component section @theluckystrike (#3289)</summary>
!unset to remove values from applicable lower-priority configuration layers. This works with base components and overrides, while higher-priority values remain in effect.</details>
<details>
<summary>fix(auth): honor --kubeconfig/--alias and expand ~/env in update-kubeconfig --integration @aknysh (#3394)</summary>
update-kubeconfig commands now apply --kubeconfig and --alias overrides with --integration; empty overrides preserve the integration’s configured values.~ and environment variables. Paths containing an unset environment variable return an error.</details>
<details>
<summary>Fix delivery workflow regressions before feature graduation @osterman (#3389)</summary>
</details>
<details>
<summary>fix: surface helm/kubernetes components in describe/list/dependents wiring @osterman (#2998)</summary>
</details>
<details>
<summary>fix(cloudformation): harden lifecycle, outputs, and delivery @osterman (#3250)</summary>
</details>
<details>
<summary>fix: enforce planfile verification in multi-component deploy @tokanize (#3397)</summary>
</details>
<details>
<summary>fix: restore describe lookup caches and reduce resolution overhead @osterman (#3380)</summary>
</details>
<details>
<summary>fix(steps): validate step fields, honor retry conditions, end whole process trees @osterman (#3320)</summary>
config get, stack get, and stack config get support command-specific format environment variables; an explicit --format flag takes precedence.!starlark tags in atmos.yaml now produce an error.</details>
<details>
<summary>fix(starlark): standalone scripts behave like real CLIs @osterman (#3276)</summary>
--chdir, and version-pinned reruns while forwarding script arguments correctly.None to top-level output produces no standalone output; None inside lists or dictionaries remains JSON null..star paths from other paths and directories.</details>
<details>
<summary>fix: clean up child processes when automation is canceled @osterman (#3294)</summary>
</details>
<details>
<summary>feat(ci): Reporter seam, local-parity generic provider, GitHub fake API @osterman (#3298)</summary>
</details>
<details>
<summary>Prepare shared execution services for Starlark @osterman (#3263)</summary>
commands: !unset.</details>
<details>
<summary>chore(deps): update cloudposse/github-action-docker-build-push action to v3.2.2 @<a href="https://github.com/apps/renovate">renovate[bot]</a> (#3417)</summary>
v3.2.1 → v3.2.2 |v3.2.2</details>
<details>
<summary>chore(deps): update anchore/sbom-action action to v0.24.3 @<a href="https://github.com/apps/renovate">renovate[bot]</a> (#3416)</summary>
v0.24.2 → v0.24.3 |v0.24.3</details>
<details>
<summary>chore(deps): update terraform http to v3.6.2 @<a href="https://github.com/apps/renovate">renovate[bot]</a> (#3128)</summary>
3.6.1 → 3.6.2 |v3.6.2</details>
<details>
<summary>build(deps): bump github.com/aws/aws-sdk-go-v2 from 1.45.1 to 1.47.1 @<a href="https://github.com/apps/dependabot">dependabot[bot]</a> (#3358)</summary>
</details>
<details>
<summary>chore(deps): update dependency @types/node to v22.20.4 @<a href="https://github.com/apps/renovate">renovate[bot]</a> (#3340)</summary>
22.20.2 → 22.20.4 | | |</details>
<details>
<summary>build(deps): bump golang.org/x/tools from 0.50.0 to 0.51.0 in /tools/lintroller @<a href="https://github.com/apps/dependabot">dependabot[bot]</a> (#3406)</summary>
</details>
<details>
<summary>build(deps): bump the website group in /website with 3 updates @<a href="https://github.com/apps/dependabot">dependabot[bot]</a> (#3407)</summary>
docusaurus-plugin-llms from 0.5.1 to 0.6.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rachfop/docusaurus-plugin-llms/releases">docusaurus-plugin-llms's releases</a>.</em></p> <blockquote> <h2>v0.6.1</h2> <p>This release fixes how links, Markdown file paths, and content are generated for versioned, translated, and multi-section sites, and adds lint and format checks to the repo. Docs are at <a href="https://rachfop.github.io/docusaurus-plugin-llms">https://rachfop.github.io/docusaurus-plugin-llms</a>.</p> <h3>Added</h3> <ul> <li><code>versions[].routePrefix</code>, for explicit versions served inside the route base path (<code>/docs/<version>/</code>) (<a href="https://redirect.github.com/rachfop/docusaurus-plugin-llms/issues/88">#88</a>).</li> </ul> <h3>Changed</h3> <ul> <li><code>versions: 'auto'</code> follows Docusaurus versioning: the last version writes the root files, the current d…</details>
Co-authored-by: cloudposse-releaser[bot] <163353533+cloudposse-releaser[bot]@users.noreply.github.com>
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Add branded per-page social cards to the website @osterman
<details> <summary>Add branded per-page social cards to the website @osterman (#3388)</summary>
Generate a 1200×630 PNG fallback and per-page JPEG social cards, wire generation and tests into the website lifecycle, and update Open Graph/Twitter metadata regardless of attribute order.
Use official Atmos and Atmos CI gradient lockups, bundled Geist fonts, measured text wrapping, a darker background, versioned image URLs, safe section-label lookups, and yielding between renders to release native memory.
Pin website preview and production builds to setup-go v6.5.0 to use the Node.js 24 action runtime.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
</details>
<details> <summary>Add reusable edition behavior gates @osterman (#3377)</summary>
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>fix(ci): publish quality gate for fork PRs; fix self-feeding reconciler @osterman (#3383)</summary>
.github/actions/stopwatch) and the quality report (magefiles/qualitygate) resolve a fork run's PR by head owner:branch (plus a SHA search for check_run/status events) when workflow_run.pull_requests and commits/{sha}/pulls are empty. The head SHA is still re-verified against the PR before anything is published.updated_at.quality-report was skipped.updated_at is advanced by the gate's own labels/comments and by Mergify/Codecov/CodeRabbit, so 163 of 165 open PRs were selected although only 11 had a commit in the last 24h. The run hit its 25-minute timeout, logged context deadline exceeded for dozens of PRs, and never reached the later ones.quality:ready and quality:not-ready swapped every 2-3 minutes between 01:34 and 01:47. The inputs were static and the run logs had swallowed the error, so the root cause is not proven; unavailable gates are now logged and no longer overwrite a same-head report.pull_request_review_thread triggers to quality-signal.yml, since the schedule no longer sees thread resolutions on old PRs with no new commit.quality-report.yml and confirm #3381 gets its comment and label.🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>fix(ci): tap homebrew/core with --force in release bump @aknysh (#3370)</summary>
.github/workflows/build.yml from brew tap homebrew/core to brew tap homebrew/core --force.The Homebrew preinstalled on ubuntu-latest was upgraded to the 7.0.x line, which now refuses a plain brew tap homebrew/core:
Tapping homebrew/core is no longer typically necessary.
Add --force if you are sure you need it for contributing to Homebrew.
The step exits 1 on that line, before brew bump-formula-pr runs, so no Homebrew PR is opened on release. This failed the v1.232.0 release bump.
brew bump-formula-pr is a developer command that edits the formula .rb, so it genuinely needs homebrew/core checked out as a local tap (established across v1.228.0-v1.231.0: without the tap it fails "No available formula with the name atmos"). We do need the tap for contributing, so --force is the path Homebrew's own error message points to.
This step only runs on release: published, so PR CI cannot exercise it - the next release is the first real confirmation.
docs/fixes/2026-09-28-homebrew-bump-brew-not-on-path.md, docs/fixes/2026-10-09-homebrew-bump-needs-core-tap.mddocs/fixes/2026-10-13-homebrew-bump-tap-core-force.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
homebrew/core with Homebrew 7.x, preventing the release step from failing.<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>feat(ci): fork-aware gate, report templates, container image comments @osterman (#3308)</summary>
Completes the remaining work for the ci automation module in one PR (no new YAML step types, per review):
ci.context.pr.fork is read from the GitHub event payload (pull_request.head.repo, and workflow_run.head_repository for workflow_run events) and from ATMOS_CI_PR_FORK on the generic provider. Under pull_request_target and workflow_run, comments and checks are now held only for fork pull requests; same-repository pull requests post normally. ci.allow_unsafe_fork_execution still overrides.ci.summary(template=, data=) and ci.comment(template=, data=) render a file under ci.templates.base_path with the same engine as the built-in plan summaries; ci.summary.template and ci.comments.template (declared in the schema but unread until now) are the defaults when a call passes only data. Backed by templates.RenderReport and Reporter.RenderSummary/RenderComment.atmos container build/push go through ci.Reporter: the job summary as before, plus one upserted pull request comment per image (keyed container:image:<image>) when ci.comments.enabled is on. The Markdown can be overridden with ci.templates.container.image; the embedded default is byte-identical to the previous renderer (golden tests).ci.*Enabled helpers instead of private copies; the generic provider reads ATMOS_CI_OUTPUT/ATMOS_CI_SUMMARY at call time; dead providers/github/loggroup.go removed.ci, ci.summary, ci.comment, ci.check reference pages, the CI templates/summary/comments configuration pages, the container component page, the environment variable table (ATMOS_CI_PR_FORK), the changelog post (new section), and the PRDs (script-ci-module.md, interfaces.md, generic.md, github/provider.md, new providers/container.md).These were the items left in the PRD's "Remaining implementation work" after #3307. Keeping them in the stack follows the repository rule that unmerged implementations are finished in their PR stack rather than tracked as issues. The fork refinement removes the one case where the previous gate blocked a legitimate workflow (base-checkout code commenting on a same-repository pull request under pull_request_target).
osterman/starlark-ci-module) → #3298 → #3296.🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
<details> <summary>fix(ci): fork gate from the event payload, commit comments, container comment hygiene @osterman (#3318)</summary>
Fixes from a field test of the native CI reporter (#3298) and the fork-aware gate, templates, and container comments in #3308.
pull_request_target and workflow_run now comes from the event payload (GITHUB_REF is the base branch there, so the headline same-repository case never posted). A fork is a head/base full_name mismatch; a deleted fork or unreadable payload is held, and a repository that is itself a fork is no longer penalised. Native Terraform comments and statuses go through ci.Reporter, so the gate applies uniformly, and env, path, and SARIF writes are held for fork pull requests under elevated events. ATMOS_ALLOW_UNSAFE_FORK_EXECUTION sets ci.allow_unsafe_fork_execution, as the docs already claimed.CommentRequest.Target (auto, pr, commit) with a CommitCommenter capability, a GitHub implementation, ghtest routes, and a generic preview. auto posts to the pull request when known and to the commit otherwise, so a push run no longer fails for lack of a pull request.ci.enabled when the master switch is off (the warning previously blamed a per-feature flag the user had on). Annotations and ::add-mask:: go to stderr; log-group markers go to stdout to bracket command output; ::add-mask:: was being masked by Atmos before it reached the runner. Repeated ci.base() calls no longer stack duplicate safe.directory entries. Nested log groups render a heading instead of a nested ::group::. behavior=update requires a key, and a local update with no prior comment fails like GitHub. Check updates send the id, and DetailsURL is always filled.--ci flow, not a cached warning. The native-ci fixtures point at an unroutable GITHUB_API_URL so their fake tokens can never reach api.github.com.ci.comments.enabled is on (the gated write used to dump the full image summary into the log as a preview), keyed by registry/repository so pushes update one comment, truncated at 65,000 characters, with failures at Warn. The two near-duplicate implementations and their 667-line mocks collapse into pkg/component/container/imagesummary.Every item was found by reading the code against its docs and then reproduced with a failing test before the fix. The fork gate as merged in #3308 did not post for the one case it was built for, and failed open for the one case it had to close. The rest are the differences between what the CI configuration pages promise and what a script author actually sees.
osterman/ci-fork-templates-hygiene) in GitHub stack #3338; the ci module host wiring, step library, and documentation follow in #3319, #3320, #3337, and #3321.docs/fixes/2026-10-08-stack-field-test-fixes.md (lands with the documentation pull request).🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>fix(automation): wire the ci module into every host and harden script inputs @osterman (#3319)</summary>
Fixes from a field test of the Starlark ci module (#3307) and the standalone script and custom-command input surface (#3261 through #3276).
ci.NewReporter(nil), so under GitHub Actions every gate read as off, warnings named flags the user had enabled, and comments and checks never posted. Both control adapters now pass the configured reporter, the engine warns when a host supplies none, and host-wiring tests cover standalone, direct step, workflow, hook, parallel, and matrix.ci.comment(target=) (auto, pr, commit), returned as .target. Annotate rejects line without file and end_line before line. Check handles send the id on update and expose the details URL.ci.summary(data=...) and ci.comment(data=...) require template=; there is no configuration default for scripts. Rendering uses missingkey=error, so a typo'd key fails naming the key; a missing template names the resolved path and ci.templates.base_path; a configured but missing ci.templates.container.image is an error.defer calls with the documented 30 s grace, then exits 130. main.go used to exit before any context was cancelled.#!/usr/bin/env -S atmos <flags> and .STAR are recognized; atmos - on a TTY says it is reading stdin; cli.flag rejects a default outside choices and checks an explicit empty value; --help ends the script; a relative script path resolves against the directory the user stood in before --chdir; atmos.tf shares the terraform binding; exec.run, component.exec, and atmos.* accept output="viewport".type: int flags parse base-10 (010 is 10, 0x10 is rejected); a wrong-typed default stubs the command with a warning naming the flag instead of silently becoming "" or false; an argument with neither required: nor default: is required again; !literal is honored on plain-string steps, command-level env, parallel and matrix env, and timeout; unsupported fields fail config load naming the field; !include.raw is used exactly as written and the template-error hint for included scripts no longer suggests a tag that cannot be applied there.retry.conditions mean the same thing in every host (used by the next pull request), tighter ErrorIs assertions in the script tests, and new acceptance suites starlark-ci.yaml, starlark-inputs, and starlark-literal-invalid.The host-wiring gap meant the ci module worked in exactly the places its unit tests mocked and not in the parallel steps a real pipeline uses. The input fixes close the differences between the documented contract (literal.mdx, cli.flag, ctx.flags, defer.mdx) and the shipped behavior; each was reproduced with a failing test first.
osterman/ci-fork-gate-commit-comments in GitHub stack #3338.docs/fixes/2026-10-08-stack-field-test-fixes.md (lands with the documentation pull request).target=; viewport added alongside stream and capture.🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
atmos.tf alias and improved standalone script discovery, including case-insensitive extensions and more flexible shebangs.--chdir is used. Ctrl-C runs deferred cleanup, and help exits before later script actions.<details> <summary>docs: align CI and automation guides with field-test fixes @osterman (#3337)</summary>
Align CI, step, hook, and script documentation with the field-test fixes. Clarify template defaults, the ninth-hook recursion boundary, stdout log-group markers, and image-comment commit fallbacks and permissions. Move detailed CI script guidance into the skill reference to keep the main skill within its size limit.
Keep the documentation corrections separate from the Scripting navigation and URL migration, with each PR below 150 changed files.
Full documentation production build passes. Current-head CI and CodeRabbit verification are pending.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>docs: clarify Scripting guides and migrate URLs @osterman (#3321)</summary>
Label the sidebar and landing page Scripting, introduce Atmos Automation Language once, and move the guides to /scripting with redirects from the previous URLs.
Rewrite the guides to explain concepts and syntax before examples. The hooks guide covers component, scaffold, and Git hooks, including events, inputs, and failure behavior. CLI examples lead with executable commands such as ./myapp and explain arguments, flags, and help directly.
Make scripting easier to find and the guides easier to use. Show where each feature belongs and how to run it before introducing a larger example.
The full website build passed, as did navigation and documentation checks. Existing unrelated CI-page anchor warnings remain. Current-head GitHub checks and CodeRabbit approval are pending. No coverable Go changes.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>Add the embedded Starlark runtime and command APIs @osterman (#3264)</summary>
Keep interpreter behavior and language bindings independently testable before wiring them into commands, workflows, and hooks. Reuse registered command metadata instead of maintaining a parallel list of commands and flags.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>Introduce Atmos Automation Language across commands and hooks @osterman (#3266)</summary>
Reusable scripts need the same command definitions and execution policies as the CLI. Final-build validation exposed context, environment, source-provenance, masking, and test portability gaps that unit mocks had missed.
component.exec calls.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>Add declarative script interfaces and automation documentation @osterman (#3261)</summary>
cli.command, cli.arg, and cli.flag, reusing native Atmos flag definitions, StandardParser, its registry, and positional-argument validation. Help and input validation finish before the main callback runs.ctx.flags and ctx.arguments, preserving parsed types through parallel, matrix, and test children. Remove the capacity example's environment mapping and regenerate its cast./automation the documentation home for Atmos Automation Language, with dedicated reference guides for the language, custom CLI apps, custom Atmos subcommands, workflows, lifecycle hooks, and testing. Link the homepage automation card to this hub, keep reference navigation inside the docs, and embed three focused casts.Small scripts should share the CLI's parsing and validation behavior, and embedded scripts should receive inputs Atmos already parsed. A dedicated documentation entry point connects standalone programs, project commands, hooks, and workflows to the same language and reference.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>docs: add Automation Functions and language references @osterman (#3274)</summary>
/functions/automation, next to YAML and Template Functions, with one page per function. It covers the cli.* declarations, every atmos.<command> wrapper (aliases are listed on their main command's page), components.get, component.exec, exec.run, steps.task, steps.parallel, fs.read_file, json.*, regex.*, dependencies.tools, each ui.* and log.* function, and the built-in values (ctx.*, env, output, print, load). Every page has usage, arguments, return values, and at least one example./automation/reference covering lexical elements, data types, expressions and operators, statements, built-in functions, methods, the execution model, and differences from Python.The automation docs were guides only. Users and agents had nothing to look up for exact signatures, defaults, return values, or language rules. Signatures were taken from the Go source, and examples were run against the interpreter built from this stack.
🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
errors.build helper for reporting script failures with structured details.Documentation
<details> <summary>feat(steps): !literal step fields and reliable custom-command inputs @osterman (#3275)</summary>
!literal in atmos.yaml, and honor it on step fields: script, command, interpreter, working_directory, and individual env values. This works in custom commands, workflows, hooks, and parallel and matrix children. Tagged values are never template-rendered at run time, and markers are recorded only on step mappings, so vars, settings, and env maps are unchanged.type: int flags, reject unknown flag types, and allow optional arguments without a default.timeout: on script, shell, atmos, and tflint steps, including workflow container paths. Reject unknown output: modes.!literal.A field test of Atmos Automation Language in custom commands and workflows found step definitions that silently changed user data, and Starlark source containing {{ could not be written at all. Details are in docs/fixes/2026-10-04-literal-steps-and-custom-command-inputs.md.
🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
!literal support for step fields and declared environment values, allowing template-like text to pass through unchanged.<details> <summary>Expose automation steps, decoded query results, and execution controls @osterman (#3278)</summary>
Expose the registered Atmos step library through the shared pkg/automation Go API and Starlark steps.* bindings. Scripts can use prompts, HTTP requests, containers, archives, and the other registered handlers, with values, metadata, and named outputs available to subsequent calls.
Add lazy JSON decoding through result.data while preserving raw process stdout/stderr and step value. atmos.list, atmos.describe, and configuration getters default to captured JSON; explicit format/output choices still apply. Add --format=json to the CLI configuration getters without changing their raw-output default.
Expose timeout and retry options on exec.run and component.exec through a shared Go execution policy. A timeout covers all attempts and backoff; retries apply to checked ordinary nonzero exits and can match output conditions.
Document the APIs and restrictions, update help recordings, and add changelog and roadmap entries. The enclosing runner still owns workflow scheduling, identity preparation, background jobs, and freshness policies.
Scripts should reuse Atmos's step handlers and execution controls, and inspect structured command results without repeating JSON parsing or subprocess policy. Language bindings convert arguments and results; the shared Go interfaces own execution behavior.
Stacked on #3276 in the linear automation stack. This PR changes 81 files, below the 150-file review limit.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
data.config get, stack config get, and stack get support --format/-f with raw and json output.<details> <summary>Run embedded Starlark steps in Git hooks @osterman (#3283)</summary>
Allow git.hooks.<name>.steps to run named steps directly inside Atmos, including inline Starlark scripts. Existing command hooks remain supported; each hook selects one form.
Add fs.glob, fs.stat, fs.exists, and fs.readlink, backed by a shared Go filesystem interface. Add two inline repository checks to atmos.yaml: tracked symlinks and CLAUDE.md/agent-file byte limits.
Refresh the Git-hook, SDK, interpreter, workflow, scaffold, and lifecycle-hook PRDs to match the implemented API. Clarify the language overview and introductory announcement around writing and testing application and infrastructure delivery processes.
Small repository checks can live beside their hook configuration, use structured errors, and share the same step library as other automation. Embedded scripts do not launch a second Atmos process. Hook arguments are available through ctx.args; steps share outputs and environment changes and stop on failure.
The sequence uses synchronous step execution and rejects workflow scheduler policies. Checks inspect working-tree contents, including unstaged changes. The existing pre-commit project setup retains its Bash checks because its pinned released Atmos binary predates these APIs.
go build ./... passed. Configuration, generated-schema, and Git-hook package tests passed, including loader coverage for !literal, relative script includes, and imported hook definitions.atmos test and atmos test --full passed for automation, interpreter, Git-hook, step-runner, and schema packages.atmos lint --changed and production documentation build passed; PRD local links checked. The combined tree with the latest docs reorganization also passes navigation, command-introduction, and example-metadata checks, with no broken links or anchors.Stacked on #3278. Includes configuration schema, function reference, Git-hook documentation, release announcement, and roadmap update.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>feat: compute stack values with !starlark @osterman (#3286)</summary>
Add !starlark to stack manifests. A scalar body uses return to produce typed configuration values from read-only ctx.vars, ctx.metadata, settings, environment, and component identity.
Expressions run after the existing YAML-function merges, resolve other computed values on access, and report circular dependencies. Literal source survives Go templates and retains its original filename and line. Configuration evaluation uses the interpreter registry with a separate typed-value capability and a 100,000-step budget.
Add the PRD, YAML-function reference, language-overview link, and roadmap milestone. Explain !starlark in the main Atmos Automation Language announcement, with a resource-tags example and a redirect from the consolidated post. This PR contains fewer than 150 changed files.
The schema ratchet classifies !starlark as stack-manifest-only. The lint and TFLint-hook CI jobs use the shared toolchain action to reuse the build job's verified binaries and avoid redundant release-attestation API calls.
Define tags, generated lists, and environment-specific values once, then compute them for each component's final configuration. The configuration host provides language builtins and JSON conversion; executable scripts provide commands, prompts, and the step library.
Reuse the shared CI toolchain cache, classify the new YAML tag for schema generation, stop SHA-pin lookups after API quota exhaustion, and pass large diagnostics between action steps through a file. Bound PR diagnostic tables, remove summed environment allocation capacities flagged by CodeQL, and make the controller-runtime NOTICE license URL deterministic. Incorporate the lower-stack formatting-bot commit while retaining the correct URL so GitHub’s combined stack checkout preserves it. Classify !starlark as forbidden in selection metadata because its context dependencies can require authentication or command execution.
actionlint.The full internal/exec short suite hit its 10-minute timeout. The scoped YAML/template regression suite passed.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
!starlark expressions in stack manifests to compute typed configuration from merged component context. Expressions can reference other computed values, with dependency cycles reported as errors.Documentation
Bug Fixes
</details>
<details> <summary>fix: harden automation inputs, steps, hooks, and stack values @osterman (#3295)</summary>
Make script inputs, step execution, Git hooks, and computed stack values behave consistently across the CLI. This includes named usage errors and argument help, profile/identity forwarding, step-field rendering and validation, case-preserved variables and outputs, hook working directories and shim maintenance, and consistent Starlark context during stack discovery and generation.
Git hooks and standalone scripts now omit local resource-usage summaries when settings.metrics.enabled is unset. Existing Git command hooks also use this default; explicit configuration is preserved. Set settings.metrics.enabled: true or ATMOS_SETTINGS_METRICS_ENABLED=true to retain the summary. Edition pins do not gate this command-specific behavior change.
Stack naming templates reject computed identity values before functions can transform them. Varfile generation defers provisional workspace identity validation until computed values resolve, then applies the same final identity checks. Git hooks resolve inherited relative Git paths against the caller’s working directory before changing directories.
Field tests exposed cases where script flags affected Atmos itself, malformed steps ran too late to fail safely, hook installation was not idempotent, and computed values differed between describe and generation commands. Regression tests cover those behaviors and preserve raw script source until the correct evaluation phase.
docs/prd/git-hook-steps.md#migration-and-editions.docs/fixes/2026-10-07-*.md.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Documentation
<details> <summary>docs: align automation guides and add CLI acceptance cases @osterman (#3296)</summary>
Align the automation guides, function references, Git-hook documentation, and agent guidance with the validated runtime behavior. Add acceptance fixtures for standalone CLI inputs, step fields, Git hooks, computed YAML values, and stack identity validation.
Users need examples that show the exact input, output, working-directory, timeout, and error behavior they will get. The fixtures exercise those paths through the CLI, while the guides explain when templates and Starlark evaluate and how tool dependencies reach scripts.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>feat(automation): ci module for reporting from scripts @osterman (#3307)</summary>
Adds the ci module to the Atmos Automation Language, so any script (standalone, custom command, workflow, or hook step) can report into the CI provider that is running it with one call each, and renders the same calls locally when no provider is detected.
ci.context (provider, event, SHA, branch, repo, actor, run ID/URL, elevated, pull request) and ci.base().ci.summary, ci.output, ci.env, ci.path, ci.mask, ci.annotate, ci.comment (keyed upsert, returns id/url/created), ci.check (handle with update), ci.group, ci.sarif.ci.* configuration switches as native reporting; a gated-off call warns naming the flag and renders locally. Comments and checks are held on pull_request_target/workflow_run unless ci.allow_unsafe_fork_execution is set.atmos.ci distinguishing the subprocess wrapper, the PRD docs/prd/native-ci/framework/script-ci-module.md, a changelog post, and a roadmap milestone.steps.parallel tasks, task-prefixed output), plus an integration test through the real generic provider.Teams moving build/test/deploy pipelines out of GitHub Actions YAML into Atmos custom commands had no way to report back to the pull request without shelling out to gh and echoing into $GITHUB_ENV by hand, and none of that worked on a laptop. The seam this module calls landed in #3298; this PR is the user-facing surface.
Example (runs unchanged with atmos app test api --stack=dev in CI and locally):
tests = ci.group("test", lambda: exec.run(["go", "test", "./..."], check = False, output = "capture"))
ci.summary(body)
ci.comment(body, key = "app-test:" + component + ":" + stack)
ci.output("tested", "true" if tests.exit_code == 0 else "false")
osterman/ci-reporter-seam), which is stacked on #3296.pr.fork, and housekeeping) is listed in the PRD under "Remaining implementation work"; per CLAUDE.md, no issues are opened for unmerged implementations.fs.resolve and tilde-path support for fs.* functions (see docs/fixes/2026-10-07-fs-resolve-and-tilde-paths.md).digest module (digest.sha256, digest.sha512, digest.sha1, digest.md5) and exec.which(name) (see docs/fixes/2026-10-07-digest-module-and-exec-which.md).defer(fn, *args, **kwargs): cleanup that runs last in first out when the script or task finishes, after fail() and cancellation (see docs/fixes/2026-10-07-defer-builtin.md).🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
</details>
<details> <summary>fix(ci): share CI reporting workflow and limit recovery scans @osterman (#3376)</summary>
published output to invoke the Go quality reporter after Actions workflows finish, keeping stopwatch's TypeScript code and separate timing comment unchanged.main PRs updated within 24 hours with early pagination stopping, selection logging, missing-timestamp validation, and no unchanged label writes.go test -tags mage ./magefiles/qualitygate/..., actionlint, and all commit hooks.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
main updated within the past 24 hours; manual checks cover all open pull requests to main.<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>chore: bump Claude Code plugin version to v1.232.0 @cloudposse-releaser[bot] (#3369)</summary> Automated changes by create-pull-request GitHub action </details>
<details> <summary>fix(ci): quiet Quality Gate comment; skip CodeRabbit gate for bot PRs @osterman (#3375)</summary>
<details> block, like "All other benchmarks". The headline and per-snapshot warning lines stay visible above it.github.com/cloudposse/atmos/ module prefix from benchmark metric names. Rows now read tests/benchmarks/CLI/DescribeAffected/... (sec/op).user.type == "Bot"): Renovate, Dependabot, the github-actions token, cloudposse-releaser[bot]. Evidence reads "Not required: PR opened by automation (<login>)".cloudposse-releaser[bot]).🤖 Generated with Claude Code
</details>
<details> <summary>fix: enforce planfile verification in multi-component deploy @tokanize (#3397)</summary>
terraform deploy (--affected, --all, --components) now runs the same stored-plan check as single-component deploy, per component. Drift or a missing required plan fails the node before apply. A match applies the fresh plan.PlanFile into the executor. Before, the executor got a copy made before the hook ran, so the result was lost.provision.workdir that share a source dir take a lock on it, only while verification can write stored.plan.tfplan and new.plan there (storage configured, verify not off).cmd/terraform/verify_plan_bulk_test.go and pkg/scheduler/adapters/terraform_test.go, fix log in docs/fixes/.terraformRunWithOptions return before verifyStoredPlanForDeploy, so only single-component deploy ever reached it. The download hook is warn-only and counts on that gate. Result: bulk deploy applied changed inputs and missing plans with exit 0.verify / required / storage combination, including the warnings single deploy already logs outside CI. No new flags or config.go build ./..., atmos lint --changed, go test -count=1 on cmd/terraform, pkg/scheduler, pkg/scheduler/adapters, pkg/ci/plugins/terraform/..., internal/exec, -race on cmd/terraform and the adapters. atmos test --full fails only in pkg/ci/startup and pkg/runner/step (PTY cast tests), same on a clean main at 753f2fed. Manual runs with local/dir and with github/artifacts in GitHub Actions: bulk drift and missing exit 1 with state untouched, matching applies in dependency order, single-component rows unchanged.aws/s3 or a real AuthManager, both covered by unit tests with stubs.patch (bug fix, no new flag). Can't set labels from a fork.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>fix: restore describe lookup caches and reduce resolution overhead @osterman (#3380)</summary>
!terraform.output, !terraform.state, and atmos.Component, partitioned by execution mode, configuration root, and authentication.Inspection cache bypasses and repeated deferred target describes multiplied lookup work. Profiling identified repeated full-stack capture for goroutine IDs. The follow-up report on #3353 exposed another multiplier: ambient store entries were split by caller stack, causing 660 backend reads for 11 keys across 20 stacks and three describe passes. After fixing that multiplier, rebuilding effective auth for empty component auth maps still added work on every cache hit.
The store workload is back to v1.229.0 speed. Rebuilt local field test using an identical current harness, twenty fresh-process samples per version in one series, Apple M4 Max, Go 1.27.1, GOMAXPROCS=2:
| Version | Median | Change versus v1.229.0 | Backend reads |
|---|---|---|---|
| v1.229.0 | 0.596 s | baseline | 11 |
| v1.231.0 | 12.17 s | +1,943% | 7,920 |
| v1.232.0 | 1.699 s | +185% | 660 |
| This PR | 0.617 s | +3.55% | 22 |
This PR is 19.7x faster than v1.231.0 and 2.75x faster than v1.232.0. The remaining 3.55% difference from v1.229.0 is below the 10% regression threshold.
The earlier ten-sample Terraform/component comparison measured 0.46957 s, versus 0.51650 s for v1.228.0 and 1.58634 s for v1.232.0: 9.09% faster than v1.228.0 and 70.40% faster than v1.232.0 (both p=0.00001083). These are separate field-test series, not stored CI snapshots.
The store read-count advisory remains: 22 versus 11 because HEAD and BASE have independent values. The fixture uses a loopback SSM service and fake ambient credentials; the customer's real AWS timing and effective default-identity configuration remain unverified.
Raw component describes can evaluate recursive stack locals, so those cache misses deliberately do not use singleflight. Concurrent cold misses may duplicate work while completed values are reused.
Validation: focused race tests cover cycle detection, deep-stack identity, inspection/cache/auth isolation, concurrent store credentials, and auth changes after cache hits. go build ./..., scoped atmos test, all new CLI scenarios via scoped atmos test --full, Mage tests, changed-file lint, all pre-commit hooks, and the website build passed. Earlier broad runs encountered startup-notice environment failures and terminal/CLI/workflow timeouts; full-suite success is not claimed. Details and reproduction commands are in the fix log.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
</details>
<details> <summary>fix(steps): validate step fields, honor retry conditions, end whole process trees @osterman (#3320)</summary>
Fixes from a field test of the automation step library, process cleanup, Git hook steps, and !starlark values (#3278 through #3296).
steps.shell(url="x") and steps.join(command="x") now error with the step type and the valid list instead of being accepted silently.retry.conditions apply to every step type (regexes over stdout, stderr, and error text; a non-matching failure stops at once); only http keeps its own status matching. Workflow and custom-command shell and atmos steps honor them too.ShellRunnerWithWriters caller (custom commands, workflows, !exec, hook commands), run children in a process group that is torn down on timeout or cancel. A custom-command type: shell step with a timeout and a backgrounded grandchild used to hang Atmos forever on the pipe the orphan held; a regression test covers it.Step '<name>' (type <t>) did not finish within its timeout of <d> everywhere, not a bare context deadline exceeded; capture and stream on steps.<type> point to exec.run.!starlark. Selective commands (list … --columns, describe stacks --sections, describe component --query) evaluate only the config fields a value reads through ctx, by static reference analysis with a full-evaluation fallback; a component containing !starlark no longer runs sibling !exec values those commands never asked for. !starlark in atmos.yaml is rejected naming the file and key."$@" and ATMOS_GIT_HOOK_ARGS; push-style hooks get their stdin in ATMOS_GIT_HOOK_STDIN and the first shell step still gets it on stdin; a later configuration source can switch a hook between steps: and command:; shims pin the atmos path at install and fall back to PATH; a prompt without a default fails with a hint; the failing step's exit code propagates.ATMOS_HOOK_DEPTH recursion guard (limit 8), profile and identity forwarded to script steps in custom commands, workflows, and hooks, and --format on config get, stack get, and stack config get registered through the standard flag parser with per-command environment variables.The hang and the !starlark side effects are the two findings that could cost a user real time or run commands they did not expect; the rest turn documented promises (steps.run.mdx, retry.mdx, the Git hook pages) into enforced behavior. Each was reproduced with a failing test before the fix.
osterman/starlark-ci-module-inputs-fixes in GitHub stack #3338.docs/fixes/2026-10-08-stack-field-test-fixes.md (lands with the documentation pull request).🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
config get, stack get, and stack config get support command-specific format environment variables; an explicit --format flag takes precedence.!starlark tags in atmos.yaml now produce an error.Improvements
<details> <summary>fix(starlark): standalone scripts behave like real CLIs @osterman (#3276)</summary>
ATMOS_USE_VERSION, version.use, and --profile re-execution.atmos --chdir=dir tool.star. Extensionless paths run as scripts when they have an Atmos shebang.None output as no output, so --help no longer prints null.true or false follows a boolean flag.--help hint, and the missing argument named. Help marks required flags, choices, and env bindings. Tracebacks use relative paths..star extension is optional when a script runs by path, and how to set editor file-type hints for Vim, Emacs, GitHub Linguist, and VS Code.A field test of interpreter mode found that re-execution dropped the script, parsing quirks silently produced wrong values, and user mistakes looked like Starlark crashes. Details are in docs/fixes/2026-10-04-standalone-script-cli-behavior.md.
!literal and step fixes), which is stacked on #3274 and #3261.🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
--chdir, and version-pinned reruns while forwarding script arguments correctly.None to top-level output produces no standalone output; None inside lists or dictionaries remains JSON null..star paths from other paths and directories.</details>
<details> <summary>fix: clean up child processes when automation is canceled @osterman (#3294)</summary>
Terminate non-interactive subprocess groups when Atmos is canceled or a step times out. On Unix, children receive SIGTERM followed by SIGKILL after a bounded grace period if needed. Interactive children retain their terminal process group; Windows continues to terminate the direct child.
Canceling Atmos could leave commands and grandchildren running after a deployment stopped. Cleanup now completes before the canceled command returns, including when a parent exits before a grandchild that ignores SIGTERM.
docs/fixes/2026-10-07-child-process-group-signal-propagation.md.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>feat(ci): Reporter seam, local-parity generic provider, GitHub fake API @osterman (#3298)</summary>
Foundation for exposing the native CI surface to the automation language (the Starlark ci module lands in the next PR of this stack). No Starlark in this PR.
ci.Reporter (pkg/ci/reporter.go): one injectable seam with Summary, Output, Env, Path, `Note truncated.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Vulnerability scan reports now remove duplicate stack entries before submission, preventing duplicate-entry errors. Reports are preserved if scanning…
<details>
<summary>docs(validation): add OPA-focused example and repoint validation docs @aknysh (#3360)</summary>
</details>
<details>
<summary>fix(ci): stop Quality Gate concurrency queue overflow @osterman (#3367)</summary>
</details>
<details>
<summary>fix(ci): use ARM benchmarks and improve quality reports @osterman (#3363)</summary>
</details>
<details>
<summary>feat(ci): add benchmark history and extensible quality gates @osterman (#3356)</summary>
</details>
<details>
<summary>fix(ci): tap homebrew/core before bumping the Homebrew formula @aknysh (#3336)</summary>
homebrew/core before bumping the formula.</details>
<details>
<summary>fix(ci): dedupe govulncheck SARIF stacks via ci:vulncheck mage target @osterman (#3347)</summary>
</details>
<details>
<summary>Use .tool-versions as the tool baseline for every command and component @osterman (#3346)</summary>
.tool-versions support across components, workflows, custom commands, hooks, and commands. Explicit tool dependencies take precedence over matching manifest entries.toolchain.install policies: never, declared, auto (default), and always. Projects pinned to editions before 2026-10-09 retain the declared default; ATMOS_TOOLCHAIN_INSTALL can override the setting.</details>
<details>
<summary>Honor color opt-outs and add independent log color control @osterman (#3345)</summary>
logs.color, --logs-color, and ATMOS_LOGS_COLOR. Log color is enabled by default when available, and CLICOLOR=0 disables automatic color unless color is forced.true or false values, such as --logs-color false.logs.color values now produce a clear error instead of being silently interpreted as false.--no-color and nonempty NO_COLOR disable color across logs and terminal output, even when color is forced. Nonempty NO_COLOR takes precedence over conflicting flag values.</details>
<details>
<summary>fix(auth): honor AWS ambient identity environment overrides @osterman (#3362)</summary>
</details>
<details>
<summary>fix(config): preserve imported auth identities when main config defines identities @osterman (#3339)</summary>
</details>
<details>
<summary>fix(auth): refresh AWS user chain sessions and stabilize CI @osterman (#3351)</summary>
</details>
<details>
<summary>fix(auth): paginate and cache SSO account name lookups @osterman (#3344)</summary>
</details>
<details>
<summary>fix(store): cache deferred atmos.Store template lookups @osterman (#3354)</summary>
</details>
<details>
<summary>build(deps): bump github.com/google/go-containerregistry from 0.21.9 to 0.22.0 @<a href="https://github.com/apps/dependabot">dependabot[bot]</a> (#3146)</summary>
</details>
<details>
<summary>chore(deps): update floci/floci docker digest to 4e451c3 @<a href="https://github.com/apps/renovate">renovate[bot]</a> (#3130)</summary>
d2ecc80 → 4e451c3 |</details>
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.