Bump actions/setup-python@v5 → @v6 to remove Node.js 20 deprecation warning

Open Beginner friendly
#74 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
github-actions, python
Domain
ci-cd

Research direction

Open action.yml on the v3-beta branch and inspect the composite action step that uses actions/setup-python. Update the action reference from @v5 to @v6, then verify that the workflow still supplies Python 3.10 and that consumers no longer receive the Node.js 20 deprecation annotation.

Written by the indexing model from the issue text.

Description

Summary

microsoft/ai-agent-evals@v3-beta pins actions/setup-python@v5, which targets Node.js 20. Every consumer of this action now sees a deprecation warning on every workflow run:

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The runner is currently auto-forcing Node.js 24, but the warning clutters the annotations panel on every workflow run and will eventually become a hard failure when GitHub removes Node 20 support entirely.

Current code

action.yml v3-beta:

runs:
  using: composite
  steps:
    - name: Set up Python
      uses: actions/setup-python@v5   # ← Node 20
      with:
        python-version: "3.10"

Fix

Bump the pin to @v6, which targets Node 24 natively.

    - name: Set up Python
-     uses: actions/setup-python@v5
+     uses: actions/setup-python@v6
      with:
        python-version: "3.10"

actions/setup-python@v6 has been out since 2025 and is at v6.3.0 as of 2026-06-24. It is a drop-in replacement for @v5 — same inputs, same outputs — and eliminates the deprecation warning without any consumer changes.

Verification

actions/setup-python@v6.x targets Node.js 24 per release notes. No breaking API changes vs. v5 for the python-version input.

Acceptance

  • Consumers of microsoft/ai-agent-evals@v3-beta no longer see the "Node.js 20 is deprecated" annotation on every run.
  • No behavioural change to the eval step itself.

Happy to open a PR for this if it helps.

Dominant language
Python
Stars
103
Forks
26
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/ai-agent-evals

All issues in microsoft/ai-agent-evals

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.