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 12 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Some releases are documented
notes for 32 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
2417 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
feat: add test steps, build controls, and default CLI help @osterman
<details> <summary>feat: add test steps, build controls, and default CLI help @osterman (#3124)</summary>
Add type: test to workflows, custom commands, and lifecycle hooks with continuation by default, parallel/matrix checks, existing failure policies, buffered failures/all output, and isolated concurrent state
Add themed test trees with status dots, leaf progress, durations, immediate failure logs, and CI output; update schemas, documentation, tests, the roadmap, and a custom-command example with a recorded cast and success announcement
Implement live output viewports for shell/Atmos commands, including sizing and horizontal padding; use a four-line padded window labeled Compiling for builds and add --no-cache
Make bare atmos display help without requiring stacks and suppress duplicate error boxes for already-reported custom-command test failures
Bundle an atmos-tests agent skill with HTTP, script/interpreter, shell, require, parallel/dependency, matrix, and post-deployment hook patterns
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
test workflow steps with progress reporting, pass/fail summaries, parallel and matrix checks, retries, and configurable failure handling.--no-cache support for builds to force recompilation without clearing shared caches.atmos without a subcommand now displays usage and available commands.Bug Fixes
Documentation
Nothing published for this version
chore(deps): add 14-day cooldown for Renovate updates @osterman
<details> <summary>chore(deps): add 14-day cooldown for Renovate updates @osterman (#3135)</summary>
minimumReleaseAge: "14 days" cooldown to renovate.json.floci/floci and floci/floci-az Docker digest bumps) the moment a new release/digest was published, with no waiting period.cooldown.default-days: 14 already set for every ecosystem in .github/dependabot.yml, so cooldown policy is consistent regardless of which bot opens the PR.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>feat(website): add download/share to blog post cast embeds @osterman (#3126)</summary>
CastEmbed component (website/src/components/CastEmbed/) that wraps CastPlayer with the existing CastShareLink and CastProDownload controls, on by default.siteCastPath() helper to CastProArtifact/url.mjs (with a unit test) that resolves a cast's public src to its committed website/static/... path, replacing an inline convention previously duplicated only in the file-browser example pages.website/blog/ from bare <CastPlayer> to <CastEmbed>, so every previously published changelog post's cast embed also gets Download/Share.changelog, atmos-asciicast, and pull-request skills to reference CastEmbed (with opt-out guidance via download={false}/share={false}) instead of bare CastPlayer for future blog posts.CastProDownload/CastShareLink) already existed and was wired into the examples-gallery pages.CastEmbed component avoids every blog post (and future skill guidance) re-deriving the owner/repo/gitRef/path wiring by hand.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Documentation
<details> <summary>ci: add sticky cross-workflow timing summary @osterman (#3125)</summary>
workflow_run coordinator for every workflow that can run on an open pull request.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Documentation
<details> <summary>ci: shard race detector tests across hosted runners @osterman (#3123)</summary>
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Performance
Reliability
Maintenance
<details> <summary>feat(helm): add runtime value overrides and values output @osterman (#3094)</summary>
-f/--values and --set* overrides to native Helm render, diff, and apply commands.atmos helm values <component> -s <stack> to print final masked values as formatted YAML.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
atmos helm values to display fully resolved chart values as masked YAML.--set, --set-string, --set-file, --set-json, and --set-literal.Bug Fixes
Documentation
<details> <summary>fix(ci): cap concurrent subprocess launches in acceptance test orchestration @osterman (#3116)</summary>
maxConcurrentSubprocesses = 4) in internal/ci/acceptance/command.go that caps how many real subprocesses (go build/go test -c/go test/precompiled *.test.exe) commandRunner.run/.output may have in flight at once, across every commandRunner instance.testfixture_test.go's buildFixtureTestBinary to route its go test -c compile through commandRunner.output instead of a bare exec.Command, so it shares the same cap.fatal error: found pointer to free object (runtime: marked free object in span) during a concurrent os/exec process launch triggered from this package's own acceptance-test suite.t.Parallel() subtests, many of which shell out to the real go toolchain. On a wide CI runner that lets dozens of real go build/go test subprocesses launch fully concurrently — each independently allocating and syscalling heavily — which is the kind of condition known to trigger a long-standing, still-recurring class of Go runtime GC/allocator race on Windows (see golang/go#44900, #45364, #47415, #54247). It's a documented class of upstream Go runtime flakiness under heavy concurrent allocation+syscall pressure, not a bug in the specific command being run.go test ./internal/ci/acceptance/... -v still passes in full (~15s, no deadlocks) with the cap in place.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Tests
Documentation
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>fix(docs): use localhost redis URL in sops-secrets demo cast @osterman (#3120)</summary>
sops-secrets example's secret-lifecycle screengrab demoed atmos secret set REDIS_URL=redis://prod:6379 --stack=dev --component=api.redis://localhost:6379, matching the fixture component's own default (redis_url: !secret REDIS_URL | default "redis://localhost:6379").website/static/casts/examples/sops-secrets/secret-lifecycle.cast) via atmos --chdir=demo/casts casts generate examples sops-secrets secret-lifecycle, which re-runs its own validation step.dev stack demo was setting an obviously production-looking Redis URL (redis://prod:6379), which is confusing/embarrassing in published docs and contradicts the stack it's demoing against.redis://localhost:6379 keeps the demo internally consistent with the fixture's real default for the dev stack.<!-- 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: describe/error/prompt DX bugs found while field-testing aws/cloudformation @osterman (#3106)</summary>
Four general, cross-cutting bug fixes:
describe component couldn't prompt for a missing --stack; it used Cobra's native MarkPersistentFlagRequired, which hard-fails before the interactive-prompt code ever runs.components["terraform"] (so any non-terraform component always matched zero stacks and fell back to an unfiltered, org-wide list), and the flag prompt ran before the positional-arg prompt, so the filter never saw the component name even when one had already been typed.filterEmptySections treated "no per-key provenance recorded" as "this section is empty," silently dropping any top-level section populated as a plain value rather than merged key-by-key (reproduces for any component type, e.g. a terraform component's settings/hooks).Found via a real-AWS field-test pass on the (currently unmerged) aws/cloudformation feature stack. All four bugs are general Atmos behavior unrelated to CloudFormation itself, so they ship here independently rather than waiting on that stack to merge.
docs/fixes/2026-09-09-error-callout-gradient-two-tone.mddocs/fixes/2026-09-09-missing-stack-prompt-not-firing.mddocs/fixes/2026-09-09-cfn-describe-component-missing-fields.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
describe component.Bug Fixes
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details>
<summary>fix(helm): carry create_namespace through the stack processor @aknysh (#3134)</summary>
create_namespace setting (added in #3034) being silently dropped by the stack processor, so create_namespace: false had no effect.create_namespace was not on it — so the key was stripped before it reached the Helm executor. atmos describe stacks --sections create_namespace returned {}, and the default of true always won.create_namespace to the per-component whitelist (helmComponentSectionKeys) and the stack-level helm: defaults whitelist (helmLifecycleSectionKeys), plus a HelmCreateNamespaceSectionName constant, regression + precedence tests, and a fix doc.create_namespace: false validated fine (the JSON schema already accepted it) but was invisible in the resolved config and never reached helm apply. The JSON schema and the stack processor's runtime whitelist are two independent lists; #3034 updated the schema but not the whitelist — hence "validates fine, shows up nowhere."403 — exactly the case create_namespace: false was meant to solve. Reported by a customer on Atmos 1.228.0.true; only components that explicitly set create_namespace: false change behavior.PR #3034 wired the reader side of the toggle — resolveCreateNamespace / boolFieldDefault in pkg/component/helm/values.go, the CreateNamespace field on chartSpec, the install-action plumbing in pkg/component/helm/client.go, and the JSON schemas — but never wired it through the stack processor. extractHelmComponentSection (internal/exec/stack_processor_process_stacks_helpers_extraction.go) copies only keys in helmComponentSectionKeys; any unrecognized key (including create_namespace) was dropped before the resolved section reached buildChartSpec, so the reader fell back to its true default.
pkg/config/const.go: add HelmCreateNamespaceSectionName = "create_namespace".internal/exec/stack_processor_process_stacks_helpers_extraction.go:
cfg.HelmCreateNamespaceSectionName to helmComponentSectionKeys (core fix — per-component, flows through base-component inheritance and into the final component config);helmLifecycleSectionKeys so it can also be set once as a stack-level helm: default and apply to every Helm component.internal/exec/stack_processor_process_stacks_helpers_test.go: TestExtractHelmComponentSectionCreateNamespace.internal/exec/stack_processor_merge_test.go: TestMergeComponentConfigurations_CreateNamespacePrecedence.docs/fixes/2026-09-11-helm-create-namespace-stack-processor-drop.md: fix record.| Where | Precedence | Use case |
|---|---|---|
component field (helmComponentSectionKeys) |
wins | per-release opt-out |
stack-level helm: default (helmLifecycleSectionKeys) |
weaker — a component can override it | convenience default across components |
The concern was to prove create_namespace reaches the Helm SDK install action end-to-end (native Helm uses action.Install, not the helm binary), not just that it survives the whitelist. Every link was traced and verified.
| # | Stage | Carries create_namespace? |
How verified |
|---|---|---|---|
| 1 | Stack manifest YAML | ✅ | JSON schema accepts it (#3034) |
| 2 | Stack processor extractHelmComponentSection |
✅ (fix) | new unit test; added to helmComponentSectionKeys |
| 3 | Merge → flatten into component map (stack_processor_merge.go) |
✅ | comp[key]=value over finalComponentHelm; TestMergeComponentConfigurations_CreateNamespacePrecedence |
| 4 | Resolved stacks map (read by describe stacks) |
✅ | ran the built binary — see below |
| 5 | processComponentConfig → info.ComponentSection |
✅ | utils.go:310 copies the whole component map wholesale (no helm sub-filter) |
| 6 | Template + YAML-function round-trips | ✅ | round-trip type is AtmosSectionMapType = map[string]any (generic map — no typed-struct drop) |
| 7 | buildChartSpec / resolveCreateNamespace reads it |
✅ | TestBuildChartSpec_CreateNamespacePropagates (default-true and explicit-false) |
| 8 | newInstallClient: client.CreateNamespace = spec.CreateNamespace |
✅ | TestNewInstallClient_WiresCreateNamespace |
| 9 | Helm SDK install action honors it | ✅ | TestApplyRelease_CreateNamespaceControlsNamespaceCreate (recording kube client asserts namespace create only fires when true) |
Two traps specifically ruled out:
schema.Helm (the struct) is only the global components.helm: type defaults (base_path, plugins, repositories…). The per-component section travels as map[string]any and is never unmarshaled through a typed struct that would silence unknown keys. The template/YAML re-conversions use map[string]any.describe stacks uses its own extractDescribeComponentSections, but that only pulls named sub-sections; it passes top-level scalar keys through (proof: namespace, also not in that struct, already appears in output).Empirical run (built from this branch, against a copy of examples/helm with create_namespace: false added to the demo component):
$ atmos describe stacks -s dev --components demo --component-types helm --sections create_namespace
dev:
components:
helm:
demo:
create_namespace: false # ← was {} before the fix
That output comes from the same resolved component map the executor feeds to buildChartSpec; steps 7–9 carry it the rest of the way to client.CreateNamespace = false.
Automated tests + coverage (all pass):
go test ./internal/exec/ -run TestExtractHelmComponentSectionCreateNamespace — fails on the pre-fix whitelist (reproduces the drop), passes after the fix.go test ./internal/exec/ -run TestMergeComponentConfigurations_CreateNamespacePrecedence — component value wins over stack default; stack default applies when the component is unset.extractHelmComponentSection, extractHelmLifecycleSection, extractHelmOverrideSection 100%; mergeComponentConfigurations 97.6%.go test ./internal/exec/ -run 'Helm', plus the full ./internal/exec/ suite; go test ./pkg/component/helm/... ./pkg/config/....go build ./...; gofumpt clean.Add create_namespace setting to native Helm components).docs/fixes/2026-09-11-helm-create-namespace-stack-processor-drop.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
create_namespace setting is now preserved during stack processing.true and false values flow through correctly; omitted values retain existing defaults.Tests
Documentation
<details> <summary>fix(ui): output-only plans no longer reported as NO CHANGES in --ui @osterman (#3121)</summary>
--ui) now treats output-only plan diffs as real changes instead of reporting NO CHANGES.DependencyTree.HasOutputChanges()/OutputChangeCount() (from plan.OutputChanges) and ResourceTracker.HasOutputChanges() (from the streamed outputs message's per-output action).pkg/terraform/ui/executor.go (showPlanTree, showTwoPhasePlanTree, executeWithPlanFile) and into the streaming completion summary in model_render.go.RenderChangeSummaryBadges gained an OUTPUTS CHANGED badge and no longer renders NO CHANGES when only outputs changed.atmos terraform apply <component> -s <stack> --ui silently skipped the confirmation prompt and the apply entirely when the only diff in the plan was an output value, so the new output never reached state (exit code 0, no error).atmos terraform plan --ui hid the output diff completely, and atmos terraform deploy --ui (auto-approve) applied the change correctly but printed a misleading ... completed (no changes) summary.tfjson.Plan.OutputChanges or the streamed output action field, even though that data was already being parsed and stored.tree_test.go, executor_test.go, model_test.go, resource_test.go), written first to confirm the gap before implementing the fix, per the repo's bug-fixing workflow.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>fix(pro): report full logical component name in Atmos Pro uploads @goruha (#3111)</summary>
Fixes two places where Atmos Pro uploads report a truncated component name for nested (path-style, slash-containing) logical component names — e.g. foo/bar/baz is reported as baz:
--upload-status): uploadStatus in internal/exec/pro.go now sends info.ComponentFromArg (the full logical name) instead of info.Component (the truncated working-directory leaf).terraformNodeHooks.recordExecResult in cmd/terraform/utils.go now passes info.ComponentFromArg into buildTerraformExecData for each per-node entry, instead of the truncated leaf.The internal name-splitting logic that produces the truncated leaf (internal/exec/utils.go, ProcessStacks) is untouched — it's still required for Terraform working-directory resolution (components/terraform/<prefix>/<leaf>/).
The original issue's proposed fix targeted only recordExecResult, but code review established that call site only fires for multi-component runs (--affected/--all/--components/--query). The issue's own repro — a single-component atmos terraform plan "foo/bar/baz" -s <stack> --upload-status — is actually caused by uploadStatus, a separate call site the original proposal didn't touch. Both are fixed here so the exact repro and the broader bug class are both resolved.
Because other identity channels (stack locks, affected-component uploads, single-component execution records) already report the full logical name, this mismatch caused Atmos Pro's approvals-page "previous plan" lookup to fail with "No previous plan found for this component" for any nested component, even though the plan ran and uploaded successfully.
A related but distinct issue — path-style CLI arguments (atmos terraform plan ./components/terraform/vpc) reporting the raw filesystem path instead of the resolved logical name in single-component execution records — was identified during review and deliberately scoped out to keep this fix minimal. Tracked in #3110.
specs/003-fix-upload-component-name/ (spec, plan, research, data-model, contracts, quickstart, tasks)TestUploadStatusReportsFullComponentName (nested + flat cases) in internal/exec/pro_test.goTestRecordExecResult_ReportsFullComponentNameForNestedComponent in cmd/terraform/utils_exec_metadata_test.goTestTerraformExecMetadataParserFunc_ReportsFullComponentNameForNestedComponent confirming the already-correct single-component parser path is unaffectedinternal/exec and cmd/terraform pass unmodifiedpact consumer-contract suite (go test -tags pact ./pkg/pro/...) passes unmodified — no fixtures assumed the truncated valueinternal/exec/utils.go (working-directory split logic) has zero diffgo build ./..., atmos lint --changed, atmos test, and full tests/ package all pass<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
foo/bar/baz, instead of reporting only the final segment.Documentation
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>fix(website): cast download polls render status as JSON, waits up to 30m @osterman (#3115)</summary>
CastProArtifact/useCastArtifact.ts) to poll the render-status endpoint with Accept: application/json instead of the raw artifact URL, and to treat only a genuine 200 response as "ready" — never response.ok on any 2xx.CastProArtifact/polling.mjs, with a companion polling.test.mjs covering the queued→rendering→ready path, an immediate-ready response, terminal errors, the slowdown threshold, the wait ceiling, a hung fetch, and cancellation.CastProDownload to show "Queued…"/"Rendering… m:ss" (with a "taking longer than usual" hint) and an optional progress bar, and updated CastProArtifact/README.md to document the render service's actual JSON/200/202/500 contract and the new polling cadence.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Documentation
<details> <summary>fix: terraform --all bootstrap, list-command lazy eval, init/UI polish @osterman (#3095)</summary>
atmos terraform apply --all no longer aborts before the scheduler runs anything, on a fresh environment where a dependent component's !terraform.state/!terraform.output reference points at a component that hasn't been applied yet (e.g. audit-trail reading kms's key_arn before kms has run). This does not skip or fake the value: the preflight's unresolved placeholder is discarded and never reaches Terraform. Each component still independently re-describes and re-resolves its own vars from scratch immediately before its own plan/apply — by which point, in a correctly-ordered dependency graph, kms has already applied and !terraform.state reads the real value.atmos list stacks/list components/list instances now skip evaluating Go templates (atmos.Component, atmos.GomplateDatasource) and YAML functions (!terraform.state, !terraform.output, !store) for stack/component sections that no displayed column actually reads. Previously every value was resolved eagerly regardless of the requested columns, which produced a spurious "N value(s) could not be determined and are shown as (computed)" warning for values that were never shown, and could take 30s–6+ minutes on stacks that use !terraform.output/atmos.Component in vars — even though list stacks only ever displays stack names by default. Closes #3068.atmos init "Select a template" picker now sizes its columns to the real terminal width instead of hard-coded widths, so long descriptions truncate cleanly at a word boundary instead of splitting mid-word onto a stray line.--ui, the after-init providers lock step (triggered by an active registry/plugin cache) now streams through the same init spinner as terraform init/plan/apply, instead of dumping raw provider-fetch/checksum output into the middle of the fancy UI.atmos init) are now indented to align under the item's own text instead of falling flush with the bullet/number.--all preflight only exists to build the dependency graph and validate config before the scheduler starts — it's built purely from static dependencies/settings.depends_on, never from resolved vars. But it previously resolved !terraform.state/!terraform.output for every component strictly, so an unprovisioned dependency (normal and expected on a fresh AWS landing-zone environment: kms → audit-trail/baseline/monitoring) aborted the entire run before a single component was applied. Since the preflight's resolved value for this one recoverable error class is never used for anything but graph construction — and every node re-resolves its own vars fresh, for real, immediately before its own apply — degrading (not failing on) this specific error class during preflight (reusing the existing --error-mode=warn machinery) is safe and unblocks the documented apply --all bootstrap flow. Other error classes (e.g. a missing !secret) are unaffected and still fail the preflight as before.list stacks/list components/list instances resolved every section of every component before column projection ever happened, regardless of whether any column would display the result. A new opt-in evaluation-scope filter (evalSections, deliberately separate from the existing output-only sections filter used by describe stacks --sections=X, so that command's behavior is untouched) is derived from the resolved column set and threaded through both the Go-template render pass and YAML-function resolution, falling back to full eager evaluation whenever the column templates can't be statically proven safe to skip.providers lock hook ran through a raw shell call that bypassed the streaming TUI entirely, so its output leaked raw into an otherwise fully---ui-rendered run.</details>
<details> <summary>chore(deps): update dependency posthog-js to v1.418.1 @renovate[bot] (#2954)</summary> This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| posthog-js (source) | 1.409.5 → 1.418.1 |
<details> <summary>PostHog/posthog-js (posthog-js)</summary>
v1.418.10599fe0 Thanks @ablaszkiewicz! - Recognise Firefox and Safari extension frames when filtering extension exceptions, and stop counting Safari's masked webkit-masked-url:// frames as in-app code.
(2026-08-18)0599fe0]:
v1.418.01ade666 Thanks @marandaneto! - Add cookieWinsOnConflict to keep shared cross-subdomain identity and session state ahead of stale per-origin localStorage, deprecate __preview_cookie_wins_on_conflict, and enable the new behavior for the 2026-08-29 defaults.
(2026-08-18)1ade666]:
v1.417.48d74821 Thanks @ksvat! - Take a full snapshot when session recording wakes from idle if DOM mutations were dropped while idle, so replay no longer shows duplicated or overlapping DOM after an idle period.
(2026-08-17)v1.417.3ce8fc13 Thanks @marandaneto! - Restore exception autocapture compatibility for posthog-js clients through version 1.141.0.
(2026-08-17)v1.417.27b61aa4 Thanks @posthog! - Fix error tracking coercion reporting the wrong exception type for non-Error objects (e.g. TypeError, ReferenceError) that are thrown by browser extensions or other cross-realm code. Previously these always reported as type Error, burying the real type in the message string. Also fixed a local isError helper shadowing the more robust cross-realm-aware implementation, which caused some errors thrown from iframes or extension isolated worlds to be misclassified.
(2026-08-17)7b61aa4]:
v1.417.1#4521 0a0206f Thanks @marandaneto! - Normalize capture timestamp overrides to equivalent UTC ISO strings in the browser and Node.js SDKs and shared core.
(2026-08-14)
#4523 6230b5b Thanks @marandaneto! - Prevent swallowed rrweb observer initialization errors from breaking session replay teardown and subsequent recorder restarts.
(2026-08-14)
#4503 eb05237 Thanks @pauldambra! - fix(dead-clicks): treat visibility and focus changes as liveness signals, not dead-click evidence
The dead-click detector treated a visibilitychange as evidence a click was dead: it measured Math.abs(clickTimestamp - lastVisibilityChange) and, once that exceeded the threshold, timed the click out as dead. Because it only recorded the tab becoming visible, any click in a session where the tab had ever been backgrounded (median gap ~1 minute) was flagged.
A visibility or focus change near a click is the opposite — a sign the click did something (it woke/focused the tab, opened a new tab, or opened a new window/popup) — so these signals now only ever suppress a dead click, never cause one:
hidden), and a window focus/blur observer is added, since a click that opens a new window/popup may leave the tab visible and only surface as the current window losing focus.$dead_click_visibility_changed_timeout stays in the payload (always false) for shape compatibility, and a new $dead_click_focus_changed_delay_ms is emitted for observability.Updated dependencies [0a0206f, eb05237]:
v1.417.08bc63c3 Thanks @dustinbyrne! - Default external dependency loading to versioned asset paths with automatic fallback to legacy paths, and add a strict_script_versioning: 'fallback' mode.
(2026-08-13)8bc63c3]:
v1.416.1#4443 b2c6830 Thanks @arnohillen! - Harden the session replay stylesheet inlining budget (inlineStylesheetBudgetRules):
0 to disable) and direct rrweb.record() consumers keep unbounded inlining unless they opt in._cssText atomically, so monolithic sheets no longer produce one long task and partial CSS never reaches the wire.pagehide; residual failure modes are counted via $sdk_debug_replay_deferred_stylesheets_failed / _abandoned.insertRule output, adoptedStyleSheets) no longer charge the budget, since deferring <link> sheets buys those pages nothing.$sdk_debug_replay_discarded_duration_samples). (2026-08-13)Updated dependencies [c9086de, b2c6830]:
v1.416.0#4495 e4b9947 Thanks @marandaneto! - feat(browser): add rewriteRequestPath to customize API, feature flag, and asset paths for reverse proxies
(2026-08-12)
#4493 e34ebf9 Thanks @marandaneto! - Add reset options for applying bootstrapped identity, feature flag, and session values after posthog.reset() while preserving the legacy boolean argument.
(2026-08-12)
e4b9947, e34ebf9]:
v1.415.7847d963 Thanks @dustinbyrne! - Migrate browser feature flags to the shared extension lifecycle while preserving the public feature flag facade, persistence compatibility, request behavior, and event enrichment.
(2026-08-12)v1.415.6#4500 d773405 Thanks @ksvat! - Fix session recording starting from arbitrarily old persisted configs.
Recording configs persisted by SDK versions before 1.347.2 carry no cache_timestamp. The core freshness check treated these undated configs as always fresh, so the recorder started immediately under their settings. A device whose stored config predated a customer's config change kept recording under the old triggers, sample rate, and masking settings indefinitely.
The core now treats undated persisted configs as stale. Recording waits for a fresh remote config before it starts, the same path every dated config older than one hour already takes. The lazy recorder bundle is unchanged: it still accepts undated configs, because old cores that load the latest bundle cannot recover from a rejected config (INC-749). (2026-08-11)
v1.415.5#4497 d62e42e Thanks @hpouillot! - Fix a Chrome renderer crash (grey "Aw, Snap" tab) that could occur when closing an in-app survey.
The survey close path wrapped the survey container's DOM removal in document.startViewTransition. Removing the element inside the transition callback left the captured snapshot pointing at a removed node, which on heavy SPAs triggered a Chromium renderer crash and took down the whole tab.
The close path now only animates a fade-out inside the transition and lets React tear the container down once the transition settles. It also guards against overlapping transitions (a second close while one is animating) and always settles the popup state if the transition is skipped or interrupted, so the survey can never be left visible with a stale reference. (2026-08-11)
v1.415.4deb6bb0 Thanks @marandaneto! - fix(types): accept current and legacy Segment Analytics SDK types in the Segment integration config
(2026-08-11)deb6bb0]:
v1.415.3#4488 23db844 Thanks @TueHaulund! - fix(replay): never ship a buffer swapped in by a re-entrant session rotation mid-flush
(2026-08-11)
#4474 e06bf52 Thanks @dependabot! - dependencies updates: - Updated dependency dompurify@^3.4.13 ↗︎ (from ^3.4.12, in dependencies) (2026-08-11)
#4435 1cbbe6a Thanks @arnohillen! - fix(replay): stop dropping adopted stylesheets that arrive before the host's shadow root is attached. When the recorder's full snapshot races a web component's hydration, the AdoptedStyleSheet event can be recorded before the mutation that attaches the host's shadow root. The replayer silently dropped those styles for the rest of the page view, so components styled via shadowRoot.adoptedStyleSheets (Stencil, Lit) rendered completely unstyled. The replayer now constructs the stylesheet even when the shadow root does not exist yet and keeps retrying adoption until it is attached.
(2026-08-11)
v1.415.2f999394 Thanks @dustinbyrne! - Support removing multiple persisted properties in one operation.
(2026-08-11)f999394]:
v1.415.16f9adf8 Thanks @TueHaulund! - fix(replay): don't open a recording that holds only idle lifecycle markers
(2026-08-10)v1.415.0#4436 80f15a3 Thanks @jakesciotto! - feat(surveys): optional intro screen shown before the first question
Surveys can now display an intro screen before question 1, configured via the new
displayIntroScreen, introScreenHeader, introScreenDescription,
introScreenDescriptionContentType, and introScreenButtonText appearance fields.
The intro is dismissed with a button and records no response, does not affect
completion or partial-response metrics, does not re-fire "survey shown", and is
skipped when a survey is resumed with answers in progress. Intro copy is
translatable like the thank-you message. renderSurveysPreview accepts
previewPageIndex: -1 (exported as INTRO_SCREEN_PREVIEW_INDEX) to preview the
intro screen. (2026-08-10)
80f15a3]:
v1.414.05bd8b83 Thanks @darkopia! - Add posthog.conversations.getUnavailableReason() to expose why the conversations API is unavailable (bundle blocked/failed to load, disabled in project, remote config pending/failed, still initializing, …) instead of collapsing every case into isAvailable() === false. Lets callers that fall back to another channel record the specific cause. ConversationsUnavailableReason is exported from the package entry points, so consumers can name the type.
(2026-08-07)v1.413.3#4414 1b88c2f Thanks @marandaneto! - Clear properties registered for a session when the PostHog session rotates.
(2026-08-06)
#4374 b39b577 Thanks @dustinbyrne! - Persist in-place object and array mutations when properties are re-registered.
(2026-08-06)
#4434 75fb719 Thanks @arnohillen! - Make the session replay attribute masking options mutually exclusive: when both maskAllElementAttributes and maskAttributeFn are set, the coarse option wins and the callback is ignored (with a console warning), so a callback can no longer accidentally unmask what maskAllElementAttributes hides.
(2026-08-06)
Updated dependencies [64ba193, 75fb719]:
v1.413.2ee7fab0 Thanks @posthog! - Fix a benign network failure (e.g. TypeError: Failed to fetch) in the async native-gzip request path surfacing as an unhandled promise rejection, which exception autocapture would otherwise pick up
(2026-08-05)v1.413.1#4390 1160403 Thanks @posthog! - Contain and log recorder-owned callback failures while preserving exceptions from patched native host APIs. Keep recording mutations from adopted cross-realm nodes.
(2026-08-05)
#4286 d108d66 Thanks @posthog! - fix(replay): preserve privacy masking for initial network metadata
Initial navigation and performance-timing entries are now passed through maskCapturedNetworkRequestFn, including when they have no method. URL rewrites are respected. When the callback returns nullish for an initial entry, replay-required timing metadata is retained without its URL, headers, or body so method-gated callbacks do not drop the metadata or expose deliberately filtered customer data. Derived server-timing entries are also suppressed when this strict fallback is used. Enforced PostHog filtering and payload cleaning still run first. (2026-08-05)
Updated dependencies [d108d66]:
v1.413.02da12b8 Thanks @posthog! - Add attribute-level masking to session replay: maskAttributeFn provides per-attribute control over the final serialized value, while maskAllElementAttributes masks all source DOM string attributes (including rendering attributes and synthesized form values) at the cost of replay fidelity.
(2026-08-05)2da12b8 Thanks @posthog! - fix(replay): discard held interaction-less recordings when a background document unloads without ever becoming visible
(2026-08-05)2da12b8]:
v1.412.23acadfe Thanks @marandaneto! - fix(replay): discard held interaction-less recordings when a background document unloads without ever becoming visible
(2026-08-05)v1.412.1a348fb3 Thanks @dependabot! - Update PostCSS to include upstream security fixes.
(2026-08-05)v1.412.0v1.411.0#4266 43d1850 Thanks @posthog! - feat: add opt-in capture_performance.__preview_web_vitals_soft_navs to fix inflated web vitals on single-page apps
Client-side route changes in SPAs previously left web vitals (LCP especially) accumulating against the original hard-navigation timestamp, inflating the top tail of Core Web Vitals. Setting capture_performance: { __preview_web_vitals_soft_navs: true } now scopes metrics to the browser's Soft Navigation entries so each route change starts a fresh measurement window. It's a preview option because it relies on Chrome's experimental Soft Navigation Detection API and loads pinned stable web-vitals 6.x callbacks; when disabled (the default), the existing web-vitals 5.x behavior remains unchanged. (2026-08-04)
d3c4538 Thanks @posthog! - Keep $referring_domain and canonical utm_*/campaign parameters on minimal $feature_flag_called events. Previously the minimal allowlist stripped every campaign parameter, so a flag-called event landing first in a session could set the session's UTM attribution and channel type to NULL in web analytics.
(2026-08-04)d3c4538, 43d1850]:
v1.410.10#4271 3d4e2fd Thanks @felipeatom! - Fix inline surveys rendering an empty container when a stale persisted question index (left over from a prior completion) points past the last question. When the persisted index is out of range the whole in-progress record is now discarded and the survey starts fresh, instead of clamping the index while keeping the equally-stale responses and visited indices. Restored visited indices are also filtered to valid questions so the Back button can never navigate to a non-existent question and re-empty the container.
(2026-08-04)
#4412 5f2b78a Thanks @TueHaulund! - fix(replay): hold fresh interaction-less session recordings until there is evidence someone cares
A tab that loads but never sees any user interaction (prefetched pages, background tabs, in-app browser preloads) no longer ships a billable recording while it sits untouched. Like rotation-born sessions, a fresh recording epoch is held until there is evidence someone cares about it: a user interaction, an event trigger match, or an explicit override (posthog.startSessionRecording(...)) releases the hold and ships the buffer on the normal flush cadence, so released recordings are playable from the session's start. A clean unload also ships a fresh-start hold, so passive visits (reading, watching a video) are still captured exactly as before; rotation-born holds are discarded on unload as before. A held buffer that reaches the size cap is dropped to bound memory, and a later release takes a fresh full snapshot so the recording resumes playable. (2026-08-04)
#4410 064874a Thanks @ioannisj! - Fix held rotation-born session replay buffers not flushing when a V2 event trigger matches
(2026-08-04)
#4343 83a9b67 Thanks @arnohillen! - Session replay no longer freezes the page re-encoding base64 images that are already small. When canvas recording is enabled, every <img> with a data: URL was synchronously redrawn and re-encoded through canvas.toDataURL during full snapshots and attribute mutations. The encode cost scales with pixel dimensions, not payload size, so a page of base64 lazy-load placeholders (measured: 18 images of 4096x3072 at ~33KB each) blocked the main thread for 7+ seconds to produce outputs that were larger than the inputs. Recompression now skips data URLs under 100KB (where it cannot save meaningful payload), keeps the original when the re-encoded output is not smaller, and memoizes by input so repeated snapshots and src-swapping mutations never pay for the same image twice. Genuinely large base64 images are still recompressed as before.
(2026-08-04)
#4339 f865818 Thanks @posthog! - Report privacy-aware dropped-event count, page and session context in the client rate limit warning
(2026-08-04)
Updated dependencies [f865818]:
v1.410.9#4314 feb9e2a Thanks @posthog! - fix: warn when reset() silently opts the user back out
reset() clears stored consent along with the rest of the user's state. With opt_out_capturing_by_default, this returns the instance to the opted-out default, so calling reset() after opt_in_capturing() would stop capturing without warning. It now logs a warning when that happens and documents the required ordering. (2026-08-04)
#4288 877418e Thanks @posthog! - Fix event-triggered survey popup delays resetting on every page navigation. The popup delay now resumes from when the trigger fired (persisted for the session) instead of restarting a fresh countdown on each page load, so a survey configured with an event/action trigger and a popup delay no longer gets lost when the user navigates before the delay elapses.
(2026-08-04)
Updated dependencies [feb9e2a]:
v1.410.8a31bd1e Thanks @NVolcz! - Publish TypeScript declarations for browser extension entrypoints under their public dist paths.
(2026-08-04)v1.410.79811a43 Thanks @marandaneto! - Avoid promoting handled transport failures to error logs in surveys, product tours, remote config, conversations, and logs while preserving error severity for HTTP and unexpected failures.
(2026-08-04)v1.410.66d5e314 Thanks @ioannisj! - Fix session replay shipping one billable recording per session rotation for tabs the user never interacts with. A session born from an idle rotation now holds its buffer until the first user interaction, then ships a recording playable from the session's start; without interaction nothing is sent — a further rotation, stop, opt-out, or page unload discards the held data instead of shipping it. An event trigger match (for example record-on-exception) also releases the hold, since it is explicit intent to record the session.
(2026-08-03)v1.410.58ec3499 Thanks @felipeatom! - Fix selector-widget surveys being abruptly removed while open when their trigger element is unmounted from the DOM (e.g. a dropdown or menu that hosts the trigger closes). The survey is now kept in place while open and only torn down once the user has closed it. Also fixes a related leak where, if the selector resolved to a different element while the survey was open, the old element's click listener was never removed and kept dispatching the show-widget event for the lifetime of the page.
(2026-08-03)v1.410.4v1.410.3662fb4c Thanks @christiaan-ph! - Conversations widget: bullet and numbered lists in a support reply now keep their markers on host pages with an aggressive CSS reset (for example Tailwind preflight's ol, ul { list-style: none }). The widget renders into the host page's DOM, so the list style is now set inline on <ul>, <ol>, and <li> rather than left to the page's own styles.
(2026-08-03)v1.410.2v1.410.1Note truncated.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Bumped 5 vulnerable transitive npm deps in website/ (js-yaml, svgo, joi, colord) via pnpm.overrides, closing 7 open Dependabot alerts — all within-maj…
<details> <summary>Add single-label lookups with optional defaults @osterman (#3097)</summary>
Add !labels key [default] with missing-key errors, explicit fallbacks, and inheritance coverage.
Document label access and an Atmos Pro example that consumes resolved labels; update agent skills, the feature announcement, and roadmap.
Allow macOS Colima startup 12 minutes for provisioning and its VM restart, and give the enclosing setup step 55 minutes to cover both attempts.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
!labels can retrieve an individual metadata label with an optional fallback value.!labels continues to return the complete label map.Documentation
<details> <summary>fix(ci): stop Mergify updating bot PRs once approved @osterman (#3112)</summary>
#approved-reviews-by=0 to the Mergify rule Keep Dependabot/Renovate PRs up to date with main, so Mergify stops running update on a bot PR once it has an approval.Since main moved to GitHub's native merge queue (ruleset "Merge Queue", 2026-08-06), this rule fails on essentially every bot PR that gets enqueued — 6 of the last 12 (#3066, #3067, #3071, #3086, #3091, #3098):
Base branch update has failed protected branch '<pr head branch>' check failed: A pull request for this branch has been added to a merge queue. Branches that are queued for merging cannot be updated.
Mechanism:
Mergify's update action merges main into the PR's head branch. GitHub locks that branch while the PR sits in the native queue.
Mergify's built-in "skip if queued" guard is queue-position = -1, which only reflects Mergify's own queue. There is no Mergify condition for GitHub's native queue, and nothing lands on the head SHA either (no check-run or commit status is created on enqueue), so there is nothing else to condition on.
The rule wakes on PR webhooks, not promptly on pushes to main. On the failing PRs the branch had been behind for 50–70 min unnoticed; Mergify re-evaluated ~2 min after the approval/enqueue events, when the branch was already locked:
| PR | approved | enqueued | update failed | merged |
|---|---|---|---|---|
| #3091 | 02:20:02Z | 02:20:09Z | 02:21:44Z | 02:40Z |
| #3098 | 02:22:21Z | 02:22:28Z | 02:24:37Z | 02:43Z |
| #3067 | 20:35:15Z | 20:35:32Z | 20:37:46Z | 21:25Z |
| #3066 | 20:35:30Z | 20:35:35Z | 20:38:05Z | 21:25Z |
Why approval is the right gate: the "Required Pull Request Reviews" ruleset requires 1 approval with no bypass actors, so GitHub cannot enqueue a PR without a current approval. Approval is therefore a strictly earlier signal than enqueue, with no timing dependency (an Actions workflow on pull_request: enqueued toggling a label would be racing that same ~2 min window). After approval the merge queue owns freshness by re-testing against current main.
Side benefit: the ruleset has dismiss_stale_reviews_on_push: true, so today a Mergify update landing after approval dismisses the approval and forces a re-review. That stops.
Context: this rule was added in #2752 because main then had strict: true (require branches up to date). That protection is gone with the merge queue, so the alternative of deleting the rule outright is also valid; this keeps pre-review freshness for bot PRs.
The failures were cosmetic (Mergify is not a required status check; the PRs merged via the queue), but they show up as a red check on every bot PR.
update action docs: "You do not need to use this action if you use the merge queue."<!-- 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): invalidate CloudFront cache on website deploys @osterman (#3103)</summary>
cloudfront-distribution-id / cloudfront-invalidation-paths input and invalidation step to the shared .github/actions/s3-deploy composite action.website-deploy-prod.yml (invalidates /* on the prod atmos-docs-site-spa distribution E2WVYUGW40ZPA8) and website-preview-deploy.yml (invalidates only /pr-<N>/* on the dev distribution E1U29O8X09M5UR, so one PR's deploy never busts every other open PR's preview cache).cloudfront.amazonaws.com:443 to both workflows' Harden Runner allowlist.ChunkLoadError (404 on a hashed JS bundle). Root cause: website-deploy-prod.yml runs aws s3 sync --delete but never invalidated CloudFront, and the distribution's legacy per-behavior TTL (min_ttl: 60) floors edge caching regardless of origin Cache-Control. A client hitting a stale edge-cached index.html within that window got 404s on chunks a newer deploy had already deleted.docs/fixes/2026-09-08-website-deploy-race-serialize.md) — confirmed via GitHub Actions run history that the existing concurrency: guard is working correctly.cloudfront:CreateInvalidation/cloudfront:GetInvalidation scoped to their own distribution (confirmed live via aws iam get-role-policy, not just the infra-live Terraform source) — it was simply unused, so this fix is fully contained in cloudposse/atmos with no infra-live change needed.Completed.docs/fixes/2026-09-09-website-cloudfront-stale-chunk-invalidation.mddocs/fixes/2026-09-08-website-deploy-race-serialize.md (related prior incident, confirmed not the same root cause)<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>Link changelog announcements to usage documentation @osterman (#3099)</summary>
</details>
<details> <summary>feat(vendor): add Azure DevOps pull-request provider @jorrite (#3048)</summary>
Adds pkg/git/providers/azuredevops as a second PullRequestPublisher implementation alongside the existing GitHub provider, so atmos vendor update --pull-request can target Azure DevOps Repos.
azuredevops provider, registered via init() under ci.pull_request.provider: azuredevops.schema.VendorPullRequestConfig gains organization / project / repository fields, since Azure DevOps addresses a repository with three segments instead of GitHub's owner/repository pair. pkg/config's bridgeVendorUpdaterConfig now syncs these three fields into viper along with the rest of vendor.ci.pull_request.* — they were declared on the schema and read by cmd/vendor/update.go but never actually bridged, so provider: azuredevops always failed configuration validation regardless of what atmos.yaml declared (found by testing against a real Azure DevOps org).PullRequestOptions gains an additive Namespace []string field to carry the extra segment (nil for GitHub; the GitHub provider now rejects a non-empty Namespace instead of silently ignoring it).AZURE_DEVOPS_EXT_PAT (HTTP Basic, empty username).reviewers entry (a display name, account name, or email) is resolved through the Identities API before being applied. A group match or an ambiguous match fails loudly instead of guessing; only individuals are supported today. Confirmed against a real Azure DevOps org, resolving both a display name and an email correctly.assignees fails loudly instead of being silently dropped.atmosgit.PullRequestBodyBadger interface lets a PullRequestPublisher return its own badge, since each forge's pull request markdown has its own quirks (raw HTML support, image hosting requirements, light/dark switching); a publisher that doesn't implement it gets a static text-link fallback. GitHub keeps its existing raw-HTML <picture> badge with light/dark switching. Azure DevOps uses a plain, sized markdown image (![]() with Azure DevOps' own =WIDTHxHEIGHT sizing syntax) instead of raw HTML, which doesn't render in Azure DevOps pull request descriptions at all — confirmed against a real pull request.website/docs/cli/configuration/vendor.mdx, a changelog post, and a roadmap milestone.The PullRequestPublisher interface was explicitly designed to support more providers than GitHub, but nothing had implemented a second one yet. Teams hosting components in Azure DevOps Repos had no way to use the Component Updater's automated PR workflow at all.
pkg/git/pull_request.gopkg/git/providers/github/pull_request.gomain for any git-ref-versioned vendor source): #3076<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
vendor update --pull-request.AZURE_DEVOPS_EXT_PAT.Bug Fixes
Documentation
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>feat(website): Atmos Pro cast download/embed components @osterman (#2739)</summary>
CastProDownload, a "Download ▾" split-button component offering rendered GIF/MP4/SVG/WEBM artifacts of any .cast file in a public GitHub repo, via the new Atmos Pro cast-rendering service.CastProEmbed, an <iframe> wrapper for the service's hosted HTML player, for embedding a cast player without hosting the source file locally.CastProArtifact module: a pure URL builder (buildArtifactUrl/buildEmbedUrl, with unit tests) and a useCastArtifact hook that follows the render service's three response shapes — an already-rendered artifact (triggers a native download), a still-rendering one (polls on Retry-After, capped at ~60s), and a hard error (surfaces the JSON error message)./cast-pro-demo page exercising both components against a real cloudposse/atmos cast path, and a test:cast-pro-artifact npm script..cast recording in a public GitHub repo to GIF/MP4/SVG/WEBM, or to a hosted HTML player. This lets atmos.tools offer downloads/embeds of casts without needing them committed as static assets first, unlike the existing CastPlayer component.no-release.https://atmos-pro.com/casts/{owner}/{repo}/{ref}/{path}.cast.{gif|mp4|svg|webm}<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Tests
Documentation
<details> <summary>docs: flag Homebrew FIPS gap in fips-140-mode PRD @osterman (#3074)</summary>
Documents a Homebrew-specific gap in docs/prd/fips-140-mode.md's "Where It's Wired In" table: the atmos formula in Homebrew/homebrew-core builds with a plain go build and no GOFIPS140, so brew install atmos produces a binary reporting "fips": false in atmos version --format=json, while GitHub Release binaries (built via .goreleaser.yml, which does set GOFIPS140=latest) correctly report "fips": true.
atmos version --format=json showing fips: false looked like GoReleaser had regressed. Investigation confirmed GoReleaser and the local atmos build path (magefiles/build.go) both set GOFIPS140=latest correctly. The actual gap is Homebrew's from-source build, which lives entirely outside this repo. The PRD's wiring table previously claimed "every distinct Go-toolchain build invocation in the repo sets GOFIPS140" without mentioning that Homebrew isn't covered by that claim at all (it's not a build invocation in this repo), so this was an unflagged blind spot.
A fix is proposed upstream: Homebrew/homebrew-core#302847 (draft, pending Homebrew maintainer review — outside this repo's control).
docs/prd/fips-140-mode.mdinternal/exec/version.go (isFIPSBuild() — reads crypto/fips140.Enabled() at runtime).goreleaser.yml (sets GOFIPS140=latest for release binaries)<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Documentation
Bug Fixes
<details> <summary>docs: add homebrew skill for atmos formula PR workflow @osterman (#3081)</summary>
Adds .claude/skills/homebrew/SKILL.md, an agent skill covering the Homebrew/homebrew-core formula PR workflow for atmos: the real PR template, AI/LLM disclosure rules, the 50-character commit-subject limit, and how to run brew install --build-from-source / brew test / brew audit --strict / brew style locally via a disposable tap without a full homebrew-core clone.
A prior attempt at a Homebrew formula PR (Homebrew/homebrew-core#302847) was auto-closed by BrewTestBot for looking AI-generated and skipping the real PR template. This skill exists so the next attempt (fixing that PR, per its own "do not open a new PR" instruction) follows homebrew-core's actual conventions instead of repeating the same mistake.
.claude/skills/homebrew/SKILL.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Reliability
Documentation
<details> <summary>fix(ci): restore-only Go caches with a real warmup writer @osterman (#3077)</summary>
actions/setup-go's built-in cache with a restore-only custom cache (restore-keys fallback, ImageOS-free key) in .github/actions/setup-go-cache; no CI job ever saves Go caches anymoresetup-go-cache-warmup.yml the sole cache writer: adds a Linux leg, runs the real compiles (go build ./..., mage acceptance:precompile, and a -race/CGO warm for the race job's namespace), saves under run-unique keys, and triggers on go.mod/go.sum pushes to mainextras=s3-cache so all Linux jobs share the GitHub cache backend; upgrade the race job to runner=xlargekubernetes-e2e nullifying its restored cache with a GOCACHE overridewarm-cache job); PR runs are now restore-onlycustom-gcl binary (full golangci-lint rebuild every run today), the pnpm store in both website workflows, and add restore-only toolchain caches to lint, hooks-tflint, floci, floci-go, and race.tool-versions changes (hashFiles in atmos.yaml ci.cache.key)Storage-level caching works (92 entries / ~99GB active, no eviction thrash), but the caches were functionally hollow: setup-go entries are immutable per go.sum hash, and the old warmup only ran go mod download — so whenever it saved first, the frozen entry had an empty GOCACHE and every later build compiled from scratch while logging a cache hit. Measured live on run 34179823625: 504s go build in Build(linux), a 27-minute race job, and 1-1.8GB re-saved per platform per PR after every dependency merge. The Linux split-brain (build job on RunsOn S3, shards on GitHub cache) meant the warmest cache in the run was invisible to the ten Linux acceptance shards.
Deliberately not done: relocating atmos's own cache root to the Windows work disk — the acceptance shards assert XDG-default paths, and the cache's saver and restorers must agree on the root.
Post-merge verification: dispatch setup-go-cache-warmup.yml, confirm multi-GB go-cache-* entries on refs/heads/main, then compare Build(linux) go build time (expect ~504s → well under 2 min) and race-job duration (expect ~27m → ~10-15m).
🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
CI Improvements
Website Builds
Bug Fixes
Documentation
<details> <summary>feat(version): add yaml manager and json format field to Version Tracker @osterman (#3069)</summary>
format field to the json version-tracker manager's options.set entries (pkg/version/managers/json/json.go): a Go template (Sprig string functions + Atmos template functions) rendered against the resolved manager.VersionRef, whose output replaces the verbatim value before it's written into the target JSON field.yaml file manager (pkg/version/managers/yaml/) that writes locked values into YAML files at configured field paths, reusing Atmos's own format-preserving YAML editor (pkg/yaml, the engine behind atmos config set/atmos stack set) so comments, anchors/aliases, and key order on untouched fields survive the write. It supports the same optional format field as the json manager, and the same dot-notation path syntax as atmos config set/atmos stack set (sources[0].version, metadata."weird.key"), which is distinct from the json manager's sjson/gjson dialect.format-template rendering and duplicate-path-check logic shared by both managers into pkg/version/managers/format.go and pkg/version/managers/pathutil.go, and updates the json manager to use them (no behavior change).ErrVersionJSONFormatInvalid, ErrVersionYAML*) so a bad format template or an invalid options.set configuration is rejected outright instead of silently writing garbage or an empty string.yaml-specific test that a fixture with comments and an anchor/alias survives an edit untouched, and a test that a bare-digit version string round-trips as a YAML string rather than silently becoming an int.website/docs/cli/configuration/version/files.mdx): a format example/section for json, and a new "Updating YAML Files" section for yaml.json-manager-format, version-tracker-yaml-manager) and two roadmap milestones announcing both features.json manager always wrote a locked dependency's resolved value byte-for-byte. For a dependency sourced from github-releases/github-tags, that value is the raw git tag (e.g. v1.228.0) — wrong when the target field expects bare semver, such as a plugin manifest's version field. Reshaping happens at the write site (setEntry), not on the shared manager.VersionRef type or the lock file, since the same locked dependency may feed multiple write sites that want different shapes, and versions.lock.yaml should stay the untouched, auditable record of what was resolved against upstream.template manager (renders a whole *.tmpl source to a sibling file) nor marker (a plain comment-annotated token rewrite) patches a single field in an existing, hand-maintained YAML document while preserving comments and anchors. The yaml manager fills that gap by reusing Atmos's already-shipped format-preserving YAML editor instead of building new YAML-parsing logic.json-manager Version Tracker gaps shipped in #2900 and #2966.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
track apply.Bug Fixes
Documentation
<details> <summary>test: parallelize blocker-free tests in the race job's slowest packages @osterman (#3078)</summary>
t.Parallel() to every top-level test and t.Run closure in the test files that have no parallelism blockers, across the packages that dominate the CI race job's wall clock:
pkg/describe (46/49 tests); pkg/toolchain itself is excluded — its TestMain routes UI output into one captured buffer, so any parallel test that emits ui.* output races on it, and its heavy tests must stay serial regardlessinternal/exec (76), pkg/runner/step (29), pkg/ai/tools/atmos (29), pkg/config (22), pkg/pro (15), pkg/toolchain/installer (10), cmd/terraform (8), pkg/terraform/ui (7), cmd/toolchain (3), pkg/toolchain/registry/aqua (2)pkg/describe tests serial with explained //nolint:paralleltest directives (they invoke sibling test functions directly with their own *testing.T, so a second t.Parallel() panics)-parallel=4 (ATMOS_TEST_RACE_PARALLEL), and every acceptance-shard test process gets -parallel / -test.parallel = half the runner's cores (ATMOS_TEST_PARALLEL) — without it the 3-vCPU hosted macOS runners oversubscribed and several shards ran 50-150% slower (e.g. shard 1: 665s → 1134s) while 4-vCPU Linux/Windows were unchangedparalleltest linter scoped (via the existing path-except idiom in .golangci.yml) to exactly the converted files so they don't regress; tparallel (already on) caught seven parent tests deferring cleanup while running parallel subtests, now t.Cleanupcmd/stack's fixture copy read the basic scenario's gitignored terraform.tfstate.d/…/terraform.tfstate while a shard-mate was writing it ("another process has locked a portion of the file"); the copy now skips Terraform runtime artifacts via the shared sandbox helper's predicate, exported as testhelpers.IsTerraformArtifactThe CI race job runs the whole ./... suite un-sharded, so its ~27-minute wall clock floors on the slowest packages — pkg/toolchain (556s), pkg/describe (327s), internal/exec (323s), cmd (247s), measured from run 34179823625. Go parallelizes across packages but runs tests within a package serially unless they call t.Parallel(). Locally pkg/describe drops from 18.1s to ~7-10s.
Method: mechanical conversion, then per-package go test -count=2 and go test -race as the arbiter — any file whose tests failed, panicked, or raced was reverted (96 files in the local pass, 13 more after CI runs exposed what local validation could not: package-cache resets (detectionCache, ClearBaseComponentConfigCache) and global-registry writes (atmosio.RegisterSecret) that the mutex makes race-clean but not order-safe, gomonkey code patching in TestGetAffectedComponents (skipped locally under -race and on darwin/arm64), and logical races on tests that swap package-level seams such as os.Stdin, executeTerraformLint, renderAndDeliver, tfoutput.SetDefaultExecutor, SetLastAuthContext, SetLastMergeContext, and one that hits pkg/terminal's unsynchronized lazy viper init). Files skipped or reverted use t.Setenv/t.Chdir (directly or via fixture helpers), mutate package globals (mock getters, SetAtmosConfig, viper, data.InitWriter/ui.InitFormatter, shared cobra command trees), share package caches, or raced under -race. All of cmd/list stays serial: its initTestIO/pkg/flags bindFlagToViper path races on package-level parsers. Those need dependency-injection refactoring before they can go parallel — that's the remaining lever on the race job's floor.
Two genuine production concurrency bugs surfaced by -race during this work (not fixed here): pkg/ui/markdown.NewRenderer races on glamour's shared style bytes when called concurrently (any parallel errors.Format), and the lazy viper.BindEnv init in pkg/ui/theme/pkg/terminal is unsynchronized (concurrent-map panic).
Validated: every converted package green under -count=2 and -race (zero data races), go vet clean, paralleltest lint clean over all scoped packages. Companion to #3077, which warms the race job's build cache and upsizes its runner.
🤖 Generated with Claude Code
</details>
<details> <summary>fix(ci): serialize website deploys and fix Sentry loader key @osterman (#3072)</summary>
concurrency group to website-deploy-prod.yml (cancel-in-progress: false) so pushes to main deploy one at a time.concurrency group to website-preview-deploy.yml for the same reason.docusaurus-plugin-sentry.docs/fixes/2026-09-08-website-deploy-race-serialize.md.atmos.tools went blank tonight. The live index.html referenced runtime~main.99cb7223.js and main.7524adc2.js, both 404.
The merge queue landed #3024 and #3058 on main three minutes apart. Each push triggered Website Deploy Prod, and the workflow had no concurrency group. Both runs execute aws s3 sync --delete against the single shared origin prefix, and Docusaurus content-hashes every bundle, so two builds never share asset names.
| Time (UTC) | Run | Action |
|---|---|---|
| 02:27:30 | A (#3024) | uploads main.7524adc2.js, runtime~main.99cb7223.js |
| 02:27:55 | A | uploads index.html referencing A's bundles |
| 02:27:58 | B (#3058) | --delete removes A's two bundles; uploads its own |
B's sync plan was computed before A's index.html landed, so B never rewrote it. Result: A's index.html pointing at bundles B deleted, and both runs green.
cancel-in-progress stays false on purpose. Aborting a run mid-sync leaves a half-uploaded site, which is the same failure. With a group, the in-flight deploy finishes, the newest pending run queues behind it, and older pending runs are superseded.
Separately, the same console showed the Sentry loader script CORS-blocked. docusaurus-plugin-sentry v2 builds https://js.sentry-cdn.com/${DSN}.min.js, so the option must be the Loader Script public key, not the DSN. The corrected URL returns 200; the old one returned 404. This did not cause the outage.
actionlint passes on both workflows; the Sentry head tag was rendered locally through the installed plugin and produces the corrected src.🤖 Generated with Claude Code
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
<details> <summary>feat(website): add Security & Trust page with live OpenSSF data @osterman (#3024)</summary>
/security page to atmos.tools showing our OpenSSF Scorecard and OpenSSF Best Practices badge results.website/plugins/fetch-security-posture) — no client-side runtime dependency on the third-party APIs, and the build never fails if either API is temporarily unavailable (each dataset degrades gracefully with a "verify directly" fallback link).api.scorecard.dev, bestpractices.dev) and linking straight back to them lets evaluators verify the numbers themselves instead of trusting a cached badge.website/plugins/fetch-github-stars, fetch-latest-release), so it fits the codebase's established conventions rather than introducing a new fetch mechanism.cloudposse/atmos recently earned a passing OpenSSF Best Practices badge (project #14393).<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
</details>
<details> <summary>fix(examples): use real Infracost CLI @osterman (#3093)</summary>
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Documentation
Bug Fixes
Demo Updates
<details> <summary>fix(scaffold): write conflict markers on manual merge, fix init --update, fix --force+--update @jorrite (#3047)</summary>
atmos scaffold generate --update (and atmos init --update, sharing the same engine) with the default --merge-strategy=manual now writes real <<<<<<</=======/>>>>>>> conflict markers plus every non-conflicting change on a real merge conflict, instead of discarding the whole merge and writing nothing.atmos init --update now pins its initial --git commit to .atmos/init/metadata.yaml, the same way atmos scaffold generate already does, and reads it back as the merge base instead of defaulting to live HEAD.--force combined with --update is no longer a silent no-op: an unset --merge-strategy now defaults to theirs in that combination, and an explicitly-passed ours/manual together with --force --update is now a clear validation error instead of silently doing nothing.--update against a file already left with unresolved conflict markers now fails fast with a specific message instead of an opaque three-way merge failed.--force-suggesting error hint across the merge engine to describe what --force actually does now.main before this fix.atmos init --update has the exact base-ref-pinning bug #2989 fixed for atmos scaffold generate, because the fix lived only in cmd/scaffold and was never ported to cmd/init — the two commands' base-ref resolution had drifted apart. This PR extracts the shared logic into pkg/generator/gitinit.go so it can't drift apart a second time.--force being silently ignored under --update made several existing error hints false, and left users with no way to push through a conflict without hand-editing the file.See docs/fixes/2026-09-04-scaffold-init-update-merge-fixes.md for full context, the complete list of changed files, and how each fix was validated (unit tests plus live end-to-end verification against a built binary).
docs/fixes/2026-09-04-scaffold-init-update-merge-fixes.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
init --update and scaffold generate --update now use the correct target and previously pinned merge base.--force --update defaults to using the template version; incompatible strategies are rejected.<details> <summary>fix(ci): test summary/JUnit dropped OpenTofu runs and late diagnostics @osterman (#3082)</summary>
atmos terraform test --ci discarded every run and file event from tofu test -json: OpenTofu emits one test_run/test_file event per subject carrying only status, with no progress field, and the parser only accepted events with progress: "complete". The test_summary event has the same shape in both tools, so badge counts stayed right while the results table came out empty and <component>.junit.xml reported tests="0" on a passing run.diagnostic after the run's final event; the parser only attached diagnostics that arrived before it, so failing runs lost their message and file:line (and with them the ::error annotation and the summary's Details column) under Terraform too.testEventComplete accepts a bare terminal status as final; attachLateDiagnostics reconciles diagnostics that arrive after their run. The stop-gap backfillMissingTestJSONRuns guard stays as a last resort but now warns loudly if it ever fires.git merge-base --is-ancestor and a fresh Docker repro that #2942/#2960 are intact and shipped in v1.228.0; re-verification note appended to the existing fix doc.The report came from a repository whose toolchain pins tofu. This repo's own examples/terraform-tests fixture is Terraform-only (it uses variable blocks that OpenTofu rejects), so eleven local repro runs never hit it; diffing raw -json streams from both tools on a minimal module exposed the missing progress field and the diagnostic ordering.
run detail unavailable (pass) and no file/line.components.terraform.command: tofu, one passing + one failing run, GITHUB_ACTIONS=true … --ci): JUnit tests="2" failures="1" with real names and line="12" on the failure; summary lists both runs with tests/min.tftest.hcl:12 in Details; ::error file=…,line=12 annotation emitted.examples/terraform-tests still yields tests="4" with all real run names.docs/fixes/2026-09-08-ci-test-json-opentofu-runs-dropped.mddocs/fixes/2026-08-19-emulator-endpoint-job-container-network-join.md (re-verification note)<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
Chores
<details> <summary>fix(ci): keep pinned atmos schema snapshots durable across deploys @osterman (#3092)</summary>
atmos.tools/schemas/atmos/atmos-manifest/1.228.0/atmos-manifest.json) 404ing shortly after every release.atmos-manifest/atmos-config snapshots for all 7 releases affected since the pinning feature shipped (v1.224.0-v1.228.0) directly in prod S3 (already live, no PR needed for that part)..github/scripts/s3-deploy-with-charset.sh and the 4 near-duplicate schema generate/publish steps in website-deploy-prod.yml into two reusable composite actions: .github/actions/s3-deploy and .github/actions/publish-atmos-schema.website/ (js-yaml, svgo, joi, colord) via pnpm.overrides, closing 7 open Dependabot alerts — all within-major patch bumps.website-deploy-prod.yml only regenerated the pinned per-release schema snapshot if: github.event_name == 'release', but every deploy (including ordinary pushes to main) ran aws s3 sync --delete against the same S3 prefix. Since a pinned snapshot from an older release was absent from that run's local build, --delete pruned it — so a pinned URL survived only until the next routine deploy. The docs' own example version (1.219.0) had already succumbed to this.--delete and publishes each release's new snapshot via a direct, non-deleting aws s3 cp, decoupling it from the routine sync's deletion scope..github/scripts/*.sh, per this repo's "CI scripts live in local actions" convention.git push-triggered security-remediate pass; the current branch already had an open diff, so the fixes landed here directly.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Improvements
<details> <summary>fix(auth): clear Azure realm MSAL cache on logout so re-login is fresh @aknysh (#3087)</summary>
atmos auth logout (including --all --force) now removes the realm-scoped Azure MSAL token cache (~/.azure/atmos/{realm}/msal_token_cache.json) in addition to the keyring entry and the Atmos device-code token it already cleared.~/.azure/msal_token_cache.json) is intentionally preserved — it is co-owned with a user's own az login session.azure/device-code and azure/interactive providers (interactive embeds device-code); azure/cli and azure/oidc never create a realm MSAL cache and are unaffected.atmos auth logout followed by atmos auth login did not pick up the new access — they kept getting 403 AuthorizationFailed (e.g. Microsoft.ContainerService/managedClusters/read), and atmos auth whoami showed the credential still expiring on the old session's clock.~/.cache/atmos/azure-device-code/<provider>/token.json) but never the realm MSAL cache — a different file — so the next login silently re-minted a token from the stale cached account/refresh token, which predated the PIM elevation.rm ~/.azure/atmos/<realm>/msal_token_cache.json). This makes logout actually forget the session, so re-login is genuinely fresh.az cache, and treats a missing cache as a clean no-op. Added a direct RemoveMSALCache unit test (realm removal, missing-file no-op, empty-realm safety guard, real os.Remove failure) and a Logout error-path test.resolveMSALCachePath 100%, NewMSALCache 100%, Logout 100%, RemoveMSALCache 90.9% — only the untestable os.UserHomeDir error return remains).go test ./pkg/auth/... green; atmos fix lint (patch-scoped CI gate) reports 0 issues.docs/fixes/2026-09-08-azure-logout-msal-cache-stale-session.mdazure/interactive), #2861 / #2890 (Azure CLI cache fixes)<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>fix: preserve prompted component/stack across profile-fallback re-exec @osterman (#3080)</summary>
Carries interactively-resolved component/stack values through a profile-fallback re-exec, so the re-exec'd child process doesn't re-prompt for values the user (or an earlier prompt) already supplied.
ReExecContext (pkg/auth/profile_fallback.go) distinguishes "resolved via prompt" from "supplied on the command line" via ComponentPrompted/StackPrompted flags on schema.ConfigAndStacksInfo — only prompted values are injected into the child's re-exec argv, since command-line-supplied values are already present in os.Args and re-adding them would duplicate a positional argument.
When an invalid identity config triggers the interactive profile fallback (auth.MaybeOfferProfileFallbackForIdentity), the process re-execs itself with the newly-picked profile. Previously, if component/stack had just been resolved via an interactive prompt (not passed as CLI args), the re-exec'd child had no record of that and prompted the user again for the same values — a redundant, confusing extra step in an already-interruptive flow.
pkg/auth/profile_fallback.go (ReExecContext, maybeOfferProfileFallback, reExecWithProfile)internal/exec/utils_auth.go (offerIdentityProfileFallback, resolveIdentityConfigError)cmd/terraform/shared/execution.go (promptMissingComponent/promptMissingStack now set the *Prompted flags)pkg/schema/schema.go (ConfigAndStacksInfo.ComponentPrompted / StackPrompted)<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Tests
<details> <summary>fix(terraform-ui): clean up terraform plan --ui output @osterman (#3083)</summary>
atmos terraform plan --ui that embedded a raw blank line from Terraform's multi-paragraph diagnostic detail, making the trailing address=/file=/line= metadata appear to jump to the far right of the terminal and wrap onto its own line.ordered_cache_behavior) in the plan tree's JSON attribute-diff rendering.# (N unchanged attributes hidden) footer to the plan tree, mirroring Terraform's own plan-output convention.tests/cli_describe_identity_test.go with a timeout.extractFirstSentence: it fell through to returning Terraform's entire multi-paragraph diagnostic detail (including the embedded blank line) instead of a single clean sentence, and was also picking the generic "derived from a deprecated source" lead-in over the actual, specific deprecation message. It now stops at the first paragraph break and prefers the specific, actionable final sentence.terraform show -json <planfile> subprocess (used to build the tree/summary after a successful plan) never received the component's effective environment (TF_DATA_DIR, credentials) the way the original plan/apply subprocess does, so it could fail independently of the plan itself — and that failure was silently discarded with zero indication anything went wrong. It now inherits the same environment, and any remaining failure is logged with the real subprocess stderr instead of a bare "exit status 1".jsoniter library's MarshalIndent, confirmed against a minimal standalone repro; ConvertToJSON now marshals compact with jsoniter and re-indents with stdlib encoding/json, which isn't subject to the bug.go test's global timeout) into a fast, attributable failure on just the affected subtest.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
<details> <summary>fix(secret): stop leaking the resolved --stack into viper's override layer @osterman (#3075)</summary>
parseScopeStack (cmd/secret/shared.go) and parseInitScope (cmd/secret/init.go) no longer write the resolved stack into viper's override layer with viper.Set. A stack chosen at the interactive prompt is now recorded on the command's own --stack flag via a small adoptPromptedStack helper, which the component completion still sees through viper's flag binding.cmd/secret/stack_override_test.go: the exact failing sequence (import --stack prod, then set --stack dev must load with dev), the prompted-stack propagation through the flag binding, and the empty-choice no-op.docs/fixes/2026-09-07-secret-stack-viper-override-leak.md.[race] non-acceptance test suite failed on a main push (run 34179504147) and on #3069 (run 34181209571), each time in one of the two global-scope secret set tests with no global declaration was found in the stack. Replaying the CI shuffle seeds locally reproduces it deterministically; unshuffled runs pass.secret command ran with --stack prod, the next command's --stack dev resolved to prod, its stack filter matched nothing, and the lookup failed. Bisected to TestRunSecretImport_FromStoreMode → global-scope set; a probe showed the pflag reset to "" while viper.GetString("stack") stayed "prod" even after SetDefault, i.e. the override layer.secret command per process.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Tests
Documentation
<details> <summary>fix(source): retry DNS/connect failures for JIT sources; clone JIT test fixtures locally @osterman (#3073)</summary>
isRetryableGitError (pkg/downloader/get_git.go) now recognises OS-level resolver and connect failures in git's own wording — could not resolve host, no such host, could not connect to server, failed to connect to, network is unreachable, name resolution — with tests for each plus a guard that a real 403 from the remote is still not retried.pkg/provisioner/source/vendor.go) always passes a retry policy to the git getter: the source's own retry: when set, otherwise a bounded default of 3 attempts with exponential backoff (1s→8s, 20% jitter). Only transient transport failures are retried; auth failures and missing refs still fail fast, and max_attempts: 1 opts out. The terraform/helmfile/packer source docs describe the default.TestJITSource_* and TestJITSource_MetadataComponentSubpath* acceptance tests clone from a throwaway local git::file:// repository (tests/jit_source_local_repo_test.go) instead of github.com — same go-getter git path (clone, ref=, depth=1, //subpath), no network, runs on all three OSes. The rewrite happens in each test's sandboxed copy of the fixture; the checked-in fixture keeps its real-world URIs. RequireGitHubAccess is dropped from the two tests that used it.docs/fixes/2026-09-07-jit-source-network-flakes.md.Acceptance Tests (windows, shard 2/10) on #3069 failed in TestJITSource_PackerOutput with Failed to connect to github.com:443 after 61 ms: Could not connect to server, right after the same job's checkout had hit Could not resolve host: github.com. On Windows, harden-runner's agent fronts DNS with a local proxy and installs a firewall allow-rule per resolved IP; under a test shard's process churn it occasionally drops a query or races the allow-rule. These blips recur several times a week (see the docs/fixes/ entries from 2026-08-10, 2026-09-02, 2026-09-03) and nothing in the affected PRs touches source provisioning.terraform plan with a JIT source fails on the same blip on a laptop or in their CI. Retrying only transport-level failures, with a bounded budget, fixes the user-facing behaviour without masking real errors.docs/fixes/2026-09-02-vendor-pull-dns-resolution-flake.md, docs/fixes/2026-09-03-harden-runner-windows-dns-restore-race.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
<details> <summary>fix(ci): never create a bulk-run status without a real component @osterman (#3058)</summary>
createCheckRun/updateCheckRun and harden FormatStatusContext so a CI status can never be created or referenced without a real, resolved component and stack.before.terraform.{plan,apply,destroy}.aggregate CI hook events, fired once the component graph is resolved and filtered, that create one real pending check-run per component up front for --affected/--all runs — mirroring the existing after-aggregate path.deploy (it already had a per-node after-hook but no before counterpart), gated so it never fires if a user before-hook aborts the node.defer in ExecuteTerraform so it's guaranteed to fire even if a later step errors and returns early.atmos terraform deploy --affected --upload-status (and --all, and plan/apply/destroy) created a pending GitHub commit status named atmos/deploy/<stack>/ — with no component, because bulk selection resolves its component list after the global before-hook already fired. That status was never updated, leaving PR checks stuck on "Waiting for status to be reported" forever, even though the run succeeded.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
<details> <summary>build(deps): bump github.com/containerd/containerd/v2 from 2.3.3 to 2.3.5 in the go_modules group across 1 directory @dependabot[bot] (#3098)</summary> Bumps the go_modules group with 1 update in the / directory: github.com/containerd/containerd/v2.
Updates github.com/containerd/containerd/v2 from 2.3.3 to 2.3.5
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/containerd/containerd/releases">github.com/containerd/containerd/v2's releases</a>.</em></p>
<blockquote>
<h2>containerd 2.3.5</h2>
<p>Welcome to the v2.3.5 release of containerd!</p>
<p>The fifth patch release for containerd 2.3 contains various fixes
and updates including security patches.</p>
<h3>Security Updates</h3>
<ul>
<li><strong>containerd</strong>
<ul>
<li><a href="https://github.com/containerd/containerd/security/advisories/GHSA-7jxh-36q5-gcqv"><strong>CVE-2026-53495</strong></a></li>
<li><a href="https://github.com/containerd/containerd/security/advisories/GHSA-rp3h-jf77-q9p4"><strong>GHSA-rp3h-jf77-q9p4</strong></a></li>
</ul>
</li>
</ul>
<h3>Highlights</h3>
<h4>Image Distribution</h4>
<ul>
<li>Apply hardening to strip sensitive authentication headers when fetching descriptor URLs (<a href="https://redirect.github.com/containerd/containerd/pull/14030">#14030</a>)</li>
</ul>
<h4>Runtime</h4>
<ul>
<li>Avoid hangs and data races when streaming container standard I/O in CRI (<a href="https://redirect.github.com/containerd/containerd/pull/14094">#14094</a>)</li>
<li>Fix missing error messages in OpenTelemetry trace attributes (<a href="https://redirect.github.com/containerd/containerd/pull/14049">#14049</a>)</li>
<li>Fix user and group lookup failures in container rootfs containing symlinked /etc/passwd or /etc/group (<a href="https://redirect.github.com/containerd/containerd/pull/13999">#13999</a>)</li>
<li>Fix configuration loading error when drop-in configuration files have a higher version than the root configuration (<a href="https://redirect.github.com/containerd/containerd/pull/13995">#13995</a>)</li>
<li>Avoid containerd startup hangs when loading shims (<a href="https://redirect.github.com/containerd/containerd/pull/13983">#13983</a>)</li>
<li>Add context to error when shim delete times out (<a href="https://redirect.github.com/containerd/containerd/pull/13921">#13921</a>)</li>
<li>Fix Windows Server 2022 container compatibility on host builds newer than the latest LTSC (<a href="https://redirect.github.com/containerd/platforms/pull/34">containerd/platforms#34</a>)</li>
</ul>
<h4>Snapshotters</h4>
<ul>
<li>Fix unpack failure for EROFS images containing the erofs OS feature (<a href="https://redirect.github.com/containerd/containerd/pull/14062">#14062</a>)</li>
</ul>
<p>Please try out the release binaries and report any issues at
<a href="https://github.com/containerd/containerd/issues">https://github.com/containerd/containerd/issues</a>.</p>
<h3>Contributors</h3>
<ul>
<li>Phil Estes</li>
<li>Samuel Karp</li>
<li>Derek McGowan</li>
<li>Sebastiaan van Stijn</li>
<li>Akhil Mohan</li>
<li>Maksym Pavlenko</li>
<li>Wei Fu</li>
<li>Oleh Konko</li>
<li>Austin Vazquez</li>
<li>Jing Chen</li>
<li>Martín Fernández</li>
<li>Paco Xu</li>
<li>XlabAI</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/containerd/containerd/commit/1294c24a7da8e5a793ed378161673abe94118892"><code>1294c24</code></a> Merge pull request <a href="https://redirect.github.com/containerd/containerd/issues/14092">#14092</a> from samuelkarp/prepare-release-2.3.5</li>
<li><a href="https://github.com/containerd/containerd/commit/db68d72b89bb8c71ef9686360618e7ab41075de3"><code>db68d72</code></a> Prepare release notes for v2.3.5</li>
<li><a href="https://github.com/containerd/containerd/commit/be419b070c178548c8e384d8bc3c8fe0ad6f154a"><code>be419b0</code></a> Merge commit from fork</li>
<li><a href="https://github.com/containerd/containerd/commit/84ea25bc1d7e9f71390ce9d647dbdec4408c05bc"><code>84ea25b</code></a> Merge commit from fork</li>
<li><a href="https://github.com/containerd/containerd/commit/5db0399a263911794a478fa64d8139ff88052976"><code>5db0399</code></a> Merge pull request <a href="https://redirect.github.com/containerd/containerd/issues/14094">#14094</a> from k8s-infra-cherrypick-robot/cherry-pick-14085-t...</li>
<li><a href="https://github.com/containerd/containerd/commit/9f6be869c8a6144dc66befde081d6e262b7c4c7d"><code>9f6be86</code></a> Fix data races and a deadlock in the byte stream helpers</li>
<li><a href="https://github.com/containerd/containerd/commit/9ec55f024041d0641f6d79841e45c8781141ddaa"><code>9ec55f0</code></a> cri: cancel ExecSync IO drain on context cancellation</li>
<li><a href="https://github.com/containerd/containerd/commit/c535779652bc8d541328a36ba598088c09819b97"><code>c535779</code></a> archive: skip redundant opaque whiteout walks</li>
<li><a href="https://github.com/containerd/containerd/commit/3684f8651b1183bae6964b1679102105097f0ec9"><code>3684f86</code></a> Merge pull request <a href="https://redirect.github.com/containerd/containerd/issues/14063">#14063</a> from k8s-infra-cherrypick-robot/cherry-pick-14057-t...</li>
<li><a href="https://github.com/containerd/containerd/commit/7459b1fc3732042ac6bbcd1851d6b48ace509a3f"><code>7459b1f</code></a> Merge pull request <a href="https://redirect.github.com/containerd/containerd/issues/14062">#14062</a> from k8s-infra-cherrypick-robot/cherry-pick-14012-t...</li>
<li>Additional commits viewable in <a href="https://github.com/containerd/containerd/compare/v2.3.3...v2.3.5">compare view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR@dependabot recreate will recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the Security Alerts page.</details> </details>
<details> <summary>fix(deps): update module github.com/gofrs/flock to v0.13.1 @renovate[bot] (#3091)</summary> This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| github.com/gofrs/flock | v0.13.0 → v0.13.1 |
<details> <summary>gofrs/flock (github.com/gofrs/flock)</summary>
v0.13.1Note truncated.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
feat: implement native Helm release lifecycle controls @shirkevich
<details> <summary>feat: implement native Helm release lifecycle controls @shirkevich (#2847)</summary>
release policy with release-wide defaults and operation-specific install, upgrade, and delete overlays.values: key decodes to null, keep inline and values_files template strings consistent, propagate top-level secrets, and honor command-local --mask=false.This is 2 of 4 in the native Helm lifecycle stack and is based on #2846:
release tree, including distinct install and upgrade timeouts and upgrade rollback plus cleanup policy.git diff --check, and generic fixture-name audit pass.docs/prd/native-helm-release-lifecycle.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>docs: define native Helm release lifecycle @shirkevich (#2846)</summary>
This is 1 of 4 in the native Helm lifecycle stack:
docs/prd/native-helm-release-lifecycle.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<details> <summary>ci: fix three post-release pipeline failures (summarizer egress, goreleaser 422, Homebrew) @aknysh (#3063)</summary>
.github/workflows/release.yml): add golang.org, go.dev, raw.githubusercontent.com, and dl.google.com to the summarize-notes job's harden-runner allowed-endpoints..github/workflows/build.yml): add --skip=publish to the GoReleaser step in the sign-and-attest-release job..github/workflows/build.yml): replace the broken dawidd6/action-homebrew-bump-formula with a direct brew bump-formula-pr call.docs/fixes/2026-09-06-*.md.Publishing v1.228.0 succeeded (release, binaries, Docker image, website all green), but three downstream jobs failed. None relate to the release contents — they are pre-existing pipeline gaps that were previously masked by the syft break fixed in #3061.
Set up Go with getaddrinfo EAI_AGAIN golang.org before any summarization ran: its egress allow-list lacked the toolchain hosts actions/setup-go resolves (golang.org/go.dev) and downloads from (raw.githubusercontent.com/dl.google.com). (This is not the 125k release-body overflow the summarizer guards against — the draft body was ~5 KB.)goreleaser release --clean against the already-published release; GoReleaser PATCHed target_commitish, which GitHub rejects on a published release (422 Validation Failed). The job only rebuilds dist/* for provenance attestation, so it must not publish — --skip=publish fixes it.undefined method 'safe_system' for module Homebrew. v8 has byte-identical code and the upstream Homebrew-5 fix was reverted, so bumping the action does not help. The wrapped command brew bump-formula-pr is fine, so this calls it directly (atmos is in homebrew-core).docs/fixes/2026-09-06-release-notes-summarizer-egress-golang-org.md, docs/fixes/2026-09-06-sign-and-attest-goreleaser-skip-publish.md, docs/fixes/2026-09-06-homebrew-bump-safe-system.md.brew bump-formula-pr command this PR automates, which pre-validates fix 3.release: published run; its fix doc records the manual fallback.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
<!-- end of auto-generated comment: release notes by coderabbit.ai --> </details>
<details> <summary>feat: add Helm lifecycle reporting and integration coverage @shirkevich (#2849)</summary>
release data to CI job summaries.hookOnly to watcher promotion.values_files targets in --affected selection, including files outside the chart directory.tests/fixtures/scenarios/helm-lifecycle.This is 4 of 4 in the native Helm lifecycle stack and is based on #2848:
--affected execution must react to the files whose values are rendered, not only to changes in the values_files list itself.components/helm and an unrelated-file negative control.hookOnly to watcher promotion is reported before the action at the default log level with its field path and machine-readable code; Debug output distinguishes derived policy from a directly configured watcher.--dependency-update; six objects include both weighted hooks and the preserved inline Helm template expression, and its full k3s workflow passes end to end.describe component confirms deep-merged stack and component release policy.git diff --check pass.docs/prd/native-helm-release-lifecycle.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
!secret options, global-scope secret management, and improved secret masking.Bug Fixes
Documentation
<details> <summary>feat: propagate component execution context @shirkevich (#2848)</summary>
--dependency-update support to chart-loading operations without hidden network access by default.This is 3 of 4 in the native Helm lifecycle stack and is based on #2847:
context.Background(), preventing signals and scheduler cancellation from consistently reaching active operations.git diff --check passes.docs/prd/native-helm-release-lifecycle.md<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
--dependency-update support for Helm template, apply, diff, and plan operations.Bug Fixes
Documentation
<details> <summary>fix(deps): update module github.com/agiledragon/gomonkey/v2 to v2.14.2 @renovate[bot] (#3067)</summary> This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| github.com/agiledragon/gomonkey/v2 | v2.14.0 → v2.14.2 |
<details> <summary>agiledragon/gomonkey (github.com/agiledragon/gomonkey/v2)</summary>
v2.14.2: Fix Darwin ARM64 same-page SIGBUS and private method patch corruptionwrite removes execute permission from its own active page (NOP isolation was only 4 KiB on 16 KiB pages)B plus an executable trampolineReference: #188
v2.14.1: Fix potential SIGBUS on Darwin</details>
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log. <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC42MS4zIiwidXBkYXRlZEluVmVyIjoiNDQuNjEuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsibm8tcmVsZWFzZSJdfQ==-->
</details>
<details> <summary>fix(deps): update module filippo.io/age to v1.3.2 @renovate[bot] (#3066)</summary> This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| filippo.io/age | v1.3.1 → v1.3.2 |
<details> <summary>FiloSottile/age (filippo.io/age)</summary>
v1.3.2: age v1.3.2age v1.3.2 is a minor release with a wide range of fixes and hardening improvements.
Some previously-accepted inputs are now rejected: headers over 2 MiB or 1024 recipients, malformed SSH keys in recipients files, and non-UTF-8 plaintext written to a terminal (force with -o -).
Pre-built binaries now cover windows/arm64 and darwin/amd64, and release archives include the compatibility plugins (age-plugin-pq, age-plugin-tag, and age-plugin-tagpq).
</details>
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log. <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC42MS4zIiwidXBkYXRlZEluVmVyIjoiNDQuNjEuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsibm8tcmVsZWFzZSJdfQ==-->
</details>
<details> <summary>fix(deps): update aws-sdk-go-v2 monorepo @renovate[bot] (#3044)</summary>
ℹ️ Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
<details> <summary>aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2)</summary>
v1.45.1github.com/aws/aws-sdk-go-v2/service/elasticache: v1.45.1
github.com/aws/aws-sdk-go-v2/service/iotmanagedintegrations: v1.0.0
github.com/aws/aws-sdk-go-v2/service/iotsitewise: v1.47.0
github.com/aws/aws-sdk-go-v2/service/rds: v1.94.1
v1.45.0github.com/aws/aws-sdk-go-v2/service/apigateway: v1.38.0
github.com/aws/aws-sdk-go-v2/service/athena: v1.56.0
github.com/aws/aws-sdk-go-v2/service/bedrock: v1.50.0
github.com/aws/aws-sdk-go-v2/service/bedrockagentcorecontrol: v1.14.0
github.com/aws/aws-sdk-go-v2/service/bedrockdataautomationruntime: v1.9.0
github.com/aws/aws-sdk-go-v2/service/bedrockruntime: v1.45.0
github.com/aws/aws-sdk-go-v2/service/cloudformation: v1.71.0
github.com/aws/aws-sdk-go-v2/service/computeoptimizerautomation: v1.0.0
github.com/aws/aws-sdk-go-v2/service/connect: v1.148.0
github.com/aws/aws-sdk-go-v2/service/controltower: v1.28.0
github.com/aws/aws-sdk-go-v2/service/ec2: v1.274.0
github.com/aws/aws-sdk-go-v2/service/ecr: v1.54.0
github.com/aws/aws-sdk-go-v2/service/eks: v1.75.0
github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2: v1.54.1
github.com/aws/aws-sdk-go-v2/service/invoicing: v1.9.0
github.com/aws/aws-sdk-go-v2/service/kinesisvideo: v1.33.0
github.com/aws/aws-sdk-go-v2/service/kms: v1.49.0
github.com/aws/aws-sdk-go-v2/service/lambda: v1.83.0
github.com/aws/aws-sdk-go-v2/service/lexmodelsv2: v1.58.0
github.com/aws/aws-sdk-go-v2/service/marketplaceentitlementservice: v1.35.0
github.com/aws/aws-sdk-go-v2/service/marketplacemetering: v1.35.0
github.com/aws/aws-sdk-go-v2/service/mediapackagev2: v1.34.0
github.com/aws/aws-sdk-go-v2/service/odb: v1.6.0
github.com/aws/aws-sdk-go-v2/service/organizations: v1.48.0
github.com/aws/aws-sdk-go-v2/service/qconnect: v1.24.0
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.98.0
github.com/aws/aws-sdk-go-v2/service/rds: v1.111.0
github.com/aws/aws-sdk-go-v2/service/redshift: v1.61.0
github.com/aws/aws-sdk-go-v2/service/redshiftserverless: v1.32.0
github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.226.0
github.com/aws/aws-sdk-go-v2/service/sagemakerruntimehttp2: v1.0.0
github.com/aws/aws-sdk-go-v2/service/securityir: v1.10.0
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.55.0
github.com/aws/aws-sdk-go-v2/service/transfer: v1.68.0
v1.44.0github.com/aws/aws-sdk-go-v2/service/apigateway: v1.37.0
github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.33.0
github.com/aws/aws-sdk-go-v2/service/backup: v1.54.0
github.com/aws/aws-sdk-go-v2/service/bcmpricingcalculator: v1.10.0
github.com/aws/aws-sdk-go-v2/service/bedrockruntime: v1.44.0
github.com/aws/aws-sdk-go-v2/service/billing: v1.9.0
github.com/aws/aws-sdk-go-v2/service/billingconductor: v1.27.0
github.com/aws/aws-sdk-go-v2/service/cloudtrail: v1.54.0
github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs: v1.60.0
github.com/aws/aws-sdk-go-v2/service/connectcampaignsv2: v1.9.0
github.com/aws/aws-sdk-go-v2/service/costexplorer: v1.60.0
github.com/aws/aws-sdk-go-v2/service/costoptimizationhub: v1.21.0
github.com/aws/aws-sdk-go-v2/service/datazone: v1.48.0
github.com/aws/aws-sdk-go-v2/service/dynamodb: v1.53.0
github.com/aws/aws-sdk-go-v2/service/ec2: v1.272.0
github.com/aws/aws-sdk-go-v2/service/ecr: v1.53.0
github.com/aws/aws-sdk-go-v2/service/ecs: v1.68.0
github.com/aws/aws-sdk-go-v2/service/emr: v1.56.0
github.com/aws/aws-sdk-go-v2/service/fsx: v1.64.0
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.68.0
github.com/aws/aws-sdk-go-v2/service/health: v1.35.0
github.com/aws/aws-sdk-go-v2/service/iam: v1.52.0
github.com/aws/aws-sdk-go-v2/service/inspector2: v1.45.0
github.com/aws/aws-sdk-go-v2/service/invoicing: v1.8.0
github.com/aws/aws-sdk-go-v2/service/lambda: v1.82.0
github.com/aws/aws-sdk-go-v2/service/mediaconnect: v1.46.0
github.com/aws/aws-sdk-go-v2/service/medialive: v1.87.0
github.com/aws/aws-sdk-go-v2/service/networkfirewall: v1.58.0
github.com/aws/aws-sdk-go-v2/service/networkflowmonitor: v1.11.0
github.com/aws/aws-sdk-go-v2/service/partnercentralchannel: v1.0.0
github.com/aws/aws-sdk-go-v2/service/route53: v1.60.0
github.com/aws/aws-sdk-go-v2/service/rum: v1.30.0
github.com/aws/aws-sdk-go-v2/service/s3: v1.91.0
github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.224.0
github.com/aws/aws-sdk-go-v2/service/secretsmanager: v1.40.0
github.com/aws/aws-sdk-go-v2/service/sfn: v1.40.0
github.com/aws/aws-sdk-go-v2/service/signin: v1.0.0
github.com/aws/aws-sdk-go-v2/service/sts: v1.41.0
github.com/aws/aws-sdk-go-v2/service/transcribestreaming: v1.33.0
v1.43.8github.com/aws/aws-sdk-go-v2: v1.43.8
github.com/aws/aws-sdk-go-v2/service/account: v1.36.0
github.com/aws/aws-sdk-go-v2/service/acmpca: v1.51.0
github.com/aws/aws-sdk-go-v2/service/autoscaling: v1.73.0
github.com/aws/aws-sdk-go-v2/service/billingconductor: v1.33.0
github.com/aws/aws-sdk-go-v2/service/cloudcontrol: v1.33.0
github.com/aws/aws-sdk-go-v2/service/cloudhsmv2: v1.38.0
github.com/aws/aws-sdk-go-v2/service/cloudwatchevents: v1.36.0
github.com/aws/aws-sdk-go-v2/service/codebuild: v1.73.0
github.com/aws/aws-sdk-go-v2/service/codegurureviewer: v1.38.0
github.com/aws/aws-sdk-go-v2/service/codepipeline: v1.50.0
github.com/aws/aws-sdk-go-v2/service/dataexchange: v1.45.0
github.com/aws/aws-sdk-go-v2/service/deadline: v1.37.0
github.com/aws/aws-sdk-go-v2/service/detective: v1.42.0
github.com/aws/aws-sdk-go-v2/service/devopsagent: v1.11.0
github.com/aws/aws-sdk-go-v2/service/directoryservice: v1.42.0
github.com/aws/aws-sdk-go-v2/service/drs: v1.44.0
github.com/aws/aws-sdk-go-v2/service/ec2: v1.323.0
github.com/aws/aws-sdk-go-v2/service/eks: v1.93.0
github.com/aws/aws-sdk-go-v2/service/emrcontainers: v1.46.0
github.com/aws/aws-sdk-go-v2/service/eventbridge: v1.49.0
github.com/aws/aws-sdk-go-v2/service/evs: v1.14.0
github.com/aws/aws-sdk-go-v2/service/frauddetector: v1.45.0
github.com/aws/aws-sdk-go-v2/service/fsx: v1.69.0
github.com/aws/aws-sdk-go-v2/service/globalaccelerator: v1.39.0
github.com/aws/aws-sdk-go-v2/service/iamtoolbox: v1.0.0
github.com/aws/aws-sdk-go-v2/service/inspector: v1.34.0
github.com/aws/aws-sdk-go-v2/service/iot: v1.78.0
github.com/aws/aws-sdk-go-v2/service/iotsecuretunneling: v1.37.0
github.com/aws/aws-sdk-go-v2/service/iottwinmaker: v1.33.0
github.com/aws/aws-sdk-go-v2/service/ivs: v1.56.0
github.com/aws/aws-sdk-go-v2/service/ivsrealtime: v1.38.0
github.com/aws/aws-sdk-go-v2/service/licensemanager: v1.42.0
github.com/aws/aws-sdk-go-v2/service/marketplacecatalog: v1.46.0
github.com/aws/aws-sdk-go-v2/service/marketplacemetering: v1.40.3
github.com/aws/aws-sdk-go-v2/service/mediapackage: v1.43.0
github.com/aws/aws-sdk-go-v2/service/mediapackagevod: v1.43.0
github.com/aws/aws-sdk-go-v2/service/mediastore: v1.33.0
github.com/aws/aws-sdk-go-v2/service/networkmanager: v1.45.0
github.com/aws/aws-sdk-go-v2/service/outposts: v1.68.0
github.com/aws/aws-sdk-go-v2/service/paymentcryptography: v1.34.0
github.com/aws/aws-sdk-go-v2/service/pi: v1.40.0
github.com/aws/aws-sdk-go-v2/service/qconnect: v1.35.0
github.com/aws/aws-sdk-go-v2/service/resourceexplorer2: v1.28.0
github.com/aws/aws-sdk-go-v2/service/servicecatalogappregistry: v1.39.0
github.com/aws/aws-sdk-go-v2/service/servicediscovery: v1.44.0
github.com/aws/aws-sdk-go-v2/service/shield: v1.38.0
github.com/aws/aws-sdk-go-v2/service/signer: v1.36.0
github.com/aws/aws-sdk-go-v2/service/storagegateway: v1.47.0
github.com/aws/aws-sdk-go-v2/service/swf: v1.38.0
github.com/aws/aws-sdk-go-v2/service/transcribestreaming: v1.39.0
github.com/aws/aws-sdk-go-v2/service/transfer: v1.76.0
github.com/aws/aws-sdk-go-v2/service/translate: v1.37.0
github.com/aws/aws-sdk-go-v2/service/voiceid: v1.34.0
github.com/aws/aws-sdk-go-v2/service/vpclattice: v1.27.0
github.com/aws/aws-sdk-go-v2/service/wafv2: v1.78.0
github.com/aws/aws-sdk-go-v2/service/wisdom: v1.36.0
github.com/aws/aws-sdk-go-v2/service/workspacesthinclient: v1.24.0
github.com/aws/aws-sdk-go-v2/service/xray: v1.40.0
v1.43.7github.com/aws/aws-sdk-go-v2/service/aiops: v1.7.0
github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: v1.28.0
github.com/aws/aws-sdk-go-v2/service/apprunner: v1.40.0
github.com/aws/aws-sdk-go-v2/service/backup: v1.57.0
github.com/aws/aws-sdk-go-v2/service/batch: v1.65.0
github.com/aws/aws-sdk-go-v2/service/bcmdataexports: v1.16.0
github.com/aws/aws-sdk-go-v2/service/bedrockagentcore: v1.27.0
github.com/aws/aws-sdk-go-v2/service/bedrockagentcorecontrol: v1.40.0
github.com/aws/aws-sdk-go-v2/service/bedrockdataautomation: v1.15.0
github.com/aws/aws-sdk-go-v2/service/billing: v1.11.0
github.com/aws/aws-sdk-go-v2/service/budgets: v1.43.7
github.com/aws/aws-sdk-go-v2/service/chimesdkidentity: v1.28.0
github.com/aws/aws-sdk-go-v2/service/chimesdkmediapipelines: v1.27.0
github.com/aws/aws-sdk-go-v2/service/cleanrooms: v1.45.0
github.com/aws/aws-sdk-go-v2/service/cleanroomsml: v1.24.0
github.com/aws/aws-sdk-go-v2/service/codeconnections: v1.11.0
github.com/aws/aws-sdk-go-v2/service/connecthealth: v1.2.0
github.com/aws/aws-sdk-go-v2/service/controlcatalog: v1.15.0
github.com/aws/aws-sdk-go-v2/service/datazone: v1.62.0
github.com/aws/aws-sdk-go-v2/service/devopsguru: v1.41.0
github.com/aws/aws-sdk-go-v2/service/emrserverless: v1.41.0
github.com/aws/aws-sdk-go-v2/service/evs: v1.10.0
github.com/aws/aws-sdk-go-v2/service/greengrassv2: v1.43.0
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.78.0
github.com/aws/aws-sdk-go-v2/service/identitystore: v1.37.0
github.com/aws/aws-sdk-go-v2/service/iotmanagedintegrations: v1.10.0
github.com/aws/aws-sdk-go-v2/service/ivschat: v1.22.0
github.com/aws/aws-sdk-go-v2/service/keyspacesstreams: v1.7.0
github.com/aws/aws-sdk-go-v2/service/kinesisvideowebrtcstorage: v1.21.0
github.com/aws/aws-sdk-go-v2/service/managedblockchainquery: v1.23.0
github.com/aws/aws-sdk-go-v2/service/marketplaceagreement: v1.16.0
github.com/aws/aws-sdk-go-v2/service/mediapackagev2: v1.39.0
github.com/aws/aws-sdk-go-v2/service/medicalimaging: v1.26.0
github.com/aws/aws-sdk-go-v2/service/notifications: v1.8.0
github.com/aws/aws-sdk-go-v2/service/observabilityadmin: v1.16.0
github.com/aws/aws-sdk-go-v2/service/odb: v1.11.0
github.com/aws/aws-sdk-go-v2/service/osis: v1.22.0
github.com/aws/aws-sdk-go-v2/service/partnercentralchannel: v1.2.0
github.com/aws/aws-sdk-go-v2/service/pcaconnectorscep: v1.12.0
github.com/aws/aws-sdk-go-v2/service/pipes: v1.24.0
github.com/aws/aws-sdk-go-v2/service/redshiftserverless: v1.35.0
github.com/aws/aws-sdk-go-v2/service/resiliencehub: v1.36.0
github.com/aws/aws-sdk-go-v2/service/resourcegroupstaggingapi: v1.32.0
github.com/aws/aws-sdk-go-v2/service/rolesanywhere: v1.23.0
github.com/aws/aws-sdk-go-v2/service/route53globalresolver: v1.3.0
github.com/aws/aws-sdk-go-v2/service/s3tables: v1.16.0
github.com/aws/aws-sdk-go-v2/service/sagemakeredge: v1.32.0
github.com/aws/aws-sdk-go-v2/service/sagemakergeospatial: v1.20.0
github.com/aws/aws-sdk-go-v2/service/scheduler: v1.18.0
github.com/aws/aws-sdk-go-v2/service/servicediscovery: v1.40.0
github.com/aws/aws-sdk-go-v2/service/servicequotas: v1.35.0
github.com/aws/aws-sdk-go-v2/service/ssmquicksetup: v1.9.0
github.com/aws/aws-sdk-go-v2/service/workspacesthinclient: v1.21.0
v1.43.6v1.43.5github.com/aws/aws-sdk-go-v2: v1.41.5
github.com/aws/aws-sdk-go-v2/service/accessanalyzer: v1.45.12
github.com/aws/aws-sdk-go-v2/service/account: v1.30.5
github.com/aws/aws-sdk-go-v2/service/acm: v1.37.23
github.com/aws/aws-sdk-go-v2/service/acmpca: v1.46.12
github.com/aws/aws-sdk-go-v2/service/aiops: v1.6.21
github.com/aws/aws-sdk-go-v2/service/amp: v1.42.9
github.com/aws/aws-sdk-go-v2/service/amplify: v1.38.14
github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.32.20
github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.28.20
github.com/aws/aws-sdk-go-v2/service/apigateway: v1.39.1
github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.29.14
github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.34.1
github.com/aws/aws-sdk-go-v2/service/appconfig: v1.43.13
github.com/aws/aws-sdk-go-v2/service/appconfigdata: v1.23.22
github.com/aws/aws-sdk-go-v2/service/appfabric: v1.16.21
github.com/aws/aws-sdk-go-v2/service/appflow: v1.51.12
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.37.7
github.com/aws/aws-sdk-go-v2/service/applicationautoscaling: v1.41.14
github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: [v1.27.12](service/applicationcostprofiler✂ Note
PR body was truncated to here.
</details>
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log. <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC42MS4zIiwidXBkYXRlZEluVmVyIjoiNDQuNjEuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsibm8tcmVsZWFzZSJdfQ==-->
</details>
<details> <summary>chore(deps): update terraform http to v3.6.1 @[renovate[bot]](https://github.com/apps/ren
Note truncated.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
ci: install syft for GoReleaser SBOM generation @aknysh
create_namespace setting to native Helm components @aknysh (#3034)3a39a05 to d7e1218 @dependabot[bot] (#3013)025b74b to b8c3669 in /.devcontainer @dependabot[bot] (#3014)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.
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.
One column per quarter.