Skip to content

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2 #128

Closed

Description

@Denny-g6labs

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Activity

  1. shannonwhitworth commented on Mar 19, 2026

    @shannonwhitworth

    Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

    Bumping this ☝️

    Please can you confirm if any action is being taken (or is at least planned) to address this issue? The deprecation date for Node.js 20 on GH actions runners was September 19, 2025

  2. Cupprum commented on Mar 28, 2026

    @Cupprum

    Apparently AWS SAM CLI is already part of Ubuntu runners -> https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2404-Readme.md#cli-tools

    So i just deleted this action from my action

    Edit: mistook runner for action

  3. Denny-g6labs commented on Mar 29, 2026

    @Denny-g6labs
    Author

    Trying...

  4. Denny-g6labs commented on Mar 29, 2026

    @Denny-g6labs
    Author

    Worked!

  5. rivierch commented on Apr 1, 2026

    @rivierch
    Contributor

    thanks @Cupprum suppress usage of setup-sam works for me.

  6. kylegirard commented on Apr 9, 2026

    @kylegirard

    Confirmed that is now built into the runners. Removed setup-sam actions and everything still works. Thanks, @Cupprum.

  7. wilkinsocks commented on Apr 24, 2026

    @wilkinsocks
    Contributor

    I've actually only just seen this issue 😅

    I've submitted a pull request to resolve this regardless: #136

    There's most likely still value in having an action which could allow more features to define finer grained control over SAM rather than relying on the runner image

  8. reedham-aws commented on May 1, 2026

    @reedham-aws

    Thank you @wilkinsocks for your PR. We have merged it and released a new version 3.0.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions