Update actions/setup-dotnet action to v3.2.0

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-dotnet	action	minor	v3.0.3 -> v3.2.0

---

Release Notes

actions/setup-dotnet (actions/setup-dotnet)

### [`v3.2.0`](https://togithub.com/actions/setup-dotnet/releases/tag/v3.2.0) [Compare Source](https://togithub.com/actions/setup-dotnet/compare/v3.1.0...v3.2.0) #### What's Changed In scope of this minor release, the ability to cache the NuGet `global-packages` folder was added in [https://github.com/actions/setup-dotnet/pull/303](https://togithub.com/actions/setup-dotnet/pull/303) by [@​nogic1008](https://togithub.com/nogic1008) For caching, the action uses the [@​toolkit/cache](https://togithub.com/actions/toolkit/tree/main/packages/cache) library under the hood, which in turn allows getting rid of configuring the [@​actions/cache](https://togithub.com/actions/cache) action separately. Such input parameters as `cache` and `cache-dependency-path` were added. The `cache` input is optional, and caching is turned off by default, `cache-dependency-path` is used to specify the path to a dependency file - `packages.lock.json`. **Example of use-case:** ```yaml - uses: actions/setup-dotnet@v3   with:     dotnet-version: 6.x     cache: true     cache-dependency-path: subdir/packages.lock.json ``` More details can be found in the [action's documentation](https://togithub.com/actions/setup-dotnet#caching-nuget-packages). **Full Changelog**: https://github.com/actions/setup-dotnet/compare/v3...v3.2.0 ### [`v3.1.0`](https://togithub.com/actions/setup-dotnet/releases/tag/v3.1.0) [Compare Source](https://togithub.com/actions/setup-dotnet/compare/v3.0.3...v3.1.0) #### What's Changed This minor release includes the following new **features**: - The latest patch syntax was added in [https://github.com/actions/setup-dotnet/pull/428](https://togithub.com/actions/setup-dotnet/pull/428) by [@​IvanZosimov](https://togithub.com/IvanZosimov) ```yml - uses: actions/setup-dotnet@v3 with: dotnet-version: '7.0.2xx' ``` More details about the new syntax can be found [here](https://togithub.com/actions/setup-dotnet#supported-version-syntax). - The `global-json-file` input was updated to accept absolute paths in [https://github.com/actions/setup-dotnet/pull/396](https://togithub.com/actions/setup-dotnet/pull/396) by [@​othmane-kinane-nw](https://togithub.com/othmane-kinane-nw) - Error messages were made more informative in [https://github.com/actions/setup-dotnet/pull/375](https://togithub.com/actions/setup-dotnet/pull/375) by [@​IvanZosimov](https://togithub.com/IvanZosimov) - Notification if the `global.json` was not found in the root directory was added in [https://github.com/actions/setup-dotnet/pull/344](https://togithub.com/actions/setup-dotnet/pull/344) by [@​teo-tsirpanis](https://togithub.com/teo-tsirpanis) It also contains several **infrastructure changes**: - Update to latest `actions/publish-action` by [@​JamesMGreene](https://togithub.com/JamesMGreene) in [https://github.com/actions/setup-dotnet/pull/348](https://togithub.com/actions/setup-dotnet/pull/348) - Update version of publish-action by [@​MaksimZhukov](https://togithub.com/MaksimZhukov) in [https://github.com/actions/setup-dotnet/pull/368](https://togithub.com/actions/setup-dotnet/pull/368) - Update action to use reusable workflows by [@​IvanZosimov](https://togithub.com/IvanZosimov) in [https://github.com/actions/setup-dotnet/pull/358](https://togithub.com/actions/setup-dotnet/pull/358) - Update workflow badges by [@​IvanZosimov](https://togithub.com/IvanZosimov) in [https://github.com/actions/setup-dotnet/pull/377](https://togithub.com/actions/setup-dotnet/pull/377) - Add and configure ESLint and update configuration for Prettier by [@​IvanZosimov](https://togithub.com/IvanZosimov) in [https://github.com/actions/setup-dotnet/pull/391](https://togithub.com/actions/setup-dotnet/pull/391) - Turn on automatic update of ESLint and Prettier configuration files by [@​IvanZosimov](https://togithub.com/IvanZosimov) in [https://github.com/actions/setup-dotnet/pull/395](https://togithub.com/actions/setup-dotnet/pull/395) - Update e2e tests and e2e test infrastructure by [@​IvanZosimov](https://togithub.com/IvanZosimov) in [https://github.com/actions/setup-dotnet/pull/414](https://togithub.com/actions/setup-dotnet/pull/414) - Refactor and update unit-tests by [@​IvanZosimov](https://togithub.com/IvanZosimov) in [https://github.com/actions/setup-dotnet/pull/418](https://togithub.com/actions/setup-dotnet/pull/418) - Increase amount of retries for Dotnet installation scripts tests by [@​nikolai-laevskii](https://togithub.com/nikolai-laevskii) in [https://github.com/actions/setup-dotnet/pull/427](https://togithub.com/actions/setup-dotnet/pull/427) #### New Contributors - [@​teo-tsirpanis](https://togithub.com/teo-tsirpanis) made their first contribution in [https://github.com/actions/setup-dotnet/pull/344](https://togithub.com/actions/setup-dotnet/pull/344) - [@​JamesMGreene](https://togithub.com/JamesMGreene) made their first contribution in [https://github.com/actions/setup-dotnet/pull/348](https://togithub.com/actions/setup-dotnet/pull/348) - [@​othmane-kinane-nw](https://togithub.com/othmane-kinane-nw) made their first contribution in [https://github.com/actions/setup-dotnet/pull/396](https://togithub.com/actions/setup-dotnet/pull/396) - [@​nikolai-laevskii](https://togithub.com/nikolai-laevskii) made their first contribution in [https://github.com/actions/setup-dotnet/pull/427](https://togithub.com/actions/setup-dotnet/pull/427) **Full Changelog**: https://github.com/actions/setup-dotnet/compare/v3...v3.1.0

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[viezly[bot]]

Pull request by bot. No need to analyze

[senior-dev-bot[bot]]

Hi there! :wave: Thanks for opening a PR. :tada: To get the most out of Senior Dev, please uninstall the app from your organization, then re-install it into your organization. You can uninstall the app here :rocket:

[performance-testing-bot[bot]]

Unable to locate .performanceTestingBot config file

[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

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

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

This PR has 2 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 : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .yml : +1 -1 ``` > 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.

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[aviator-app[bot]]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes. Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[difflens[bot]]

View changes in DiffLens