chore: upgrade action runtime to Node 24

[John C. Bland II (johncblandii)]

what

• Change the action runtime from node20 to node24 in action.yml

why

• GitHub is deprecating the Node 20 runtime; actions declaring runs.using: node20 emit a
  deprecation warning for every consumer and are already being force-migrated to Node 24
• Declaring node24 makes the migration deliberate rather than implicit
• The committed dist/ bundle is unchanged (no source changes, so check-dist still matches);
  it was smoke-tested locally under Node 24, and this repo's integration tests exercise the bundle
  end-to-end via uses: ./ on this PR, now running on Node 24

references

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

[Copilot]

Pull request overview

Updates the GitHub Action metadata to explicitly run the bundled JavaScript action on the Node 24 runtime, aligning the action with GitHub Actions runner runtime deprecations/migrations.

Changes:

• Switched runs.using in action.yml from node20 to node24.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[John C. Bland II (johncblandii)]

Note: the build-and-test failures on this PR are pre-existing and unrelated to the runtime bump — the identical unit/integration failures (atmos_cli_config.components.terraform.base_path resolving to empty) appear on unrelated Renovate PRs since 2026-08-10 (e.g. run 31443943285), which points at a behavior change in the latest atmos release pulled in via atmos-version: latest. The single setting job additionally hit a transient 503 downloading the atmos release binary.

[John C. Bland II (johncblandii)]

Root-caused and fixed the pre-existing CI failures in this PR (e92f46b): atmos v1.225.0 removed atmos_cli_config from describe component output — bisected locally: v1.224.0 emits .atmos_cli_config.components.terraform.base_path = components/terraform, v1.225.0 and v1.226.0-rc.6 emit null. Since the test workflows install atmos-version: latest, every PR here has been red since Aug 10.

• CI now pins atmos-version: 1.224.0 (last good release) in all three setup-atmos steps, with a comment pointing at the upstream issue.
• Filed regression: describe component no longer emits atmos_cli_config (v1.225.0+) atmos#2933 for the regression — note this breaks consumers of this action reading atmos_cli_config.*, not just CI, so it needs an upstream fix or a documented replacement.

[John C. Bland II (johncblandii)]

Update per review feedback — the earlier version-pin is gone; this is edition-gated behavior with a supported knob, not a hard regression (3926b9d):

• Root cause refined: atmos edition 2026-07-17 (first shipped in v1.225.0) flips the describe.component.filter default from full to schema, which drops computed sections like atmos_cli_config from describe component output (atmos list editions documents it).
• Action fix: runAtmosDescribeComponent now sets ATMOS_DESCRIBE_COMPONENT_FILTER=full (respecting an explicit override from the caller), so settings-paths keep resolving for every consumer on any atmos version — dist/ rebuilt with the repo toolchain.
• The atmos-version: 1.224.0 CI pins are reverted; tests run on latest again.
• Verified locally: 9/9 unit tests pass against atmos 1.224.0, 1.225.0, and 1.226.0-rc.6.

Tracking issue cloudposse/atmos#2933 updated accordingly. (Separate note for maintainers: runAtmosDescribeComponent interpolates component/stack into an execSync shell string — pre-existing, but worth migrating to execFileSync with an argv array in a follow-up.)

[John C. Bland II (johncblandii)]

Phase-2 follow-up now that cloudposse/.github#261 is merged: the repo's own workflow pins are bumped to Node 24 runtimes, SHA-pinned (checkout # v7.0.1, setup-node # v7.0.0, setup-atmos # v3.5.0, assert-action # v4.0.1).

[github-actions]

These changes were released in v2.0.3.