⬆ Bump actions/setup-python from 2 to 5

[dependabot]

Bumps actions/setup-python from 2 to 5.

Release notes

Sourced from actions/setup-python's releases.

v5.0.0

What's Changed

In scope of this release, we update node version runtime from node16 to node20 (actions/setup-python#772). Besides, we update dependencies to the latest versions.

Full Changelog: actions/setup-python@v4.8.0...v5.0.0

v4.8.0

What's Changed

In scope of this release we added support for GraalPy (actions/setup-python#694). You can use this snippet to set up GraalPy:

steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v4 
  with:
    python-version: 'graalpy-22.3' 
- run: python my_script.py

Besides, the release contains such changes as:

• Trim python version when reading from file by @​FerranPares in actions/setup-python#628
• Use non-deprecated versions in examples by @​jeffwidman in actions/setup-python#724
• Change deprecation comment to past tense by @​jeffwidman in actions/setup-python#723
• Bump @​babel/traverse from 7.9.0 to 7.23.2 by @​dependabot in actions/setup-python#743
• advanced-usage.md: Encourage the use actions/checkout@v4 by @​cclauss in actions/setup-python#729
• Examples now use checkout@v4 by @​simonw in actions/setup-python#738
• Update actions/checkout to v4 by @​dmitry-shibanov in actions/setup-python#761

New Contributors

• @​FerranPares made their first contribution in actions/setup-python#628
• @​timfel made their first contribution in actions/setup-python#694
• @​jeffwidman made their first contribution in actions/setup-python#724

Full Changelog: actions/setup-python@v4...v4.8.0

v4.7.1

What's Changed

• Bump word-wrap from 1.2.3 to 1.2.4 by @​dependabot in actions/setup-python#702
• Add range validation for toml files by @​dmitry-shibanov in actions/setup-python#726

Full Changelog: actions/setup-python@v4...v4.7.1

v4.7.0

In scope of this release, the support for reading python version from pyproject.toml was added (actions/setup-python#669).

      - name: Setup Python
        uses: actions/setup-python@v4
</tr></table> 

... (truncated)

Commits

• 0b93645 Enhance workflows: Add macOS 13 support, upgrade publish-action, and update d...
• 9c76e71 Bump pillow from 7.2 to 10.2.0 in /tests/data (#956)
• f4c5a11 Revise isGhes logic (#963)
• 19dfb7b Bump default versions to latest (#905)
• e9675cc Merge pull request #943 from actions/Jcambass-patch-1
• 3226af6 Upgrade IA publish
• 70dcb22 Merge pull request #941 from actions/Jcambass-patch-1
• 65b48c7 Create publish-immutable-actions.yml
• 29a37be initial commit (#938)
• f677139 Bump pyinstaller from 3.6 to 5.13.1 in /tests/data (#923)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

CI:

• Update GitHub Actions workflows to use actions/setup-python version 5 instead of version 2.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the GitHub Action actions/setup-python from version 2 to version 5 across multiple workflow files. The update brings several improvements including Node.js runtime update to node20, GraalPy support, and various dependency updates. The changes are straightforward version number updates in the workflow files.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update actions/setup-python action version across GitHub workflow files	Update setup-python action from v2 to v5 in requirement controller workflow Update setup-python action from v2 to v5 in deploys workflow Update setup-python action from v2/v4 to v5 in release generation workflow Update setup-python action from v2 to v5 in refactor workflow Update setup-python action from v2 to v5 in release workflow	.github/workflows/requirement_controller.yml .github/workflows/deploys.yml .github/workflows/release_generation.yml .github/workflows/refactor.yml .github/workflows/release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

(Checks updated until commit 09ac58e)

Action: windows

Failed stage: Install Dependencies [❌]

Failure summary: The action failed due to a dependency conflict between the required versions of the jinja2 package: gpt-computer-agent version 0.22.4 requires jinja2==3.1.4. litellm version 1.40.8 requires jinja2 version >=3.1.2 and <4.0.0. pywifi-controls version 0.7 requires jinja2==3.1.2 specifically for Windows. This conflict makes it impossible to resolve the dependencies as specified.

Relevant error logs: 1: ##[group]Operating System 2: Microsoft Windows Server 2022 ... 875: Collecting soupsieve>1.2 (from beautifulsoup4==4.12.3->gpt_computer_agent==0.22.4) 876: Downloading soupsieve-2.6-py3-none-any.whl.metadata (4.6 kB) 877: Collecting curl-cffi>=0.6.2 (from duckduckgo-search==5.3.0->gpt_computer_agent==0.22.4) 878: Downloading curl_cffi-0.7.4-cp38-abi3-win_amd64.whl.metadata (12 kB) 879: Collecting orjson>=3.10.0 (from duckduckgo-search==5.3.0->gpt_computer_agent==0.22.4) 880: Downloading orjson-3.10.12-cp311-none-win_amd64.whl.metadata (42 kB) 881: Requirement already satisfied: setuptools in c:\hostedtoolcache\windows\python\3.11.9\x64\lib\site-packages (from open-interpreter==0.2.6->gpt_computer_agent==0.22.4) (65.5.0) 882: INFO: pip is looking at multiple versions of pywifi-controls to determine which version is compatible with other requirements. This could take a while. 883: ERROR: Cannot install None and gpt_computer_agent because these package versions have conflicting dependencies. 884: The conflict is caused by: 885: gpt-computer-agent 0.22.4 depends on jinja2==3.1.4 886: litellm 1.40.8 depends on jinja2<4.0.0 and >=3.1.2 887: pywifi-controls 0.7 depends on Jinja2==3.1.2; platform_system == "Windows" 888: To fix this you could try to: 889: 1. loosen the range of package versions you've specified 890: 2. remove package versions to allow pip to attempt to solve the dependency conflict 891: ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts ... 1343: Collecting soupsieve>1.2 (from beautifulsoup4==4.12.3->gpt_computer_agent==0.22.4) 1344: Using cached soupsieve-2.6-py3-none-any.whl.metadata (4.6 kB) 1345: Collecting curl-cffi>=0.6.2 (from duckduckgo-search==5.3.0->gpt_computer_agent==0.22.4) 1346: Using cached curl_cffi-0.7.4-cp38-abi3-win_amd64.whl.metadata (12 kB) 1347: Collecting orjson>=3.10.0 (from duckduckgo-search==5.3.0->gpt_computer_agent==0.22.4) 1348: Using cached orjson-3.10.12-cp311-none-win_amd64.whl.metadata (42 kB) 1349: Requirement already satisfied: setuptools in c:\hostedtoolcache\windows\python\3.11.9\x64\lib\site-packages (from open-interpreter==0.2.6->gpt_computer_agent==0.22.4) (65.5.0) 1350: INFO: pip is looking at multiple versions of pywifi-controls to determine which version is compatible with other requirements. This could take a while. 1351: ERROR: Cannot install None and gpt_computer_agent because these package versions have conflicting dependencies. 1352: The conflict is caused by: 1353: gpt-computer-agent 0.22.4 depends on jinja2==3.1.4 1354: litellm 1.40.8 depends on jinja2<4.0.0 and >=3.1.2 1355: pywifi-controls 0.7 depends on Jinja2==3.1.2; platform_system == "Windows" 1356: To fix this you could try to: 1357: 1. loosen the range of package versions you've specified 1358: 2. remove package versions to allow pip to attempt to solve the dependency conflict 1359: ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 1360: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.