NuGet/login needs to be updated to a later node.js version

[richlander]

NuGet Product Used

Other/NA

Product Version

v1

Worked before?

No response

Impact

None

Repro Steps & Context

I see this on my repos that use NuGet Trusted Publishing. Is there a plan to resolve this before the date?

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

Verbose Logs

[richlander]

@Lanaparezanin

[Lanaparezanin]

Thank you for bringing this to my attention @richlander! Will work on resolving this by end of month.

[richlander]

Thanks! I'll upgrade when its ready.

I'd recommend creating a plan for node upgrades to stay ahead of the deprecation warnings.

[Lanaparezanin]

Update: we are currently testing a GH action that will automatically upgrade the node version, to stay ahead of the deprecation process. Will update this thread as soon as all is fixed.

[baywet]

Hey everyone,
Seeing this warning all over the place, I'll send a couple of PRs to help making progress in this direction (and others for general repository health).

• fix: adds an engine requirement to align with action requirement #18 so that when running the code, it's aligned with the versions requirements. Your update workflow will need to keep this in sync.
• ci: adds a validation workflow #19 adds a validation workflow to ensure that things at least build before a PR gets merged, the auto-update workflow will need to be amended to account for that one as well.
• ci: adds a workflow to update floating tags #21 handle re-tagging automatically when patch/minor versions are published.

Additionally:

• you should consider setting up release please to automate version creations from conventional commits
• you should consider updating your workflow so it uses a conventional commit (thus automating the release down the road)
• you should consider GH copilot instructions to use conventional commits.
• you should consider automating version updates in the readme (release please can do that for you)
• you'll NEED TO update your workflow to use an app registration so it can actually create pull requests. Here is an example of a similar workflow. https://github.com/BinkyLabs/openapi-overlays-dotnet/blob/main/.github/workflows/promote-shipped-apis.yml (happy to discuss the app management/transfer aspects with you on Teams)

Happy to submit PRs for those other points, but I thought I should pause here to avoid spamming. I hope this helps!