NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1416 by repository stars
Latest stable
v1.234.0
Last release 13 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.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
Nothing published for this version
Add Validation, Scaffolding, and Emulators cards to landing grid @osterman
<details> <summary>Add Validation, Scaffolding, and Emulators cards to landing grid @osterman (#2974)</summary>
/validation/validating, /cli/commands/scaffold/usage, /cli/commands/emulator/usage) were verified against how other docs pages already link to these same destinations internally, not guessed.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>fix(container): resolve build/mount paths via base_path, add JIT source support @osterman (#2979)</summary>
components.container) now resolve build.context, build.dockerfile, and run.mounts[].source the same way Terraform/Helmfile/Kubernetes/Helm components resolve theirs: relative to components.container.base_path joined with the component's own name, via a new precomputed ContainerDirAbsolutePath and a "container" case in the shared component-path resolver.components.container.base_path is promoted from an ad hoc, silently-ignored config value into a real, typed Components.Container field.source: provisioning as Terraform/Helmfile/Kubernetes/Helm — a component declaring a source is auto-vendored into a workdir, which then anchors build/mount paths instead of the static base path.container.Config/DefaultConfig()/parseConfig(), and fixed a hardcoded "components/container" literal in describe_stacks.go that ignored any configured override.atmos.yaml JSON schema, updated the container CLI docs and the atmos-container agent skill, and added a changelog post + roadmap milestone.build.context/build.dockerfile were passed to docker build/podman build completely unanchored, so they silently resolved against whatever directory atmos happened to be invoked from instead of the project — working by accident only when run from the repo root.run.mounts[].source anchored to the bare project root rather than the component itself, and components.container.base_path had no effect anywhere despite being accepted as valid config.base_path + component:/metadata.component) plus JIT source provisioning; containers were the one component kind never wired into it.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
components/container.source: when needed.Documentation
<details> <summary>fix(ci): scope test-required aliases to their own OS's shard results @osterman (#2976)</summary>
test-required (the legacy compatibility shim that aliases the sharded test matrix under the three historical required-check names) checked needs.test.result, which is a single aggregated verdict across the entire test matrix (3 OSes × 10 shards). A failure in any one shard on any one OS flipped that aggregate to failure, so all three aliases (Acceptance Tests (linux/macos/windows)) failed together even when only one OS actually had a failing shard.
This PR rewrites test-required to query the run's actual per-job results via gh api .../actions/runs/.../jobs, filtered by OS, so each alias only fails when a shard belonging to its own OS failed. It also stops gating the macos alias on terraform-registry-cache (whose matrix only has linux/windows legs and has no macos job to report on), which had the same cross-OS aggregation bug.
Observed on #2972: windows shard 2/10 failed after 57s, and Acceptance Tests (linux), (macos), and (windows) all failed within 3-4s as sympathetic failures with no real linux/macos test failures, forcing unnecessary re-runs/investigation of unaffected OSes.
</details>
<details> <summary>fix: ECR/ACR ambient-credential errors and broken --identity selector @osterman (#2977)</summary>
atmos aws ecr login / atmos azure acr login ambient-credential fallback (no Atmos identity
configured) now returns a rich, actionable error when the underlying cloud SDK fails to retrieve
credentials (e.g. EC2 IMDS timeout, Azure managed identity failure), with an explanation and a
hint to run login --identity <name> or configure via.identity.--identity (no value) failing with flag needs an argument instead of showing the
interactive identity selector, on 6 commands: custom commands (atmos.yaml commands:),
describe, list, aws ecr login, aws eks token, and azure aks token. Each had hand-rolled
its own --identity flag registration instead of using the shared flags.WithIdentityFlag()
builder that ~150 other commands already use, so each silently lost the NoOptDefVal wiring that
makes bare --identity legal and triggers the picker.auth.ResolveSelectedIdentity (pkg/auth/manager_helpers.go) so the
sentinel-to-interactive-picker resolution logic lives in one place instead of being duplicated
(aws ecr login) or missing entirely (the other five commands).atmos app build): first
--identity (bare) rejected as a usage error instead of prompting, and separately — once
ambient AWS credentials were tried as a fallback — a bare EC2 IMDS timeout with no indication
that configuring an Atmos identity was the fix.--identity flag exists as a single, centrally-defined flag specifically so this class of
bug can't happen; these 6 commands were the stragglers that never got migrated onto that shared
definition, so the bug had to be independently rediscovered and patched (see the ad-hoc
NoOptDefVal fix already present on aws ecr login) instead of being fixed once.docs/fixes/2026-08-20-ecr-acr-ambient-credential-identity-hint.mddocs/fixes/2026-08-21-identity-flag-noOptDefVal-consolidation.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
--identity now opens interactive identity selection across supported AWS, Azure, EKS, listing, description, and custom commands.Bug Fixes
Documentation
<details> <summary>fix: prevent concurrent-map-write panic in global Viper singleton @osterman (#2980)</summary>
pkg/config.GlobalViper() wrapper (SafeViper), instead of calling viper.GetViper()/viper.Set/viper.Get* directly — mirroring the embedded-mutex pattern already used by pkg/io/pkg/ui.pkg/hooks.GetHooks to forward the AtmosConfig it already received into ExecuteDescribeComponentParams, removing a redundant second, independently concurrent config load per hook invocation.mergedConfigFiles in pkg/config/load.go) by wrapping it in its own mutex-guarded tracker.pkg/config/load_concurrent_test.go, a -race-driven regression test that spins up concurrent LoadConfig calls against a real fixture and reproduces the original panic on unfixed code.bridgeVendorUpdaterConfig now fetches GlobalViper() once instead of once per Set call, and a new ciFlagKey constant replaces 10 duplicated "ci" string literals in cmd/terraform/utils.go (surfaced by golangci-lint's add-constant check once those lines were touched).atmos terraform ... --max-concurrency 3 (and even 2) could panic with fatal error: concurrent map writes inside viper.(*Viper).Set, reported from production usage. Root cause: pkg/config.LoadConfig bridges profiles.base_path and vendor.update.*/vendor.ci.* into the process-wide global Viper singleton on every call, with zero locking (spf13/viper has no internal synchronization), while the DAG scheduler runs LoadConfig concurrently — once per graph node — whenever --max-concurrency > 1.GetHooks was also triggering a second, entirely redundant InitCliConfig/LoadConfig call per node because it never forwarded the AtmosConfig it was already given, doubling the exposure to the race for no reason.go test -race, it reliably reproduces the exact viper.(*Viper).Set race reported in production; against the fixed code it passes clean.--max-concurrency 2 and 3.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
--ci=false now overrides CI environment settings and automatic CI detection.Tests
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
perf(lint): move golangci-lint cache/tmp out of worktrees @osterman
<details> <summary>perf(lint): move golangci-lint cache/tmp out of worktrees @osterman (#2988)</summary>
.golangci-cache/, .golangci-tmp/) to the OS user cache directory: <user-cache>/atmos-lint/<worktree-hash>/{cache,tmp} (~/Library/Caches/atmos-lint/... on macOS).<worktree-hash> (first 12 hex chars of SHA-256 of the absolute worktree path) preserves #2701's per-worktree isolation of golangci-lint's single-instance lock — the dirs just no longer live under the worktree tree.ATMOS_LINT_SHARED_CACHE=1 opt-out and explicit GOLANGCI_LINT_CACHE overrides behave exactly as before.docs/fixes/2026-08-24-fsmonitor-worktree-saturation.md with the full measured diagnosis.#2701 put a 156MB / ~37k-file cache that churns on every lint run inside each worktree — directly under any filesystem watcher observing that tree (git fsmonitor, Conductor's watchexec). At multi-worktree scale this saturated macOS FSEvents: git status measured 2.9s–timeout (>2min) with fsmonitor vs 0.04–0.15s without, and every pre-commit run pays that tax dozens of times, stretching commits to minutes. Moving the churn outside the watched tree makes this impossible to re-trigger on any machine, regardless of watcher configuration.
Measured after the fix: cold lint:precommit 9.1s, warm 1.5s, no cache dirs created in the worktree; a full commit through all pre-commit hooks + signing completes in ~5s.
perf(lint): isolate golangci-lint cache and lock per worktree) — introduced the in-worktree location this PR relocates; its lock-isolation intent is preserveddocs/fixes/2026-08-24-fsmonitor-worktree-saturation.md — full diagnosis, timeline, and machine-level remediation notes<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
<details> <summary>fix(devcontainer): disable moby so docker feature installs on Debian trixie @aknysh (#2975)</summary>
"moby": false on the docker-outside-of-docker devcontainer feature in .devcontainer/devcontainer.json.The Codespaces Prebuilds workflow (prebuild) fails on every push to main. Example failed run: https://github.com/cloudposse/atmos/actions/runs/32431458655/job/96623702606
The base image mcr.microsoft.com/vscode/devcontainers/base:debian now resolves to Debian 13 (trixie), which does not package moby-cli. The docker-outside-of-docker feature defaults to moby: true and errors out during the prebuild image build:
(!) The 'moby' option is not supported on debian 'trixie' because 'moby-cli'
and related system packages are not available in that distribution.
(!) To continue, either set the feature option '"moby": false' or use a
different base image (for example: 'debian:bookworm' or 'ubuntu-24.04').
ERROR: Feature "Docker (docker-outside-of-docker)" failed to install!
Setting moby: false makes the feature install Docker CE instead. This is safe and non-redundant: the devcontainer Dockerfile already configures Docker's official apt repo and installs docker-ce/docker-ce-cli, so no moby packages were ever needed — the feature only wires up the forwarded host Docker socket.
<!-- 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(ci): bump docker-build-push to v3.2.1 to fix release job summary crash @aknysh (#2973)</summary>
Docker Build step in .github/workflows/build.yml from cloudposse/github-action-docker-build-push v3.1.0 (02993d67) to v3.2.1 (ff59bd5).release / Build and push Docker image for Atmos CLI job has been failing on the post-build Docker Inspect summary step with jq: error (at inspect.json:79): Cannot iterate over null (null) → exit code 5, even though the image builds and pushes fine.docker inspect fields (.Config.Entrypoint, .Config.Cmd, .Config.Env, .RootFS.Layers) straight into jq's join/.[]/to_entries, all of which iterate. Atmos's image is FROM debian:trixie-slim with no ENTRYPOINT, so .Config.Entrypoint is null and jq aborts; under the default bash -e shell that fails the whole step.// []), released as v3.2.1. Verified ff59bd5 contains all four guards. This bump pins Atmos to that release so the release job's summary no longer crashes.<!-- 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(terraform): filter CLI args from output hooks @zack-is-cool (#2991)</summary>
TF_CLI_ARGS_apply configured through atmos.yaml no longer reaches Terraform-exec's internal output command. Post-apply output-store hooks can retrieve and publish the declared Terraform output after a successful apply.
Terraform-exec rejects manual command-specific argument variables during its output invocation. Atmos filtered inherited variables but restored them from the resolved component environment. The output path now ignores TF_CLI_ARGS and TF_CLI_ARGS_* while preserving normal environment variables and TF_VAR_* values.
TF_VAR_*.go build ./...atmos fix coverage origin/main0 issues.Closes #2990
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
TF_VAR_* values, while excluding TF_CLI_ARGS settings from output processing.Documentation
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>fix(packer): inject Atmos Auth credentials into the packer subprocess @aknysh (#2986)</summary>
atmos packer now sets up Atmos Auth the same way terraform and helmfile do: it creates and authenticates the component AuthManager, passes it to ProcessStacks, and injects the resolved identity's credentials into the packer subprocess environment before executing.resolveDefaultIdentity and the renamed prepareComponentAuthEnvironment, formerly prepareHelmfileAuthEnvironment) into internal/exec/utils_auth.go so helmfile and packer share one path instead of duplicating it.internal/exec/packer_auth_test.go) via two test seams: one asserts a non-nil AuthManager is passed to ProcessStacks; the other asserts an injected credential reaches the packer subprocess env.docs/fixes/.atmos packer build ran completely unauthenticated when relying on Atmos Auth. internal/exec/packer.go called ProcessStacks(..., nil) (nil AuthManager) and never called PrepareShellEnvironment, so no AWS credentials ever reached the packer process. Its datasources failed with:
Error: Datasource.Execute failed: No valid credential sources found
Both other component executors already do this — terraform via setupTerraformAuth + auth.TerraformPreHook, helmfile via SetupComponentAuthForCLI + credential injection — so packer was the odd one out, even though the AuthManager interface docstring explicitly lists Packer as a supported subprocess.
Verified against a real workload: atmos packer build <component> -s <stack> now proceeds into the AMI build (VPC prevalidation, keypair creation, etc.) where the stock binary failed with the credential error.
internal/exec/helmfile.go.AuthManager contract: pkg/auth/types/interfaces.go (PrepareShellEnvironment — "Use this for all subprocess invocations: Terraform, Helmfile, Packer, ...").docs/fixes/2026-08-23-packer-atmos-auth-credential-injection.md.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
atmos packer build now honors configured authentication settings.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
fix: grant workflows:write so release-major-tag can move the v1 tag @osterman
<details> <summary>fix: grant workflows:write so release-major-tag can move the v1 tag @osterman (#2962)</summary>
Adds workflows: write to the permissions: block in .github/workflows/release-major-tag.yml.
The release-major-tag job force-pushes the moving v1 tag (so external consumers can reference cloudposse/atmos/actions/cache@v1) using only contents: write. GitHub rejects any push — including a tag force-push — whose resulting tree differs from the target ref in .github/workflows/**, unless the token also has workflows: write.
Confirmed via gh run view --log on both a passing run (v1.225.0) and failing runs (v1.223.0, v1.226.0):
refs/tags/v1:refs/tags/v1 [remote rejected] (refusing to allow a GitHub App
to create or update workflow `.github/workflows/codeql.yml` without
`workflows` permission)
This made the job fail intermittently — specifically whenever a .github/workflows/* file changed since v1 was last successfully moved — forcing consumers to pin exact release tags (e.g. @v1.226.0) instead of the moving @v1 tag. The tagger action authenticates purely via github.token, so widening this workflow's own permissions: block is sufficient; no PAT or other change is required.
.github/workflows/release-major-tag.yml29426305603), v1.226.0 (32307634756)<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>fix: name the offending component/stack in backend_type mismatch errors @osterman (#2965)</summary>
checkTerraformBackendTypeMatch / checkRemoteStateBackendTypeMatch now name the offending component and stack directly in the error's hint text, e.g.:
component "bootstrap" in stack "sandbox": remote_state_backend_type is "local" but remote_state_backend: only configures s3...
TestProcessTerraformRemoteStateBackend_InheritedLocalTypeMismatch) reproducing the exact real-world shape that surfaced this, plus hint-text assertions on the existing mismatch tests.tests/fixtures/scenarios/remote-state-backend-type-mismatch/, tests/test-cases/remote-state-backend-type-mismatch.yaml) proving the fix end-to-end through the real binary.describe stacks/terraform plan for every other stack too, including ones totally unrelated to the misconfigured component.WithContext, which the CLI's default (non --verbose) error renderer drops entirely. The printed error gave zero indication of which of potentially hundreds of components across a repo was actually at fault.atmos describe stacks --stack core-gbl-marketplace failed with only "remote_state_backend_type is local but remote_state_backend: only configures s3" — no component, no stack. It took manually instrumenting the binary with debug prints to discover the real cause was an unrelated plat/sandbox component (vpc-no-provider) that overrides backend_type: local without a matching remote_state_backend_type. With this fix, that same failure now reads:
component "vpc-no-provider" in stack "orgs/cplive/plat/sandbox/us-east-2": remote_state_backend_type is "local" but remote_state_backend: only configures s3... which is immediately actionable.
None — found and reported internally, no existing issue.
<!-- 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(terraform): support Terraform 1.15+ module source interpolation @osterman (#2915)</summary>
module block uses variable interpolation in source (e.g. source = "./mods/${var.org}") when the variable is declared const = true — valid syntax under Terraform 1.15+, not just OpenTofu 1.8+.internal/exec/utils.go / internal/exec/terraform_detection.go so it no longer depends on detecting OpenTofu — renamed isKnownOpenTofuFeature → isKnownModuleSourceInterpolationDiagnostic, and the component_info flag validation_skipped_opentofu → validation_skipped_module_source_interpolation.allDiagnosticsAreModuleSourceInterpolation), instead of pattern-matching the collapsed Diagnostics.Error() string, which only renders the first diagnostic's text.terraform (no command: override), plus a fixture/test proving a real unrelated error is still surfaced when it co-occurs with the known-safe diagnostic.terraform modules -json, never the static parser), and added a permanent guard test (pkg/sbom/terraform_test.go) for that invariant.nanoid pnpm override in website/package.json to resolve the transitive website/pnpm-lock.yaml dependency to nanoid@3.3.18, fixing an open Dependabot alert (infinite loop on zero-size input). The two open image-size alerts have no upstream patch yet and are not auto-fixable.docs/prd/opentofu-module-source-interpolation.md, surfaced once that file entered the branch's diff.terraform-config-inspect before running any Terraform/OpenTofu command. That library decodes a module's source attribute with a nil hcl.EvalContext, so any variable reference there always produces the "Variables not allowed" diagnostic — regardless of whether the configured tool/version actually supports it.const = true variables, so plain-Terraform users hit the same diagnostic as a hard failure even though their syntax is valid.docs/prd/opentofu-module-source-interpolation.md (updated with a 2026-08-10 addendum)docs/fixes/2026-08-10-terraform-module-source-interpolation.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
Tests
<details> <summary>fix(container): build.load works without bake; portable bake vars @osterman (#2963)</summary>
load: true field to the plain (non-bake) engine: buildx container build step, so docker buildx build --load works without adopting bake:.load: true now requires engine: buildx, mirroring the existing driver/cache check).bake.vars from the --var CLI flag to environment-variable injection (NAME=value), since docker buildx bake has always resolved HCL variable {} blocks from the environment, while --var is a newer flag missing from older buildx builds (e.g. Debian Trixie's 0.13.1).website/docs/workflows/workflows/workflow/steps/type/container.mdx and records the fixes in docs/fixes/.docker-container), a build's output lands in BuildKit's own cache rather than the local Docker image store, so a following push step can't find the image unless --load is passed. Previously load only existed under bake:, forcing anyone who needed --load to also adopt an external docker-bake.hcl file just to flip one boolean.docker buildx bake --var isn't implemented on every buildx release (e.g. Debian Trixie ships 0.13.1, which predates docker/buildx#3610), so builds using bake.vars failed with unknown flag: --var on those hosts. Environment-variable injection is the pre-existing, universally-supported mechanism docker buildx bake uses to resolve HCL variable "NAME" {} blocks, so it fixes portability with no change in what a bake file can express.docs/fixes/2026-08-20-container-build-load-without-bake.mddocs/fixes/2026-08-19-container-bake-vars-env-injection.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
load support for plain Buildx builds, allowing images to be added to the local Docker image store.Bug Fixes
Documentation
<details> <summary>fix(ci): recover per-run assertion detail in test summary fallback @osterman (#2959)</summary>
terraform test output (used when per-run run "name"... pass/fail status lines weren't captured) now recovers the failing assertion's file, line, and message from terraform's Error: diagnostic block when it survived in the captured output.test summary (per-run detail unavailable): N passed, M failed with no location or message, even when that detail was still present in the raw text.errorLocationRe to parse the on <file> line <N>: locator out of a terraform error block, and reuse the existing ExtractErrorBlocks helper to populate the synthesized row's Error/File/Line fields. No template changes were needed — templates/test.md already renders those fields for fail/error rows.docs/fixes/2026-08-19-ci-test-summary-fallback-recovers-error-detail.md.docs/fixes/2026-08-14-ci-summary-test-table-fallback-dropped.md) stopped the results table from disappearing entirely on this fallback path, but the synthesized row still carried no per-test detail — CI test summaries showed only aggregate pass counts and a reproduction command, with no individual test-run/assertion detail, even when that detail was actually recoverable from the captured output.TestTestTemplate_SummaryFallback_LosesRunDetail) confirmed the gap before this fix; it's retained to document the remaining, genuinely irreducible case where no Error: block survives at all.docs/fixes/2026-08-14-ci-summary-test-table-fallback-dropped.md — the prior fix this builds on.docs/fixes/2026-08-19-ci-test-summary-fallback-recovers-error-detail.md — this fix's record.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
<details> <summary>fix: type: store step misrouted to container decoder in custom commands and hooks @osterman (#2961)</summary>
decodeStepWith (pkg/schema/workflow.go) so a step is only routed to the container with: decoder when type: container, instead of whenever action: is non-empty.kind: step hook bridge (pkg/hooks/step_engine.go) to backfill WorkflowStep.With from the hook's with: payload when the normal decode leaves it nil.type: store, and both the static and runtime hook decode paths.- type: store
action: write
with:
store: image-metadata
key: image-dev
value: "..."
stack: dev
component: app
failed before ever reaching execution with container action: writedoes not accept awith: block. decodeStepWith treated any step with a non-empty action: as a container step regardless of type:, so type: store (and any other non-container type that sets action:) was misrouted into the container decoder.kind: step / type: store component-hook pattern (see /workflows/steps/type/store) also silently dropped its store/key/value config, because the hook bridge round-trips the hook's with: payload directly into WorkflowStep's top-level fields — which works for step types with flat fields (archive, say) but not for step types like store/tflint whose config lives only in the generic With map. StoreHandler.Validate then failed with a generic "store is required" error that never showed the store the user actually configured.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
with values for store hooks when decoding workflow steps.Documentation
<details> <summary>fix(emulator): join Atmos's container to the shared network when reuse fails @osterman (#2960)</summary>
NetworkConnector runtime capability (docker/podman network connect).host.docker.internal (only when it actually resolves) before falling back to the default-gateway IP guess.--network, host socket mounted) to prove the self-detection/join mechanism works against a real daemon, not just a mocked runtime.atmos terraform test --ci run inside a CI job container (talking to Docker only through a mounted socket) started the AWS emulator successfully but reported an endpoint (http://172.17.0.1:<port>) unreachable from that same job container -- connection refused against the AWS provider's GetCallerIdentity call.docker run (no --network) sits on Docker's default bridge, which CurrentContainerNetwork correctly excludes from reuse (no embedded DNS/aliases). Reuse failing meant the endpoint fell back to a guessed default-gateway IP, which isn't where Docker Desktop's port-forwarding actually listens for sibling containers.AttachSharedNetwork now actively makes it reusable by connecting Atmos's own container to the dedicated network too -- so the existing DNS-alias endpoint logic just works, for every built-in emulator driver, not just AWS.docker:cli job container, no --network, mounted host socket): the emulator now reports a DNS alias instead of an IP, and atmos terraform test app -s fixtures --ci completes fully (Success! 1 passed, 0 failed, 0 skipped.) where it previously failed with connection refused.pkg/container/sibling_network_test.go + sibling_network_docker_test.go (opt-in via ATMOS_TEST_SIBLING_CONTAINER=1) reproduces the bug end-to-end inside a real nested container -- confirmed it fails with no such host when the join logic is reverted, and passes with it in place.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
host.docker.internal.Nothing published for this version
Nothing published for this version
Nothing published for this version
…nanoid infinite-loop DoS (GHSA-2v37-7h3g-55p8 / CVE-2026-67213).
<details> <summary>refactor(lint): go-native Mage tooling + goimports→gci formatter speedup @osterman (#2955)</summary>
Replaces the bash staleness-check/build orchestration for custom-gcl, lintroller, and
gomodcheck with Go-native Mage targets under magefiles/, invoked via
go tool mage <target> (Go 1.24+ tool directive — zero global install required). Also swaps the
goimports import formatter for gci, cutting full-repo formatter time by ~15-20x.
.atmos.d/lint.yaml's custom-gcl/lintroller/gomodcheck/changed subcommands now each
delegate to a one-line go tool mage lint:<target> shell step instead of a ~15-20 line bash
staleness-check block.scripts/run-custom-golangci-lint.sh (per-worktree cache/lock isolation, staged-patch vs
--new-from-rev branching for the pre-commit hook) is fully ported to
magefiles/mage_lint_golangci_run.go and deleted..pre-commit-config.yaml's golangci-lint/gomodcheck hooks now call
go tool mage lint:precommit / go tool mage lint:goModCheck..golangci.yml gets build-tags: [mage] so the new build tooling is linted too, with scoped
exclusions for forbidigo/lintroller (dev tooling outside the Atmos CLI/UI runtime — same
precedent already used for tools/gomodcheck/main.go)..github/workflows/codeql.yml's custom-gcl build step also moved onto go tool mage..golangci.yml's formatters section swaps goimports for gci, with explicit import-section
ordering (standard, default, prefix(github.com/cloudposse/atmos), custom-order: true).
Benchmarked directly on this repo (custom-gcl fmt -d, two runs each, warm cache both ways):
goimports ~95-108s real vs. gci ~5-7s real. gci is a stock golangci-lint v2 formatter, so
no .custom-gcl.yml plugin change is needed. CLAUDE.md and the lint-fix/test-coverage-fix
agent docs are updated to name gci instead of goimports.The historical "building custom-gcl in a pre-commit hook corrupts worktrees" invariant (hook only
ever checks + fails fast, never builds) is preserved exactly — see the comment on
Lint.Precommit in magefiles/mage_lint_precommit.go.
find -newer/[ -nt ], which are POSIX-only and
silently never worked on Windows (this repo's Cross-Platform requirement is MANDATORY per
CLAUDE.md). The Go port fixes this for free via os.Stat().ModTime() comparisons, and also
fixes the per-worktree cache isolation to set TMP/TEMP on Windows (Go's os.TempDir()
ignores TMPDIR there), which the bash version never handled.gomodcheck previously had two different implementations (a staleness-cached binary in the
atmos-command path, a plain go run in the pre-commit-hook path). Unified onto go run -C tools/gomodcheck . <go.mod> for both — go run already benefits from GOCACHE, so the cached
binary bought little for the extra code.goimports was a measurable bottleneck in local and CI lint runs; gci performs the same
import-ordering job in a fraction of the time with an equivalent (arguably clearer, since it's
explicit) section-ordering configuration.go build ./..., go vet ./..., go vet -tags=mage ./magefiles/... all pass.
All customGCL staleness branches (missing binary / config newer / plugin source newer)
manually triggered and confirmed correct.
lint:precommit fail-fast path: deleted ./custom-gcl, confirmed the same error message,
nonzero exit, and — the most important regression check — that ./custom-gcl is not
created as a side effect.
Staged-patch branch and --new-from-rev branch both exercised directly; MERGE_HEAD-present
branch verified via a simulated merge state.
Full pre-commit hook run end-to-end through the real pre-commit framework (binary-missing
failure path and binary-present passing path).
atmos lint lintroller/atmos lint gomodcheck/atmos lint custom-gcl all verified through the
real atmos binary with correct exit-code propagation.
atmos test (full suite) passes.
goimports → gci swap benchmarked directly: ./custom-gcl fmt -d (diff mode, no writes)
against the full repo, two runs per formatter with a warm filesystem cache both directions to
rule out a cold-cache artifact:
Full-repo custom-gcl fmt -d (diff mode, no writes), two runs each:
| Formatter | Run 1 | Run 2 |
|---|---|---|
goimports (old) |
107.6s real | 94.9s real |
gci (new) |
5.3s real | 6.9s real |
./custom-gcl formatters confirms gci is active and goimports disabled after the swap.
This PR's own commits went through the new pre-commit hook wiring live (go-fumpt,
golangci-lint via go tool mage lint:precommit, gomodcheck) and passed cleanly.
No user-visible behavior change — this is internal dev/CI tooling only.
</details>
<details> <summary>Centralized auth guide, GitHub CLI import auth, and caching fixes @osterman (#2923)</summary>
website/docs/tutorials/centralized-auth-config.mdx: centralize an organization's Atmos auth: config in one private repo and import: it into every project, with side-by-side AWS/Azure/GCP examples.CustomGitDetector.resolveToken to fall back to gh auth token (GitHub CLI) for private git:: imports, matching the fallback already used for HTTPS/API GitHub fetches.import: entry (typo'd ref, unreachable host, unauthenticated private repo) now warns by default instead of continuing silently with an empty configuration and exit code 0.imports.ttl caching across every remote import form. It previously covered only git:: imports that use a subdirectory; it now also covers plain remote URLs and git:: imports without a subdirectory, without touching the shared pkg/cache package's behavior for its other (unrelated) consumers.website/docs/cli/configuration/imports.mdx (caching section), changelog post website/blog/2026-08-11-remote-import-github-auth-and-caching.mdx (written in ASD-STE100 style), a roadmap milestone, and fix-log records under docs/fixes/.[profile] blocks pasted in Slack or wiki pages, which drift stale, don't scale to multi-cloud orgs, and have no audit trail or single source of truth. The tutorial documents Atmos's centralized-import pattern for this exact use case.git:: imports didn't actually get GitHub CLI auth, a broken import failed with zero visibility, and remote imports had inconsistent (in one path, nonexistent) caching. Fixed all three in code instead of documenting them as known limitations.</details>
<details> <summary>Shared per-stack networking for containers, emulators & run steps @osterman (#2942)</summary>
atmos container run containers, and stack-scoped workflow type: container, action: run steps now automatically join a shared per-stack Docker/Podman network and resolve each other by a <stack>-<component> DNS alias — no configuration required, similar to the default network docker compose creates for a project. Emulator components join the same network, so a container and an emulator in one stack can resolve each other too.GITHUB_ACTIONS), fixing connection refused when reproducing a socket-mounted job container locally.atmos terraform test summary silently dropping its results table (only badges and the repro command rendered) when per-run output lines weren't captured.</details>
<details> <summary>ci(test): shard acceptance tests 10-way per OS to cut CI runtime @osterman (#2940)</summary>
tests/cli_test.go's TestCLICommands now deterministically assigns each CLI test case to a shard by hashing its name, gated by ATMOS_TEST_SHARD/ATMOS_TEST_SHARD_COUNT env vars (a no-op locally when unset - atmos test --full still runs everything)..github/workflows/test.yml's test job matrix expands to flavor x shard(1..10). TestTerraformRegistryCache now runs once per OS (shard 1 only, guarded by matrix.shard == 1) instead of implicitly once per job. Added a test-required aggregator job (mirrors the existing k3s-required pattern) so branch protection can key off one stable check name regardless of shard count.scripts/collect-coverage.sh writes to a configurable COVERAGE_OUT path and pins -covermode=atomic explicitly. The coverage job now downloads all 10 Linux shard coverage files and hands them to codecov-action in a single call so Codecov aggregates line hits server-side, instead of uploading one Linux-only coverage.out.tests package (no t.Parallel()), run once per OS. Sharding spreads that work across parallel jobs so CI feedback lands in minutes instead of the better part of an hour.coverage.out; this keeps the aggregate coverage number correct once that work is spread across 10 files.Branch protection: no admin action is needed. test-required's matrix check: values (Acceptance Tests (linux), Acceptance Tests (macos), Acceptance Tests (windows)) are the exact same check names the old per-OS test job produced, so it keeps those names live as compatibility aliases - each one only succeeds once every shard for that OS passes, and test-required now also gates on terraform-registry-cache.
</details>
<details> <summary>chore: remove approvers team from CODEOWNERS requirements @johncblandii (#2938)</summary>
@cloudposse/approvers as a required owner from .github/CODEOWNERS — the four patterns
that listed it (**/*.tf, README.yaml, README.md, docs/*.md) now require only
@cloudposse/engineeringrequire_code_owner_review enforced, any PR touching a matching file demands an approval
from the approvers team in addition to engineering review. The bare README.md pattern matches
READMEs anywhere in the tree, so even CI-only changes (e.g. #2934, which updates a README inside
.github/actions/) get blocked on the extra teamapprovers requirement so engineering review alone suffices</details>
<details> <summary>chore: upgrade actions to Node 24 runtime (SHA-pinned) @johncblandii (#2934)</summary>
golangci/golangci-lint-action@4afd733a # v8.0.0 → @ba0d7d2e... # v9.3.0 — safe here since
the workflow uses install-mode: none with a custom-built golangci-lint from a Nov-2025 (v2-era)
commit, which v9 supportscloudposse/.github shared-workflow refs (shared-go-auto-release.yml,
shared-release-branches.yml) from 8244c7c9 # main to current main 49ac8cd5 # main — the old
pin predates cloudposse/.github#261, so release workflows were still running node20 action
versions from the stale snapshotruns.using: node20verify-sha-pinning test suite passes (28/28) over the modified tree, and actionlint is cleanbobheadxi/deployments@648679e8 # v1 — latest release is still node20; no node24 version to pin
https://github.com/bobheadxi/deploymentscloudposse/github-action-seek-deployment@9c18326d # 0.1.1 — node20; runtime bump tracked in
cloudposse/github-action-seek-deployment#29 (needs a maintainer with push access)</details>
<details> <summary>feat(profiles): interactive multi-select for bare --profile @osterman (#2951)</summary>
--profile (no value) now opens an interactive multi-select of every discovered profile, mirroring bare --identity's existing selector, instead of failing with a raw pflag "flag needs an argument" error.NoOptDefVal bare-flag mechanism — previously hardcoded to StringFlag only — to also work for StringSliceFlag, across the flag registry, parser, and preprocessing pipeline.ProfileSelector dependency-injection seam in pkg/config, fulfilled by pkg/flags at init() time, so the interactive picker can be wired in without creating an import cycle (pkg/flags and pkg/profile both already import pkg/config).--profile ci --profile) are always preserved in the final selection. Non-interactive contexts (CI, scripts, no TTY) get a clear, actionable error instead of a confusing parse failure.--profile was a StringSliceFlag, and that flag type never supported the bare-flag sentinel pattern --identity already used — so atmos auth login -i <identity> --profile (expecting an interactive prompt like -i gives) instead errored with a confusing, low-level pflag message.atmos profile list first just to activate one.N/A
</details>
<details> <summary>feat(vendor): add --stack/--labels flags, fix --tags selector bugs @osterman (#1889)</summary>
--stack/-s and --labels selector flags to atmos vendor pull: vendor every component
declared in a stack (or matching stack metadata.labels) that has its own component.yaml,
bypassing vendor.yaml entirely for installation.--tags across all five vendor subcommands (pull, diff, clean, update, verify)
to compose as an independent filter with --component or --stack/--labels, instead of being
mutually exclusive with them — narrows whichever base selector resolved by vendor.yaml-declared
source tags.docs/fixes/2026-08-08-vendor-pull-selector-silent-failures.md):
vendor pull -c <component> --tags <tag> no longer silently exits 0 with nothing installed
when the tag matches a different declared component instead of the named one.--component now reports "not defined" instead of a misleading tags-mismatch
message when --tags also happens to match nothing.-c/--component on vendor pull is now rejected instead of silently keeping only
the last value (--component is now a slice, matching vendor update's flag).--stack/--labels now warns when a resolved component also has a vendor.yaml entry,
surfacing the risk that the two can install different content for the same target.go-git symlink/path
traversal, dompurify XSS, nanoid DoS); the remaining 2 (image-size DoS) have no upstream
patch available yet.--component invocations, and filter that selection further
by declared tags.internal/exec/vendor*.go → pkg/vendor/). While this branch was in flight, origin/main
independently shipped a more complete rewrite of the same internals into pkg/vendoring/
(lockfile, SBOM/provenance, native component-updater PR workflow — #2756). That refactor has
been dropped from this PR to avoid duplicating it; --stack/--labels/--tags are implemented
directly on top of main's current pkg/vendoring/internal/exec architecture.docs/fixes/2026-08-07-vendor-selector-flag-consistency.md — the --tags composition fix and
its design iteration.docs/fixes/2026-08-08-vendor-pull-selector-silent-failures.md — the four bug fixes above.website/blog/2025-12-18-vendor-stack-flag.mdx</details>
<details> <summary>feat(scaffold): dynamic per-combination file generation via matrix @jorrite (#2928)</summary>
spec.files[].matrix for dynamic per-combination file generation in scaffold templates: a file entry declaring matrix: expands into one generated file per combination of one or more axes, reusing the exact shape the workflow matrix: step already uses. when: prunes combinations that don't apply, evaluated once per resolved combination.answers.* referencing an already list-shaped answer, a free-text answer split via any Sprig/Gomplate function (e.g. splitList), or a Go-template expression computing the list from nested/structured answer data.collectKeys template function for computed axes: collectKeys(m) returns m's sorted top-level keys; collectKeys(m, "nestedKey") collects nestedKey's own keys from every value in m, flattened and deduplicated. Registered under its own name so it doesn't shadow Sprig's own keys, and registered in every Go-template FuncMap Atmos builds — not just scaffold templates — so it's available anywhere Sprig/Gomplate functions are (stack configs, locals, store references, toolchain templates, etc)..matrix.<axis> in target:, in when: (via the matrix CEL variable), and in the file's own rendered content.examples/scaffolding-matrix example (one concept: a multiselect field driving a single matrix axis), keeping examples/scaffolding itself matrix-free. Comprehensive testing (all three axis kinds, plus deliberately-wrong inputs) moved to dedicated tests/fixtures/scenarios/scaffold-* fixtures rather than piggybacking on the end-user example.atmos-scaffold/atmos-templates agent skills, the CLI reference docs, and the file-browser plugin so all three are current with matrix/collectKeys.spec.files[].when: gates whether a fixed-count file is generated — it can skip a file, never multiply it. matrix: is the mechanism for producing more than one file from a single entry, reusing conventions already familiar from Atmos workflow matrix: steps and CEL when: conditions. Some axes aren't list-shaped anywhere in the answers themselves — e.g. every region used by any environment — so collectKeys derives that list from nested/structured answer data instead of requiring template authors to hand-roll files outside the template.
Design discussed in https://github.com/orgs/cloudposse/discussions/126. See docs/prd/atmos-scaffold.md's "Dynamic File Generation (matrix)" section for the full behavior/validation/non-goals writeup.
</details>
<details> <summary>feat(auth): add GKE kubeconfig integration @shirkevich (#2937)</summary>
Adds native GKE kubeconfig authentication as an Atmos Auth integration. This is the main-based continuation of #2901 after its dependency, #2790, merged and its source base branch was deleted; GitHub consequently prevents reopening or retargeting the original approved PR.
gcp/gke with required project_id, location, and cluster nameprojects/{project}/locations/{location}/clusters/{name} resource through the native GKE API using Atmos-issued GCPCredentialsatmos gcp gke token as the kubeconfig exec plugin without persisting bearer tokensKUBECONFIG and KUBE_CONFIG_PATH through the Auth identity environmentgcp/project identitiesWhen a component sets auth.require_identity: true, Atmos resolves its default identity when --identity is omitted, requires a successfully provisioned GKE endpoint, and compares it with the effective Kubernetes REST configuration.
The guard applies consistently to every native Helm operation that contacts a Kubernetes cluster:
helm plan and helm diff--against=releasehelm apply / helm deployhelm delete / helm destroyTruly offline paths remain usable without authentication: helm template, --from-manifest, and non-cluster --against=target comparisons. The guard is disabled by default, is GKE-specific, and does not change AWS EKS or Azure AKS behavior.
auth:
integrations:
example-gke:
kind: gcp/gke
via:
identity: example-deployer
spec:
cluster:
name: example-cluster
project_id: example-project
location: us-central1
alias: example
kubeconfig:
update: merge
components:
helm:
example-release:
auth:
require_identity: true
identities:
example-deployer:
default: true
The kubeconfig stores only the GKE endpoint, CA data, and an Atmos exec stanza. It never persists an OAuth bearer token. Cluster discovery and token output require the GCP credential type already produced by Atmos Auth.
The integration does not invoke gcloud, bootstrap Application Default Credentials itself, or require gke-gcloud-auth-plugin. Credentials may come from any configured Atmos GCP identity chain. The token command writes only Kubernetes ExecCredential JSON to stdout and excludes sensitive token material from errors.
The runtime identity needs permission to call container.clusters.get; Kubernetes authorization remains controlled by cluster RBAC.
The implementation was exercised end-to-end against a real regional GKE cluster using genericized evidence recorded in docs/prd/gke-kubeconfig-authentication.md:
atmos auth exec provisioned kubeconfig without preparatory gcloud commandsatmos gcp gke tokengcloud and gke-gcloud-auth-plugin absent from PATHgo test ./pkg/component/helm -count=1go test ./pkg/auth/... -count=1go test ./internal/exec ./pkg/datafetcher -run 'Auth|GKE|GlobalAuth|Schema' -count=1git diff --check origin/main...HEADAll passed after replaying only the GKE commits onto current main. No inherited Azure implementation commits remain in this branch.
#2901 was approved before its base branch was deleted. This replacement retains the same implementation and review fixes, adds the consistent live-plan guard described above, and links the original discussion for provenance.
</details>
<details> <summary>docs(ci): document PR plan comments @osterman (#2939)</summary>
</details>
<details> <summary>feat(toolchain): add update command, fix version-pinning bugs @osterman (#2894)</summary>
atmos toolchain update [tool...] to move a pinned tool to its newest available version and reinstall it, with --dry-run and bounded --max-concurrency. Tools pinned to pr:/sha:/ref: are skipped with an explanation instead of silently left alone.which/exec resolving the wrong version (last token instead of the default first token) on a multi-version .tool-versions line, which caused false "not installed" errors.set appending instead of replacing the default version, contradicting its documented behavior.add/install silently accepting SemVer range syntax (^1.2.0, ~>1.0.0) and only failing later with a raw HTTP 404; now rejected immediately with a hint toward dependencies.tools/atmos version track.atmos version track add/set corrupting any value containing <, >, or & (a json.Marshal HTML-escaping bug), which broke the exact ~>/>= constraint syntax the toolchain docs recommend.atmos toolchain versions --help silently rendering the wrong command's help and exiting 0 instead of erroring; fixed globally in root help routing (atmos <cmd> <bogus-subcommand> --help now errors for every command tree). Removes the stale toolchain-versions and toolchain-aliases docs/casts for commands that were never implemented.list --format/--installed-only/--pending-only, clean --dry-run/--cache-only/--force, exec --dry-run.updateToolVersionsFile writing to the hardcoded default .tool-versions path instead of the configured one.update command.atmos toolchain surfaced that there was no way to update a pinned tool to a newer version, and no clear signal for why range/constraint syntax (^1.2.0, ~>1.0.0) didn't work when the docs implied it should.add <tool>@latest + install --reinstall) reproduced a real crash in which/exec, which led to finding the rest of the bugs above along the way — a documented set behavior that didn't match reality, a JSON-escaping bug corrupting exactly the constraint syntax the toolchain skill doc recommends, and a help-routing bug that let atmos toolchain versions --help silently succeed for a command that doesn't exist (which is also why its docs page and cast looked legitimate despite documenting nothing real).atmos toolchain's docs promised and what the CLI actually did, and give users a real, safe way to move a pinned tool forward.osterman/toolchain-update-pinning-field-test)</details>
<details> <summary>feat(scaffold): add --merge-driver flag to force text-based merging @jorrite (#2925)</summary>
--merge-driver flag (auto / text) to atmos scaffold generate --update and atmos init --update, alongside the existing --merge-strategy flag.auto (default) is today's existing behavior: pick the merger by file extension (YAML-aware for .yaml/.yml, line-oriented text otherwise).text forces every file — YAML included — through the line-oriented diff3 merger, bypassing the YAML-aware re-encode that has no concept of blank lines between blocks and silently drops them on every update, even when nothing meaningful changed.Structure-aware YAML merging is the right default for most files, but it re-encodes the whole document through a YAML parser/serializer, and formatting like blank lines between top-level blocks isn't part of what a YAML parser models. Templates that bundle CI pipeline YAML (a common convention uses blank lines to visually separate jobs/stages) lost that formatting on every --update, whether or not the file actually changed. --merge-driver=text gives users an explicit opt-out, mirroring git's own merge driver concept (auto/text), so this class of file can go through the same merge algorithm git merge itself uses on ordinary text files.
Closes #2886.
</details>
<details> <summary>ci(test): make macOS k3s reliable by fixing the colima timeout budget @arcaven (#2936)</summary>
[k3s-macos] is a required check (via [k3s] demo-helmfile) and flakes on unrelated PRs, costing the full step budget each time and blocking merge. The failure is entirely in CI setup: the job dies at "Start Docker-compatible runtime on macOS" without running a single helm test. Closes #2935.
The colima setup ladder was longer than the step cap that contained it, so the step was guillotined before the ladder could finish, and a status-propagation bug hid which rung actually failed. This PR makes the ladder shorter than its cap instead of growing the cap:
docs/fixes/2026-07-01-macos-k3s-runner-research.md already selected vz for macos-15-intel and records qemu failing there on usernet unable to resolve IP for SSH forwarding before any test ran, and a green run (31723563772) confirms vz starting on attempt 1 with the whole setup step under 6 minutes. The qemu rung (plus its 7-minute brew install qemu cap) was a dead rung that only added minutes to the failure path. Two bounded vz attempts remain as the half-started-VM mitigation.start_colima. status=$? ran after the completed if, which reads the if statement's own zero when no branch executes, so the function returned success after every attempt had failed and the job died later at docker version with a misleading error. The status is now captured in the else branch.docker pull rancher/k3s:latest moves out of the start/retry loop and retries on its own (two independent 5-minute attempts). In the loop, a slow or rate-limited Docker Hub pull counted as a runtime-start failure and forced a full VM delete + rebuild, so registry flakiness masqueraded as hypervisor flakiness.colima status and limactl list capped at 30s so they cannot hang the step). Teardown and backoff run only between attempts; after the final failure the runner is discarded, so cleanup is dead time.Caps on the setup path: brew installs 7m + initial cleanup 1.5m + two vz start/info attempts 10m each + bounded diagnostics and intermediate cleanup ~3m + docker verify 1m + two 5-minute pull attempts with backoff. Every cap hit simultaneously sums to ~43 minutes; the 40-minute cap deliberately undercuts that. The recovery path fits when the final image pull completes normally; anything past 40 is treated as pathological. The observed healthy path is under 6 minutes.
CI-only; no product code changes. The failure mode changes shape: instead of a slow crawl through a dead qemu rung, a runner where vz cannot start now fails hard after two bounded attempts, with diagnostics captured both times.
Pinning the k3s image would need a change to pkg/emulator/driver/k3s.go (the ref is hardcoded there), so this PR keeps :latest to stay CI-only. And macos-15-intel is on GitHub's deprecation path; a longer-term plan for [k3s-macos] is noted in the issue.
</details>
<details> <summary>feat(auth): add Azure AKS/ACR integrations mirroring EKS/ECR @osterman (#2790)</summary>
atmos azure aks token, atmos azure aks update-kubeconfig, and atmos azure acr login, mirroring the existing atmos aws eks/atmos aws ecr integrations.pkg/auth/cloud/kube.KubeconfigManager from AWS-specific to a cloud-agnostic writer shared by EKS and AKS, with a regression suite locking in byte-identical AWS output.IntegrationSpec.Cluster/.Registry schema structs (renamed from EKSCluster/ECRRegistry to Cluster/Registry) so spec.cluster/spec.registry are reused verbatim across aws/eks+azure/aks and aws/ecr+azure/acr — no new per-cloud config keys.website/docs/cli/commands/azure/), a changelog post, a roadmap update, two new agent skills (atmos-azure-aks, atmos-azure-acr), and a PRD documenting the design (docs/prd/azure-aks-acr-integrations.md).google.golang.org/grpc (xDS RBAC auth bypass / HTTP2 rapid-reset bypass), and three transitive website npm packages (fast-uri, svgo, dompurify).kubectl and Docker credentials in one step via atmos auth login. Azure had the same auth foundation (providers, identities) but no equivalent for AKS/ACR, so Azure users still needed the az CLI — and for AAD-enabled clusters, the separate kubelogin binary — outside of Atmos entirely.atmos azure aks token instead of kubelogin; ACR login is a plain OAuth2 token exchange, matching what az acr login does under the hood.docs/prd/azure-aks-acr-integrations.mddocs/prd/eks-kubeconfig.md), ECR authentication PRD (docs/prd/ecr-authentication.md)Exercised end-to-end against a live AAD-enabled AKS cluster (Azure CNI Overlay + Cilium, AAD + Azure RBAC, local accounts disabled) — the live path that PRD Success Metric #2 had previously left to unit tests only. This surfaced, and fixed, a registration gap.
Bug found + fixed. atmos azure aks update-kubeconfig --integration <name> failed with unknown integration kind: azure/aks. The pkg/auth/integrations/azure package self-registers azure/aks and azure/acr in its init(), but nothing blank-imported that package in pkg/auth/manager.go (unlike the aws and github integration packages), so init() never ran and the kinds never registered. The unit suites import the azure package directly, which registered the kinds incidentally and masked the missing production import. Fixed by adding the blank import alongside aws/github.
Integration mode — describe the cluster and write kubeconfig via the Go SDK (no az, no kubelogin):
$ atmos azure aks update-kubeconfig --integration dev/aks
✓ AKS kubeconfig: dev-aks → ~/.config/atmos/kube/config
$ export KUBECONFIG=~/.config/atmos/kube/config
$ kubectl config current-context
dev-aks
$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system cilium-8trqv 3/3 Running 0 134m
kube-system coredns-5d474ff6db-pknhn 1/1 Running 0 132m
kube-system metrics-server-5b879b45fc-5nxzs 2/2 Running 0 129m
...
The kubeconfig Atmos wrote drives its exec plugin through atmos azure aks token (not kubelogin), with --server-id discovered from the cluster (here the well-known AKS AAD server app):
$ kubectl config view --raw -o jsonpath='{.users[0].user.exec.command} {.users[0].user.exec.args}'
atmos [azure aks token --cluster-name aks-dev --resource-group rg-aks-cus \
--server-id 6dae42f8-4368-4678-94ff-3960e28e3630 --subscription-id <redacted> --identity=dev]
auth exec mode — Atmos injects KUBECONFIG into the child process from the integration's Environment() (works even with auto_provision: false, which only suppresses the auto-write on login, not the env composition), so no manual export is needed:
$ atmos auth exec --identity dev -- kubectl get nodes
NAME STATUS ROLES AGE VERSION
aks-system-64934532-vmss000000 Ready <none> 139m v1.35.6
aks-system-64934532-vmss000001 Ready <none> 139m v1.35.6
Both paths mint bearer tokens through atmos azure aks token against the Atmos-managed identity — no az CLI and no kubelogin binary. (ACR login against a live registry remains unit-test-only.)
</details>
<details> <summary>feat(config): auto type inference + provenance/merge bug fixes @osterman (#2897)</summary>
atmos config set and atmos stack set now default --type to auto: infer from the Atmos config schema, then from the type of the value already at the path, falling back to a string (with a warning) only when neither source has an answer. atmos stack set previously never inferred at all — every value was stored as a string unless --type was passed explicitly.PickProvenanceFile (shared by atmos stack set/get/delete/list and the AI/MCP tools layer) always picking the last provenance entry, which for any value defined only in an imported catalog file was a phantom Line:0 entry pointing at the wrong (importing) manifest instead of the file that actually defines the value.MCPSettings.Enabled (a bool tagged omitempty) silently disappearing from the merged config when atmos.yaml and an atmos.d/ fragment both set it to different values, instead of the explicit value winning.<placeholder> (e.g. pass --config <file>.) being silently stripped by the terminal markdown renderer, which parses unescaped angle brackets as inline HTML.--config a.yaml,b.yaml on atmos config get/set/delete/format now warns that only the first file is targeted, instead of silently dropping the rest.atmos config get on a key defined only in an atmos.d/ fragment now hints to check atmos describe config instead of just reporting "not found".unset alias (for config/stack delete) now shows up in --help output, alongside del.atmos config and atmos stack/atmos stack config surfaced these as real, reproducible bugs and gaps — silent type corruption, a provenance-resolution bug that broke edits for the standard catalog-import stack pattern, and a config value that could vanish entirely on merge.</details>
<details> <summary>Add task-runner dependencies, freshness checks, and preconditions to custom commands and workflows @osterman (#2882)</summary>
dependencies.commands/dependencies.workflows to custom commands and workflows: named, parameterized, concurrent-by-default dependency ordering across units, with automatic dedup of identical invocations.inputs/artifacts step fields: skip a step when its declared sources haven't changed since the last successful run (implicit when: checksum.changed), exposing checksum.changed/timestamp.changed/sources/artifacts as when: CEL facts.preconditions step field: skip a step when a required tool is already on PATH (implicit when: "!preconditions.success"), resolved via exec.LookPath — no shell involved. Pluralized (precondition → preconditions) to match the block-of-checks convention already used by inputs/artifacts/dependencies.continue: always step field, mirroring GitHub Actions' continue-on-error: a step's own failure is forgiven, later steps still run, overall exit status unaffected.type: parallel/type: matrix steps silently failing in custom commands (only workflows supported them before).platforms via when: CEL facts (os/arch/platform), native per-command aliases:/internal:, and a values: constraint on flags/arguments with an interactive picker.parallel/matrix, and verbatim CmdLine construction for cmd.exe /C.UnitDependencies string-shorthand schema gap.cmd/custom_command_dependency_adapter.go and cmd/custom_command_values.go into pkg/taskgraph/adapters and pkg/flags respectively, so this logic is unit-testable in isolation instead of coupled to cmd's live command registry.atmos/manifest, config/global, stacks/stack-config) accordingly.Atmos workflows and custom commands already covered most of what a task runner needs, but a handful of real gaps kept teams running go-task alongside Atmos: no dependency ordering between named commands/workflows, no up-to-date checking, no continue-on-error, no precondition shortcut, and custom commands couldn't even use parallel/matrix steps — the exact recipe the project's own go-task migration guide recommends for concurrent dependents. This closes those gaps using the existing when:/CEL condition engine and scheduler rather than inventing a second mechanism.
website/blog/2026-08-05-taskfile-convergence.mdx</details>
<details> <summary>feat(provisioner): Azure (azurerm) backend auto-provisioning @aknysh (#2911)</summary>
Adds automatic provisioning for the azurerm Terraform state backend — the Azure counterpart to the existing S3 backend provisioner. When provision.backend.enabled: true on a component using an azurerm backend, Atmos creates the resource group (if missing), storage account, and blob container before terraform init, with opinionated secure defaults.
Previously, atmos terraform backend create returned create not implemented for backend type: azurerm and provision.backend.enabled silently skipped for Azure.
StorageV2 / Standard_LRS, TLS 1.2 minimum, HTTPS-only, public blob access blockeduse_azuread_auth: trueName + ManagedBy=Atmos tagsNo lock resource is created — the azurerm backend serializes concurrent writes with native Azure Blob Storage blob leases (the DynamoDB / native-S3-locking analog, built into Blob Storage).
create/delete/exists/name into the shared backend registry via init(), so the before.terraform.init hook and atmos terraform backend create/delete pick up azurerm with no wiring changes to the hook or CLI.azureBackendAPI interface hides the ARM SDK pollers behind synchronous methods for testability, mirroring the S3 client factory and the existing azurerm state-reader wrapper. A test-injectable client factory (SetAzureBackendClientFactory/ResetAzureBackendClientFactory) mirrors SetS3ClientFactory.backend block — it is not a valid azurerm backend argument and Terraform would reject it in backend.tf.json.armresources + armstorage SDK deps (azcore/azidentity/azblob were already present).azurerm backend init under Atmos-managed CLI authField-testing the provisioner end-to-end surfaced a pre-existing bug that blocked azurerm backends whenever an Atmos profile was active. For CLI / device-code / interactive auth, Atmos exported both ARM_SUBSCRIPTION_ID and ARM_TENANT_ID to the Terraform subprocess. OpenTofu's azurerm backend authenticates via the Azure CLI and runs az account get-access-token --subscription <id> --tenant <id>, which the CLI rejects with Please specify only one of subscription and tenant, not both. It fails at argument validation — before the CLI even checks the session — so terraform init cannot list existing workspaces or read state at all:
Error: Failed to get existing workspaces: error listing blobs:
AzureCLICredential: ERROR: Please specify only one of subscription and tenant, not both
The tenant is now exported only for OIDC (service-principal / federated) auth, which needs it and does not shell out to the Azure CLI. On the CLI path only ARM_SUBSCRIPTION_ID is exported; the tenant is already fixed by the MSAL session Atmos seeds (and the active subscription), and the azurerm/azapi/azuread providers auto-detect it. oidc.go re-adds the tenant in its OIDC override, so service-principal auth is unchanged.
pkg/auth/cloud/azure/env.go: PrepareEnvironment gates the tenant export on UseOIDC.pkg/auth/providers/azure/oidc.go: OIDC override re-adds ARM_TENANT_ID / AZURE_TENANT_ID.Brings Azure to feature parity with AWS for backend bootstrapping and eliminates the chicken-and-egg problem of needing remote state before Terraform can run — replacing the bespoke cold-start storage-account component teams currently hand-roll on Azure.
The CLI-auth fix is what makes the provisioned backend actually usable under Atmos-managed Azure auth: without it, terraform init against any azurerm backend fails while a profile is active.
docs/prd/azurerm-backend-provisioner.mddocs/fixes/2026-08-11-azurerm-backend-cli-subscription-tenant-conflict.mddocs/prd/s3-backend-provisioner.mdpkg/provisioner/backend/azurerm_test.go, azurerm_wrappers_test.go): table-driven, mocked azureBackendAPI and Azure SDK fake servers — config extraction/precedence, use_azuread_auth parsing, full-create, resource-group reuse, existing-account warning, location-required error, every error path, existence checks, delete safety, registry wiring, and the ARM passthrough wrappers (404→exists mapping, poller completion, error propagation). 95.1% package coverage.pkg/auth/cloud/azure/{env,setup}_test.go, pkg/auth/providers/azure/{cli,device_code,oidc}_test.go): both branches of the tenant gate verified — omitted for CLI/device-code/interactive, present for OIDC. env.go and oidc.go PrepareEnvironment are both 100% covered.go build ./..., go vet, gofmt, and all pre-commit hooks (go-fumpt, golangci-lint, go.mod tidy) pass.[!NOTE] The auto-provisioned account uses secure-but-simple defaults (
Standard_LRS, Microsoft-managed keys, public network access with Entra ID/RBAC gating) intended for dev/test/bootstrap — not production. For production, import the resources into a managed module (e.g.Azure/avm-res-storage-storageaccount); the provisioner is idempotent, soprovision.backend.enabled: truecan be left in place.
</details>
<details> <summary>fix(ai): close DX gaps found in atmos ai field test @osterman (#2903)</summary>
atmos ai skill update [name], a new command that compares each installed bundled skill's recorded version against the catalog embedded in the running binary and reinstalls only the ones that are actually outdated — closes the "no update command" gap the fixes below originally left deferred. See the blog post for the full story.compatibility.atmos version-compatibility gate for bundled and multi-skill Git package skill installs, not just single-skill Git clones (it was previously skipped entirely for those two paths).atmos ai skill install/uninstall/update --client values instead of silently no-op'ing, by extending pkg/flags's WithValidValues to work on string-slice flags generically (this also fixed a latent bug where WithValidValues was silently dead for every command that binds flags via BindFlagsToViper without calling the full Parse() pipeline).--path is combined with --client/--scope/--global/--all-clients on skill install, since --path skips auto-distribution and those flags are otherwise silently ignored.skill list --detailed, and flags when an installed skill has a newer catalog version available (using the same comparison update now acts on).agent-skills/skills/atmos-ai/SKILL.md doc drift (it never documented skill install at all) and removes a phantom info subcommand from atmos ai skill --help.file:// support to skill source parsing and the downloader.--scope/--global precedence on skill install/uninstall/update.atmos ai exec/ask --session actually persist and resume conversations — previously a documented flag that was a complete no-op.Model from the constructed AI client instead of an independent config lookup, fixing sessions export/import for the default zero-config claude-code provider path (previously exported checkpoints for that path could never be re-imported).--mcp server filtering for CLI providers (claude-code/codex-cli/copilot-cli/gemini-cli) too — it was silently ignored, so all configured MCP servers were always passed through regardless of the flag.--format values on ai exec instead of silently falling back to text.ai exec can now return exit code 2 for a genuine infrastructure-level tool failure (e.g. an unregistered tool) immediately, without waiting on the 25-iteration tool-call loop to exhaust as it did before.sessions clean --older-than 0d now deletes all sessions immediately, distinguished from the flag not being passed at all (which still defaults to 30 days); negative durations are now a hard parse error instead of silently falling back to the default.js-yaml (GHSA-5p4m-2wfm-xmqj, quadratic CPU consumption in !!omap resolution) and mermaid (5 advisories), via pnpm.overrides bumps within their existing major versions. No CodeQL alerts were open.TestManager_ExportSession_WarnsOnUnimportableCheckpoint CI failure: the test asserted on raw ANSI-styled ui.Warning() output, which the formatter renders as two adjacent styled runs under CI=true — same visible text, different byte layout, so the test passed locally and failed in CI. Strips ANSI before asserting on content now.atmos ai command surface — reading the real implementation, hypothesizing plausible misuse an automated test wouldn't catch, and executing for real against isolated fixtures — rather than a spec change or feature request. Most are silent DX gaps (a flag that looks like it works but doesn't, an error with no way forward, a validation check that only applies on some of the paths that need it).0d instead of doing what it says is a footgun in the other direction (a user who deliberately asks to delete everything gets nothing, silently).atmos ai skill update exists because, once asked, leaving "no update command" as a documented gap wasn't the right call — bundled skills going stale after a binary upgrade is exactly the kind of silent drift this whole PR is about fixing elsewhere.atmos ai skill update command that was initially scoped out and then built once asked for.</details>
<details> <summary>feat(ai): browsable, searchable Agent Skills Directory @osterman (#2881)</summary>
/ai/skills, replacing the hand-maintained (and drifted) skill table on the Agent Skills doc page.file-browser Docusaurus plugin with category grouping, a search box, configurable card icon/CTA label, and a "Copy as Markdown" button, reused for the new skills instance.SKILL.md and every nested reference file into one clipboard-ready document, so its full context can be grabbed without installing it.atmos ai skill list gains a --format flag (table/json/yaml/csv/tsv) and a Category column.SkillCount component that renders the live, build-time skill count inline in prose (homepage AISection, docs), so counts can't drift out of date again.Atmos AI → Skills category with Agent Skills, Skill Marketplace, and a link to the new directory) and cleans up a duplicate "Native CI" sidebar/doc link.SKILL.md files surfaced by the affected-file validator./blog/agent-skills-directory/ai/skills, /ai/agent-skills</details>
<details> <summary>fix(kubernetes): single-file GitOps delivery and Kustomize metadata.name exemption @osterman (#2874)</summary>
kubernetes.gitops.provision.targets.<name> (kind: git) now supports a split tri-state: split: false writes path as a single merged multi-document YAML file instead of always treating path as a directory of auto-named files; unset infers the mode from whether path's last segment looks like a manifest filename (.yaml/.yml/.json).metadata.name on Kustomize's own Kustomization/Component objects (matched against sigs.k8s.io/kustomize/api/types's own kind/version constants), since Kustomize's own schema and field-enforcement never require one.validate: false component-level flag opts a component out of both the apply/deploy structural auto-gate and the standalone atmos kubernetes validate command.split documented on kubernetes-deploy.mdx, and the Kustomize exemption / validate: false documented on kubernetes-validate.mdx.path was always treated as a directory, so configuring path: ".../kustomization.yaml" created a directory by that name containing an auto-generated file inside it, instead of the exact file Kustomize's remote-include mechanism requires.metadata.name unconditionally, forcing users to add a meaningless name to Kustomize Component/Kustomization objects just to satisfy Atmos, even though Kustomize's own tooling never requires one.!terraform.state) and committing it to a deployment repo as a proper kustomization.yaml for Argo CD/Flux to consume.</details>
<details>
<summary>feat(toolchain): support Aqua github_archive package type @osterman (#2416)</summary>
github_archive package type to the Aqua-compatible toolchain registry parser and installer.https://github.com/{owner}/{repo}/archive/refs/tags/{version}.tar.gz, matching upstream aquaproj/aqua semantics.tar.gz (mirroring aqua's GetFormat()); asset, url, format, and format_overrides are intentionally ignored for this type.resetByPkgType so version overrides that switch a tool to github_archive clear stale asset/url.adr-tools example; cover validation, version-prefix handling, format-ignored semantics, URL pattern, and {{trimV .Version}}/path template idiom.github_archive for tools shipped as repository source archives (e.g., adr-tools, tfenv, tgswitch, and many single-script projects). Without this type, those entries failed with unsupported tool type: github_archive.</details>
<details> <summary>fix(schemas): accept documented backend types and fields the manifest schema rejected @osterman (#2953)</summary>
consul, cos, http, kubernetes, oss, pg backend types to the stack-manifest JSON Schema's backend_type/remote_state_backend_type enums and backend_manifest.properties allow-list, across all three hand-maintained schema copies (embedded, stack-config, and the test fixture).terraform.overrides.{hooks,generate,secrets,auth,retry,required_providers,required_version}, component-level retry: (terraform/helmfile/packer/kubernetes), component-level required_version/required_providers, source.ttl, and container_runtime.provider: "auto"."raw" from workflow_step.output.mode's enum — the schema accepted it but Go's validateParallelOutput never did, so it passed validation and then failed at execution time.oneOf bug that made workflows: and ordinary stack fields (vars:, settings:, etc.) mutually exclusive in one manifest, producing an uninformative (root): valid against schemas at indexes 0 and 1 error.internal/exec/stack_processor_backend.go) that errors when backend_type/backend (or remote_state_backend_type/remote_state_backend) don't match, instead of silently resolving to an empty backend config.pkg/datafetcher) and the CLI level (new fixture at tests/fixtures/scenarios/manifest-schema-coverage/ + tests/test-cases/manifest-schema-coverage.yaml, run through the real binary).atmos describe stacks (and anything that calls it, including terraform plan and custom commands) hard-rejects a backend_type: http manifest even though http is a real, generic Terraform/OpenTofu backend (e.g. GitLab-managed state) that Atmos's own docs already claim to support — closes #2919.describe stacks has always run schema validation, but a prior unrelated fix (PR #2749, 2026-07-15) corrected a bug that had silently no-op'd that validation whenever schemas.atmos.manifest was unconfigured (the default). Once validation actually started running, this pre-existing enum gap — and, as a follow-up field test found, several siblings in the same bug class — became hard, user-visible failures.oneOf fix and the backend key-mismatch check close two related, previously-silent failure modes surfaced by the same investigation, rather than leaving known gaps for the next person to rediscover.http as a valid backend_type for the same issue. This PR covers that same schema change (http in backend_type/remote_state_backend_type and backend_manifest.properties) plus 5 more missing backend types, all 3 hand-maintained schema copies (#2920 updated 2 of 3), and several independent schema/validation bug classes found via a follow-up field test. Thanks to @MacherelR for the original report and fix — closing #2920 in favor of this broader pass; will fold in the HTTP-backend documentation from that PR separately.docs/fixes/2026-08-11-manifest-schema-missing-backend-types.md</details>
<details> <summary>fix(schema): model required_providers/retry/Helm in atmos-manifest @osterman (#2950)</summary>
required_version, required_providers, and retry to the terraform, terraform_component_manifest, and shared overrides definitions in the atmos-manifest JSON Schema.generate to the stack-level kubernetes definition (same drift class, found while auditing for other instances).helm, helm_repository, helm_components, helm_component_manifest), closing the previously-tracked topLevel:helm gap.pkg/datafetcher/schema_section_coverage_test.go: required_version, required_providers, and retry were explicitly exempted from the schema-coverage guard with the comment "introspected from Terraform, not authored" — factually wrong, since all three are user-authored fields with full stack-processor support. This is why the guard never caught the original gap.tests/fixtures/schemas/atmos/atmos-manifest/1.0/atmos-manifest.json, and extend the atmos-stacks-validation fixture with real usage of every fixed field so TestValidateStacksCmd_Success is a live regression guard for this bug class.atmos validate stacks (broken since v1.224.0) and atmos describe stacks (broken since v1.225.0) reject required_version/required_providers under components.terraform.<name>, even though the fields are fully implemented and documented (added by #1841).required_version/required_providers were added to the legacy stack-config schema by #1841, but never ported to atmos-manifest, the schema actually enforced by validate/describe. That drift stayed invisible for months because a separate bug (fixed by #2749) had been silently skipping schema validation whenever schemas.atmos.manifest wasn't explicitly configured — the common case. Once #2749 fixed that wiring bug, the pre-existing drift became a hard regression for any user setting these fields.additionalProperties: false rejection pattern is the root cause behind #2919 (backend_type: http, fix open in #2920) and #2104 (depends_on_manifest.stack, fix open in #2835). Auditing for the same pattern surfaced the kubernetes.generate and native-Helm gaps fixed here.required_version/required_providers/retry as non-manifest ("introspected, not authored") let this exact regression through undetected. Fixing the classification, not just the schema, closes the actual hole.backend_type: http), #2104 / #2835 (depends_on_manifest.stack) — same bug class, separate PRs already open for those</details>
<details>
<summary>fix(docker): build the arm64 image with an arm64 userland @arcaven (#2932)</summary>
This makes the linux/arm64 image you already publish run on arm64 hardware,
instead of failing at startup with exec format error. The arm64 image has
shipped an amd64 userland since it was first added, so this closes the gap between
the advertised multi-arch manifest and what arm64 users actually receive. The
change is one line and additive, plus a guard so it cannot silently regress.
--platform=$BUILDPLATFORM pin on the runtime FROM so the Debian
base and all apt-installed tools follow TARGETPLATFORM.linux/arm64 image contained an amd64 userland and failed with
exec format error on arm64 hardware. Only atmos and kustomize were
arm64, and they were stranded in an amd64 rootfs with no aarch64 loader.</details>
<details> <summary>fix(git): tolerate config errors for CI git-clone bootstrap pre-Cobra @osterman (#2879)</summary>
atmos git clone failing before it ever attempts a clone in a fresh CI workspace, when a referenced config profile doesn't exist yet (e.g. ATMOS_PROFILE=github with no .atmos/profiles/ checked out) — ATMOS_CI=true had no effect on this failure.pkg/container's build-arg builder covering engine, driver, cache, custom dockerfile/context, and tags together in one config (previously only tested individually).cmd/root.go's Execute() runs an initial cfg.InitCliConfig before Cobra resolves any subcommand. Only the second InitCliConfig call (inside PersistentPreRun) knew how to tolerate the CI git-clone bootstrap's expected missing config (applyCIGitCloneBootstrap). The first call's error handler had no such tolerance, so a profile not found error aborted the process before Cobra — and therefore before PersistentPreRun — ever ran, regardless of ATMOS_CI.isCIGitCloneBootstrapArgs (an os.Args-based equivalent of the existing Cobra-aware bootstrap check) to the pre-Cobra handler, and a new exported CIGitCloneModeRequestedFromEnv in cmd/git so both code paths defer to the same ATMOS_CI/CI-provider resolution logic.buildBuildArgs coverage: individual fields (driver, cache, tags, custom dockerfile/context) each had their own case, but nothing asserted they all survive together in a single build.</details>
<details> <summary>fix(helm): native Helm UX fixes (repo isolation, status output, default identity, namespace) @aknysh (#2941)</summary>
Four independent fixes to the native Helm implementation (pkg/component/helm):
1. Repository config/cache isolation. newSettings now points Helm's RepositoryConfig and
RepositoryCache at an atmos-managed XDG location (<xdg-config>/atmos/helm/repositories.yaml,
<xdg-cache>/atmos/helm/repository) unless HELM_REPOSITORY_CONFIG / HELM_REPOSITORY_CACHE is set,
instead of inheriting the user's global Helm config.
2. Status output on apply/delete. atmos helm apply and atmos helm delete now print a one-line
status (release name, namespace, chart) instead of succeeding silently.
3. Stack default-identity resolution. atmos helm apply/diff/delete resolve the stack's
default: true identity binding the same way atmos terraform does, so an explicit --identity is
no longer required for cluster operations. The offline template render never triggers auth.
4. Namespace for namespace-less charts. newActionContext now sets the namespace on the Helm
EnvSettings (SetNamespace), so charts whose manifests omit metadata.namespace install into the
component's configured namespace instead of the kubeconfig-default namespace.
1. Because settings inherited the user's global Helm config, resolving a declared repo/name
chart sent Helm down downloader.(*ChartDownloader).scanReposForURL, which iterates every repository
in the user's global repositories.yaml and fails on the first one whose index is not cached
(e.g. no cached repo found ... <repo>-index.yaml). An unrelated repository in the user's global
config could break an atmos chart render, and setupHelmRepositories also mutated the user's global
config. Isolation makes chart resolution depend only on the repositories the components declare, keeps
it reproducible across workstations/CI, and mirrors how the kubeconfig is already isolated under the
atmos XDG dir.
2. A successful apply/delete produced no output, so there was no confirmation of what happened
(release, namespace, chart) without separately querying the cluster. template/diff already emit
their own output; apply/delete now do too.
3. The helm exec path set up auth only when an explicit identity was given, so without --identity
no auth manager was created, no KUBECONFIG was injected, and the command could not reach the cluster.
Terraform/helmfile already auto-resolve the stack default identity; helm now matches them for cluster
operations while keeping template fully offline. When no auth is configured, the identity stays empty
and the ambient KUBECONFIG is used, preserving prior behavior.
4. Helm derives the namespace for namespace-less objects from the settings/RESTClientGetter,
which atmos left at the kubeconfig context default; only the install action's namespace was set. Charts
that hardcode namespace: {{ .Release.Namespace }} worked, but charts that do not landed in default.
pkg/component/helm)repo_isolation_test.go - isolation is applied when the HELM_REPOSITORY_* env vars are unset;
explicit values are respected unchanged.status_output_test.go - a status line is written for apply/delete on success only (silent on error
and for template/diff), and the message names the release and namespace.default_identity_test.go - the decision logic (shouldSetupComponentAuth, operationRequiresCluster),
plus an executor test asserting a cluster operation resolves component auth with no explicit identity
while template stays offline.namespace_test.go - newActionContext sets the settings namespace; an empty namespace leaves Helm's
default untouched.New functions are covered at 100%; package total is ~89.6%. gofmt and go vet are clean, and the full
module builds. TestMain initializes the data writer once for the package since apply/delete now emit
output.
Built a binary and deployed two native Helm components: one local chart (files in the repo) and one chart pulled from a public Helm repository.
--identity, resolving the stack's default identity.default.docs/fixes/2026-08-14-native-helm-ux-fixes.md</details>
<details> <summary>fix(secret): inherit the component's default identity for stores @jaguer0 (#2746)</summary>
atmos secret (set/get/init/validate) now inherits the component's effective identity for store-backed secrets whose store declares no explicit identity:, instead of falling back to the default AWS credential chain (→ EC2 IMDS, which fails off-EC2).injectSecretStoreAuthResolver (cmd/secret/shared.go) called atmosConfig.Stores.SetAuthContextResolver(resolver), which passes an empty identity to every store, so an identity-less store fell back to the AWS default chain → EC2 IMDS and failed off-EC2 (e.g. no EC2 IMDS role found ... dial tcp 169.254.169.254:80: connect: host is down).cmd/terraform/utils.go, internal/exec/terraform_execute_helpers.go) already call SetAuthContextResolverWithDefaultIdentity; the secret CLI even computed the same DefaultIdentity (into SecretsAuth) but never applied it to the stores.website/docs/cli/configuration/secrets.mdx: "When omitted and the secret is resolved within a component scope, the component's effective identity is inherited."identity, and an explicit --identity, are unaffected (defaultIdentityForStore only fills empty-identity stores). atmos terraform and atmos secret list behavior is unchanged.Suggested label: patch (user-visible bug fix, no new surface; no blog/roadmap required).
docs/fixes/2026-07-13-secret-cli-inherit-default-identity.md</details>
<details> <summary>fix(merge): resolve deferred YAML functions losing data on merge (#2888) @osterman (#2892)</summary>
Fixes #2888 — deferred YAML functions silently losing data on merge
ApplyDeferredMerges passed processor = nil, so deferred YAML
functions (!template, !terraform.output, !terraform.state, !store, !exec, !env) were
never actually resolved-and-merged — they silently lost data whenever a concrete value at another
config layer collided with them. On top of that, !labels/!tags/!labels.keys/!labels.values
weren't in the defer list at all, which is the literal scenario reported in the issue.internal/exec/deferred_contexts.go, plus changes across
internal/exec/stack_processor_*.go, internal/exec/yaml_processor.go,
internal/exec/yaml_func_tags.go, pkg/merge/deferred.go, pkg/merge/merge_yaml_functions.go)
that resolves deferred functions per-invocation (auth- and template-context-aware) and deep-merges
the result against any concrete override at the same path — including the mirror-precedence
direction (a concrete value at a lower-precedence layer than the function), which the original
design didn't handle.ApplyDeferredMerges
now processes deferred paths ancestor-before-descendant, so a descendant leaf can never be
clobbered by a later wholesale replace of its ancestor map (see
docs/fixes/2026-08-07-deferred-merge-nested-function-collision.md).Fixes a double-execution regression introduced by the Stage 3 pass
--process-functions=true, the
document-wide ProcessCustomYamlTags pass already resolves each surviving function, and Stage 3
then re-resolved every deferredNote truncated.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merge
This is a feature preview based on an open pull request. It is intended for testing artifacts and validating functionality before the feature is merged.
[!WARNING] This release is temporary and may be removed at any time without notice.
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
fix(helm): native Helm UX fixes (repo isolation, status output, default identity, namespace) @aknysh
<details> <summary>fix(helm): native Helm UX fixes (repo isolation, status output, default identity, namespace) @aknysh (#2941)</summary>
Four independent fixes to the native Helm implementation (pkg/component/helm):
1. Repository config/cache isolation. newSettings now points Helm's RepositoryConfig and
RepositoryCache at an atmos-managed XDG location (<xdg-config>/atmos/helm/repositories.yaml,
<xdg-cache>/atmos/helm/repository) unless HELM_REPOSITORY_CONFIG / HELM_REPOSITORY_CACHE is set,
instead of inheriting the user's global Helm config.
2. Status output on apply/delete. atmos helm apply and atmos helm delete now print a one-line
status (release name, namespace, chart) instead of succeeding silently.
3. Stack default-identity resolution. atmos helm apply/diff/delete resolve the stack's
default: true identity binding the same way atmos terraform does, so an explicit --identity is
no longer required for cluster operations. The offline template render never triggers auth.
4. Namespace for namespace-less charts. newActionContext now sets the namespace on the Helm
EnvSettings (SetNamespace), so charts whose manifests omit metadata.namespace install into the
component's configured namespace instead of the kubeconfig-default namespace.
1. Because settings inherited the user's global Helm config, resolving a declared repo/name
chart sent Helm down downloader.(*ChartDownloader).scanReposForURL, which iterates every repository
in the user's global repositories.yaml and fails on the first one whose index is not cached
(e.g. no cached repo found ... <repo>-index.yaml). An unrelated repository in the user's global
config could break an atmos chart render, and setupHelmRepositories also mutated the user's global
config. Isolation makes chart resolution depend only on the repositories the components declare, keeps
it reproducible across workstations/CI, and mirrors how the kubeconfig is already isolated under the
atmos XDG dir.
2. A successful apply/delete produced no output, so there was no confirmation of what happened
(release, namespace, chart) without separately querying the cluster. template/diff already emit
their own output; apply/delete now do too.
3. The helm exec path set up auth only when an explicit identity was given, so without --identity
no auth manager was created, no KUBECONFIG was injected, and the command could not reach the cluster.
Terraform/helmfile already auto-resolve the stack default identity; helm now matches them for cluster
operations while keeping template fully offline. When no auth is configured, the identity stays empty
and the ambient KUBECONFIG is used, preserving prior behavior.
4. Helm derives the namespace for namespace-less objects from the settings/RESTClientGetter,
which atmos left at the kubeconfig context default; only the install action's namespace was set. Charts
that hardcode namespace: {{ .Release.Namespace }} worked, but charts that do not landed in default.
pkg/component/helm)repo_isolation_test.go - isolation is applied when the HELM_REPOSITORY_* env vars are unset;
explicit values are respected unchanged.status_output_test.go - a status line is written for apply/delete on success only (silent on error
and for template/diff), and the message names the release and namespace.default_identity_test.go - the decision logic (shouldSetupComponentAuth, operationRequiresCluster),
plus an executor test asserting a cluster operation resolves component auth with no explicit identity
while template stays offline.namespace_test.go - newActionContext sets the settings namespace; an empty namespace leaves Helm's
default untouched.New functions are covered at 100%; package total is ~89.6%. gofmt and go vet are clean, and the full
module builds. TestMain initializes the data writer once for the package since apply/delete now emit
output.
Built a binary and deployed two native Helm components: one local chart (files in the repo) and one chart pulled from a public Helm repository.
--identity, resolving the stack's default identity.default.docs/fixes/2026-08-14-native-helm-ux-fixes.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Nothing published for this version
And macos-15-intel is on GitHub's deprecation path; a longer-term plan for [k3s-macos] is noted in the issue.
<details> <summary>feat(toolchain): add update command, fix version-pinning bugs @osterman (#2894)</summary>
atmos toolchain update [tool...] to move a pinned tool to its newest available version and reinstall it, with --dry-run and bounded --max-concurrency. Tools pinned to pr:/sha:/ref: are skipped with an explanation instead of silently left alone.which/exec resolving the wrong version (last token instead of the default first token) on a multi-version .tool-versions line, which caused false "not installed" errors.set appending instead of replacing the default version, contradicting its documented behavior.add/install silently accepting SemVer range syntax (^1.2.0, ~>1.0.0) and only failing later with a raw HTTP 404; now rejected immediately with a hint toward dependencies.tools/atmos version track.atmos version track add/set corrupting any value containing <, >, or & (a json.Marshal HTML-escaping bug), which broke the exact ~>/>= constraint syntax the toolchain docs recommend.atmos toolchain versions --help silently rendering the wrong command's help and exiting 0 instead of erroring; fixed globally in root help routing (atmos <cmd> <bogus-subcommand> --help now errors for every command tree). Removes the stale toolchain-versions and toolchain-aliases docs/casts for commands that were never implemented.list --format/--installed-only/--pending-only, clean --dry-run/--cache-only/--force, exec --dry-run.updateToolVersionsFile writing to the hardcoded default .tool-versions path instead of the configured one.update command.atmos toolchain surfaced that there was no way to update a pinned tool to a newer version, and no clear signal for why range/constraint syntax (^1.2.0, ~>1.0.0) didn't work when the docs implied it should.add <tool>@latest + install --reinstall) reproduced a real crash in which/exec, which led to finding the rest of the bugs above along the way — a documented set behavior that didn't match reality, a JSON-escaping bug corrupting exactly the constraint syntax the toolchain skill doc recommends, and a help-routing bug that let atmos toolchain versions --help silently succeed for a command that doesn't exist (which is also why its docs page and cast looked legitimate despite documenting nothing real).atmos toolchain's docs promised and what the CLI actually did, and give users a real, safe way to move a pinned tool forward.osterman/toolchain-update-pinning-field-test)<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
toolchain update for selected or all tools, with dry-run and concurrency controls.toolchain lock to verify artifacts and create lock entries without installation.toolchain uninstall --all.Bug Fixes
Documentation
<details> <summary>feat(scaffold): add --merge-driver flag to force text-based merging @jorrite (#2925)</summary>
--merge-driver flag (auto / text) to atmos scaffold generate --update and atmos init --update, alongside the existing --merge-strategy flag.auto (default) is today's existing behavior: pick the merger by file extension (YAML-aware for .yaml/.yml, line-oriented text otherwise).text forces every file — YAML included — through the line-oriented diff3 merger, bypassing the YAML-aware re-encode that has no concept of blank lines between blocks and silently drops them on every update, even when nothing meaningful changed.Structure-aware YAML merging is the right default for most files, but it re-encodes the whole document through a YAML parser/serializer, and formatting like blank lines between top-level blocks isn't part of what a YAML parser models. Templates that bundle CI pipeline YAML (a common convention uses blank lines to visually separate jobs/stages) lost that formatting on every --update, whether or not the file actually changed. --merge-driver=text gives users an explicit opt-out, mirroring git's own merge driver concept (auto/text), so this class of file can go through the same merge algorithm git merge itself uses on ordinary text files.
Closes #2886.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
--merge-driver to initialization and scaffold generation commands.auto for YAML-aware merging or text for line-oriented merging that preserves formatting.Documentation
Chores
<details> <summary>ci(test): make macOS k3s reliable by fixing the colima timeout budget @arcaven (#2936)</summary>
[k3s-macos] is a required check (via [k3s] demo-helmfile) and flakes on unrelated PRs, costing the full step budget each time and blocking merge. The failure is entirely in CI setup: the job dies at "Start Docker-compatible runtime on macOS" without running a single helm test. Closes #2935.
The colima setup ladder was longer than the step cap that contained it, so the step was guillotined before the ladder could finish, and a status-propagation bug hid which rung actually failed. This PR makes the ladder shorter than its cap instead of growing the cap:
docs/fixes/2026-07-01-macos-k3s-runner-research.md already selected vz for macos-15-intel and records qemu failing there on usernet unable to resolve IP for SSH forwarding before any test ran, and a green run (31723563772) confirms vz starting on attempt 1 with the whole setup step under 6 minutes. The qemu rung (plus its 7-minute brew install qemu cap) was a dead rung that only added minutes to the failure path. Two bounded vz attempts remain as the half-started-VM mitigation.start_colima. status=$? ran after the completed if, which reads the if statement's own zero when no branch executes, so the function returned success after every attempt had failed and the job died later at docker version with a misleading error. The status is now captured in the else branch.docker pull rancher/k3s:latest moves out of the start/retry loop and retries on its own (two independent 5-minute attempts). In the loop, a slow or rate-limited Docker Hub pull counted as a runtime-start failure and forced a full VM delete + rebuild, so registry flakiness masqueraded as hypervisor flakiness.colima status and limactl list capped at 30s so they cannot hang the step). Teardown and backoff run only between attempts; after the final failure the runner is discarded, so cleanup is dead time.Caps on the setup path: brew installs 7m + initial cleanup 1.5m + two vz start/info attempts 10m each + bounded diagnostics and intermediate cleanup ~3m + docker verify 1m + two 5-minute pull attempts with backoff. Every cap hit simultaneously sums to ~43 minutes; the 40-minute cap deliberately undercuts that. The recovery path fits when the final image pull completes normally; anything past 40 is treated as pathological. The observed healthy path is under 6 minutes.
CI-only; no product code changes. The failure mode changes shape: instead of a slow crawl through a dead qemu rung, a runner where vz cannot start now fails hard after two bounded attempts, with diagnostics captured both times.
Pinning the k3s image would need a change to pkg/emulator/driver/k3s.go (the ref is hardcoded there), so this PR keeps :latest to stay CI-only. And macos-15-intel is on GitHub's deprecation path; a longer-term plan for [k3s-macos] is noted in the issue.
</details>
One column per quarter.