search

AdamOswald / tes

2 stars 1 forks source link

Update actions/setup-dotnet action to v3 #72

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
actions/setup-dotnet action major v2.1.1 -> v3.0.3
actions/setup-dotnet action major v2 -> v3

Release Notes

actions/setup-dotnet ### [`v3.0.3`](https://togithub.com/actions/setup-dotnet/releases/tag/v3.0.3): Fix issue with ECONNRESET and refactor authutil [Compare Source](https://togithub.com/actions/setup-dotnet/compare/v3.0.2...v3.0.3) In scope of this release we updated the link to the .Net Core releases index file ([#​337](https://togithub.com/actions/setup-dotnet/pull/337)) in order to fix the [ECONNRESET error](https://togithub.com/actions/setup-dotnet/issues/333). Besides, we refactored authutil.ts to get rid of xmlbuilder ([https://github.com/actions/setup-dotnet/pull/336](https://togithub.com/actions/setup-dotnet/pull/336)) ### [`v3.0.2`](https://togithub.com/actions/setup-dotnet/releases/tag/v3.0.2): Updating @​action/core, adding logic for processing the DOTNET_INSTALL_DIR environment variable. [Compare Source](https://togithub.com/actions/setup-dotnet/compare/v3.0.1...v3.0.2) In the scope of this release such changes were made: 1. The logic for processing the `DOTNET_INSTALL_DIR` environment variable was added to support relative paths and paths containing `~` [#​332](https://togithub.com/actions/setup-dotnet/pull/332) 2. The version of `@actions/core` was bumped to 1.10.0 [#​331](https://togithub.com/actions/setup-dotnet/pull/331) ### [`v3.0.1`](https://togithub.com/actions/setup-dotnet/releases/tag/v3.0.1): Enable DOTNET_INSTALL_DIR environment variable [Compare Source](https://togithub.com/actions/setup-dotnet/compare/v3.0.0...v3.0.1) In scope of this release the `DOTNET_INSTALL_DIR` environment variable was enabled to add the ability to change the installation directory for .NET SDK [#​329](https://togithub.com/actions/setup-dotnet/pull/329). The `DOTNET_INSTALL_DIR` can be helpful when access to the default installation directory, for instance, on self-hosted runners, is denied. Example of usage: ```yml build: runs-on: self-hosted env: DOTNET_INSTALL_DIR: "path/to/directory" steps: - uses: actions/setup-dotnet@v3 with: dotnet-version: '3.1.x' ``` ### [`v3.0.0`](https://togithub.com/actions/setup-dotnet/releases/tag/v3.0.0) [Compare Source](https://togithub.com/actions/setup-dotnet/compare/v2.1.1...v3.0.0) This major release includes the following **changes:** - [#​219](https://togithub.com/actions/setup-dotnet/issues/219) New input `dotnet-quality` was added in [#​315](https://togithub.com/actions/setup-dotnet/pull/315): ```yaml - uses: actions/setup-dotnet@v3 with: dotnet-version: '6.0.x' dotnet-quality: 'preview' - run: dotnet build ``` More in detail [here](https://togithub.com/actions/setup-dotnet#using-the-dotnet-quality-input). - [#​241](https://togithub.com/actions/setup-dotnet/issues/241) The output variable `dotnet-version` which contains the installed by the action SDK version was added in [#​324](https://togithub.com/actions/setup-dotnet/pull/324): ```yaml - uses: actions/setup-dotnet@v3 id: cp310 with: dotnet-version: '3.1.422' - run: echo '${{ steps.cp310.outputs.dotnet-version }}' # outputs 3.1.422 ``` More in detail [here](https://togithub.com/actions/setup-dotnet/tree/main#dotnet-version). - The `dotnet-version` syntax was updated and now it allows to specify the prerelease version without using `include-prerelease` input. The `include-prerelease` input was cut out: ```yaml - uses: actions/setup-dotnet@v3 with: dotnet-version: '5.0.0-preview.6' ``` More in detail [here](https://togithub.com/actions/setup-dotnet#supported-version-syntax). - [#​251](https://togithub.com/actions/setup-dotnet/issues/251) The problem with out of support .NET version warnings was solved in [#​315](https://togithub.com/actions/setup-dotnet/pull/315). **Breaking changes**: - Installation paths for Windows and Ubuntu images were changed to match the location of pre-installed SDKs. In more detail, read [here](https://togithub.com/actions/setup-dotnet/blob/main/docs/adrs/v3-setup-dotnet.md#breaking-changes).

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 these updates again.

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

performance-testing-bot[bot] commented 1 year ago

Unable to locate .performanceTestingBot config file

viezly[bot] commented 1 year ago

Pull request by bot. No need to analyze

pull-request-quantifier-deprecated[bot] commented 1 year ago

This PR has 6 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 : +3 -3 Percentile : 2.4% Total files changed: 3 Change summary by file extension: .yml : +3 -3 ``` > 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] commented 1 year ago

View changes in DiffLens

guide-bot[bot] commented 1 year ago

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.