# This workflow uses actions that are not certified by GitHub. # They are provided by a third-party and are governed by # separate terms of service, privacy policy, and support # documentation.😕 Question: why bump python version and not action version? Is there a reason?

          😕 Question: why bump python version and not action version? Is there a reason?

Please see setup-python action releases Note the changes for version v5 includes migrating the underlying node version (which fixes a deprecated version just like the 3.8 to 3.13 does).

I recommend something like this:

        uses: actions/setup-python@v5
        with:
          python-version: "3.13"  # set this to the python version to use (see https://github.com/actions/setup-python?tab=readme-ov-file#basic-usage)

[!CAUTION]
Also please note that python-versions after 3.10 and non-cpython need quoting to properly function in some GitHub Action Runner Environments (in contrast with 3.8 which did not need quotes); compare with the format used in ci/pylint.yml where quotes are used.

Benefits of these changes:

• Syntacticly Correct: Uses quotes around python-version correctly.
• Consistency in Comments: Helps keep comments consistent with other changes in this PR.
• Improved Security: Both the original version bump to 3.13 and the setup-python version bump to v5 are important for remaining current with security updates.

Originally posted by @reactive-firewall in https://github.com/actions/starter-workflows/pull/2584#discussion_r1835009893

Start by reviewing the workflow context and the referenced ci/pylint.yml, then compare the current setup-python usage with the v5 release notes. Done means the relevant workflow uses the intended action and Python versions, quotes versions consistently, and its checks pass.