chore(deps): update cloudposse/github-action-setup-atmos action to v3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-setup-atmos	action	major	v2 → v3

---

Release Notes

cloudposse/github-action-setup-atmos (cloudposse/github-action-setup-atmos)

v3.2.0

Compare Source

fix: install-wrapper silent no-op regression @​osterman (#​115)

what

• Add a real, unmocked integration test (wrapper-cache-integration.test.ts) that runs the installer's actual tc.cacheDir() copy and then spawns the resulting atmos wrapper as a real child process.
• Add a focused test (wrapper-entrypoint.test.ts) that runs the compiled dist/wrapper/index.js directly, isolated from the installer/tool-cache entirely.
• Add a mocked-level regression guard in setup-atmos.test.ts for the install-wrapper: true fresh-install cache path.
• Add an assertion to the integration CI job in main.yml so it fails if the wrapper's stdout output comes back empty.

why

• Users reported that atmos terraform deploy/apply steps with install-wrapper: true complete instantly with exit code 0 and zero output — a silent no-op.
• These new tests reproduce that exact symptom today (empty stdout, exit code 0), pinpointing the cause: dist/wrapper/index.js's if (require.main === module) entry guard evaluates to false once bundled by @vercel/ncc, so runWrapper() is never invoked in production.
• Existing tests never caught this because wrapper.test.ts imports and calls runWrapper() directly, bypassing the guard, and the CI integration job printed wrapper output without ever asserting it was non-empty.
• This PR is reproduction-only (per request); the actual entry-guard fix is a follow-up.

references

• Reported in the community Slack thread about github-action-setup-atmos@v3.

v3.1.0

Compare Source

Fix setup-atmos Windows installs @​osterman (#​111)

what

• Fix release asset parsing for Windows .exe assets and install runnable atmos.exe/wrapper shims across OSes.
• Add checksum validation input defaulting to warn, 80% coverage enforcement, expanded Jest tests, and OS/mode CI matrix.
• Rebuild committed dist/ artifacts.

why

• Windows runners need atmos immediately after setup for wrapper and no-wrapper modes.
• Checksum validation catches corrupted downloads while preserving current behavior when checksums are missing.

references

• Validation: npm run format:check, npm run lint:check, npm run test:coverage -- --runInBand, npm run clean && npm run build && npm run build:wrapper.

v3.0.0

Compare Source

Update Node version from 20 to 24 in action.yml @​goruha (#​108)

what

• Upgrade Node 24

why

• Node 20 is deprecated

References

• https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

v3

Compare Source

---

Configuration

📅 Schedule: (UTC)

• 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.