Update actions/setup-python action

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-python	action	minor	v4.3.0 -> v4.5.0
actions/setup-python	action	major	v3 -> v4
actions/setup-python	action	major	v1 -> v4
actions/setup-python	action	major	v2 -> v4

---

Release Notes

actions/setup-python

### [`v4.5.0`](https://togithub.com/actions/setup-python/releases/tag/v4.5.0): Fix cache issue for Poetry projects located in subfolders [Compare Source](https://togithub.com/actions/setup-python/compare/v4.4.0...v4.5.0) In scope of this release we fixed cache issue for Poetry projects located in subfolders ([https://github.com/actions/setup-python/issues/446](https://togithub.com/actions/setup-python/issues/446)). Besides that we updated json5 version from 2.2.0 to 2.2.3 ([https://github.com/actions/setup-python/pull/579](https://togithub.com/actions/setup-python/pull/579)). ### [`v4.4.0`](https://togithub.com/actions/setup-python/releases/tag/v4.4.0): Add support to install multiple python versions [Compare Source](https://togithub.com/actions/setup-python/compare/v4.3.1...v4.4.0) In scope of this release we added support to [install multiple python versions](https://togithub.com/actions/setup-python/pull/567). For this you can try to use this snippet: ```yaml - uses: actions/setup-python@v4 with: python-version: | 3.8 3.9 3.10 ``` Besides, we changed logic with throwing the error for GHES if cache is unavailable to warn ([https://github.com/actions/setup-python/pull/566](https://togithub.com/actions/setup-python/pull/566)). ### [`v4.3.1`](https://togithub.com/actions/setup-python/releases/tag/v4.3.1): Improve error handling and messages [Compare Source](https://togithub.com/actions/setup-python/compare/v4.3.0...v4.3.1) In scope of this release we added improved error message to put operating system and its version in the logs ([https://github.com/actions/setup-python/pull/559](https://togithub.com/actions/setup-python/pull/559)). Besides, the release - fixes issue about [specifying architecture for pypy-nightly on Windows](https://togithub.com/actions/setup-python/issues/518) with related [pull request](https://togithub.com/actions/setup-python/pull/520). - improves error handling for Http Errors ([https://github.com/actions/setup-python/pull/511](https://togithub.com/actions/setup-python/pull/511)). - updates minimatch ([https://github.com/actions/setup-python/pull/558](https://togithub.com/actions/setup-python/pull/558)).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[performance-testing-bot[bot]]

Unable to locate .performanceTestingBot config file

[viezly[bot]]

Pull request by bot. No need to analyze

[pull-request-quantifier-deprecated[bot]]

This PR has 20 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Extra Small Size : +10 -10 Percentile : 8% Total files changed: 10 Change summary by file extension: .yml : +10 -10 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[guide-bot[bot]]

Thanks for opening this Pull Request! We need you to:

1. Fill out the description.

   Action: Edit description and replace <!- ... --> with actual values.

2. Complete the activities.

   Action: Complete If you want to rebase/retry this PR, check this box

   If an activity is not applicable, use '\~activity description\~' to mark it not applicable.

[difflens[bot]]

View changes in DiffLens