Skip to content

chore(deps): update terraform cloudposse/stack-config/yaml to v2#46

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/cloudposse-stack-config-yaml-2.x
Closed

chore(deps): update terraform cloudposse/stack-config/yaml to v2#46
renovate[bot] wants to merge 1 commit intomainfrom
renovate/cloudposse-stack-config-yaml-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 20, 2026

This PR contains the following updates:

Package Type Update Change
cloudposse/stack-config/yaml (source) module major 1.8.02.0.0

Release Notes

cloudposse/terraform-yaml-stack-config (cloudposse/stack-config/yaml)

v2.0.0

Compare Source

Update cloudposse/utils provider to v2.0.0 @​aknysh (#​110)

what

  • Update cloudposse/utils provider version constraint to >= 2.0.0, < 3.0.0 across all 13 versions.tf files (root module, 6 child modules, 6 examples)
  • Remove the old < 2.0.0 upper bound from modules/remote-state that was blocking the v2 upgrade
  • Apply the < 3.0.0 upper bound consistently across all modules (previously only modules/remote-state had an upper bound)

why

  • The cloudposse/utils provider v1.x embeds Atmos v1.189.0, which panics when it encounters newer atmos.yaml features (stores, hooks, templates.settings.gomplate, !terraform.state YAML tags). This causes a critical "Plugin did not respond" crash in data "utils_component_config", blocking all components that use the remote-state module (56+ components in a typical infrastructure repo)
  • Provider v2.0.0 upgrades the embedded Atmos from v1.189.0 to v1.207.0, which can parse all current atmos.yaml features without crashing
  • The < 3.0.0 upper bound is applied consistently to all modules and examples to guard against future breaking changes in the provider, following the same pattern previously used only in modules/remote-state
  • This is a major version bump because users on older Atmos CLI versions (< 1.200) were unaffected by the crash and may need to verify compatibility after upgrading

references

Generate readme for submodules @​goruha (#​109)

what

  • Generate readme for submodules

why

  • Allow all to keep the README updated

references

🤖 Automatic Updates

Fix go version in tests @​osterman (#​108)

what

  • Update go 1.24

why

  • Error loading shared library libresolv.so.2 in Go 1.20

References

Replace Makefile with atmos.yaml @​osterman (#​107)

what

  • Remove Makefile
  • Add atmos.yaml

why

  • Replace build-harness with atmos for readme genration

References

  • DEV-3229 Migrate from build-harness to atmos

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@mergify mergify Bot added auto-update This PR was automatically generated needs-test Needs testing labels Feb 20, 2026
@renovate renovate Bot force-pushed the renovate/cloudposse-stack-config-yaml-2.x branch from ab4a408 to e3eeb2b Compare March 13, 2026 16:05
@Benbentwo
Copy link
Copy Markdown
Contributor

Superseded by #48

@Benbentwo Benbentwo closed this Mar 20, 2026
auto-merge was automatically disabled March 20, 2026 16:55

Pull request was closed

@Benbentwo Benbentwo deleted the renovate/cloudposse-stack-config-yaml-2.x branch March 20, 2026 16:55
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Mar 20, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-update This PR was automatically generated needs-test Needs testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants