Skip to content

ci: update to actions/checkout@v6#2062

Merged
folkertdev merged 1 commit intorust-lang:mainfrom
clado:github-action-checkout-v6
Mar 13, 2026
Merged

ci: update to actions/checkout@v6#2062
folkertdev merged 1 commit intorust-lang:mainfrom
clado:github-action-checkout-v6

Conversation

@clado
Copy link

@clado clado commented Mar 12, 2026

CI is showing a lot of warnings (72) right now. They are generally of the following type:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/

I don't anticipate that bumping the checkout action to v6 / Node.js 24 will cause any issues. (While Node.js 24 drops support for ARM32 and macOS versions <= 13.4, this shouldn't break anything because we use Docker to test in those environments, not github runners natively.) But! If it does cause issues it's probably better to find out now rather than by surprise 3 months from now... :)

ci is showing a lot of warnings (72) right now. apparently
actions/checkout@v4 uses Node.js 20, and all github actions are
scheduled to be force opted-in to Node.js 24 on 2026-06-02.
I don't anticipate bumping the checkout action to v6 / Node.js 24
to cause any issues (Node.js 24 drops support for ARM32 and macOS
versions <= 13.4, but this shouldn't matter because we use Docker
to test in those environments, not github runners natively) but if
it does cause issues it's probably better to find out now rather
than by surprise 3 months from now... :)
@rustbot
Copy link
Collaborator

rustbot commented Mar 12, 2026

r? @sayantn

rustbot has assigned @sayantn.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: @Amanieu, @folkertdev, @sayantn
  • @Amanieu, @folkertdev, @sayantn expanded to Amanieu, folkertdev, sayantn
  • Random selection from Amanieu, folkertdev, sayantn

@folkertdev folkertdev added this pull request to the merge queue Mar 13, 2026
Merged via the queue into rust-lang:main with commit 6bd468c Mar 13, 2026
77 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants