Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update actions/setup-dotnet action to v4 #170

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 8, 2024

This PR contains the following updates:

Package Type Update Change
actions/setup-dotnet action major v3.2.0 -> v4.2.0
actions/setup-dotnet action major v3 -> v4

Release Notes

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

v4.2.0

Compare Source

v4.1.0

Compare Source

What's Changed

Bug fixes :
Dependency updates :

New Contributors

Full Changelog: actions/setup-dotnet@v4...v4.1.0

v4.0.1

Compare Source

What's Changed

Documentation changes:
Dependency updates:

New Contributors

Full Changelog: actions/setup-dotnet@v4...v4.0.1

v4.0.0

Compare Source

What's Changed

In the scope of this release, the version of the Node.js runtime was updated to 20. The majority of dependencies were updated to the latest versions. From now on, the code for the setup-dotnet will run on Node.js 20 instead of Node.js 16.

Breaking changes

  • Update Node.js runtime to version 20 by @​harithavattikuti in #​484
  • Sequential version install fix by @​nikolai-laevskii in https://github.com/actions/setup-dotnet/pull/433
    In setup-dotnet@v3, the dotnet executable was overwritten during each action run, sometimes leading to failures if the executable was still in use. This issue was resolved in setup-dotnet@v4 by introducing an additional install-script run that installs the LTS version of the dotnet executable and utilizes it for all subsequent dotnet installations. The actual download is performed only once per workflow by the initial install-script run. To use older versions, utilize global.json. For more details, refer to the documentation.

Non-breaking changes

New Contributors

Full Changelog: actions/setup-dotnet@v3...v4.0.0

v3.3.0

Compare Source

What's Changed

Some .NET binaries and installers currently hosted on Azure Content Delivery Network (CDN) domains ending in .azureedge.net will move to new domains as the provider, edg.io, will soon cease operations. There may be downtime or unavailability of .azureedge.net domains in the future as the .NET team is required to migrate to a new CDN and set of domains moving forward.

If your workflows are pinned to specific SHAs or minor tags, please upgrade to a major release tag to avoid service disruptions. Edgio has confirmed their services will be operational until at least January 15, 2025.

For updates, follow https://github.com/dotnet/core/issues/9671.

Full Changelog: actions/setup-dotnet@v3.2.0...v3.3.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 these updates again.


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

This PR was generated by Mend Renovate. View the repository job log.

Copy link

aviator-app bot commented Feb 8, 2024

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 pull request is currently open (not queued).

How to merge

To merge this PR, comment /aviator merge or add the mergequeue label.


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.

Copy link

Unable to locate .performanceTestingBot config file

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.

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
    • 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 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? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

Copy link

guide-bot bot commented Feb 8, 2024

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.

Copy link

senior-dev-bot bot commented Feb 8, 2024

Hi there! 👋 Thanks for opening a PR. It looks like you've already reached the 5 review limit on our Basic Plan for the week. If you still want a review, feel free to upgrade your subscription in the Web App and then reopen the PR

Copy link

difflens bot commented Feb 8, 2024

View changes in DiffLens

Copy link

coderabbitai bot commented Feb 8, 2024

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

@renovate renovate bot force-pushed the renovate/actions-setup-dotnet-4.x branch from 092de56 to 83fb860 Compare July 9, 2024 16:49
Copy link

difflens bot commented Jul 9, 2024

View changes in DiffLens

3 similar comments
Copy link

difflens bot commented Jul 9, 2024

View changes in DiffLens

Copy link

difflens bot commented Jul 10, 2024

View changes in DiffLens

Copy link

difflens bot commented Jul 22, 2024

View changes in DiffLens

Copy link

lang-ci bot commented Jul 22, 2024

Issues Summary

1. Git version mismatch

Logs Summary: Git version 2.47.1 is expected but found version 2.47.1.windows.1

Failing Step:

Getting git version

Related Source Files:

None

Related Failures:

MSBuild / build


2. Git configuration issue

Logs Summary: Errors related to git configuration

Failing Step:

Post job cleanup

Related Source Files:

None

Related Failures:

CMake / build

Java CI with Maven / build

NodeJS with Webpack / build (14.x)

NodeJS with Webpack / build (16.x)

NodeJS with Webpack / build (18.x)

Node.js CI / build (14.x)

Node.js CI / build (16.x)

Symfony / symfony-tests


ℹ️ Help (You can turn this bot off by adding a comment /ai off, or force a refresh of this report with /ai ...)

For more support, join our Discord channel

EDIT: Creating a new report...

EDIT: Creating a new report...

EDIT: Creating a new report...

EDIT: Creating a new report...

EDIT: Creating a new report...

EDIT: Creating a new report...

EDIT: Creating a new report...

EDIT: Creating a new report...

Copy link

difflens bot commented Aug 28, 2024

View changes in DiffLens

14 similar comments
Copy link

difflens bot commented Aug 28, 2024

View changes in DiffLens

Copy link

difflens bot commented Aug 28, 2024

View changes in DiffLens

Copy link

difflens bot commented Aug 29, 2024

View changes in DiffLens

Copy link

difflens bot commented Aug 29, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 5, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 5, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 6, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 6, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 6, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 6, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 7, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 7, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 7, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 7, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 10, 2024

View changes in DiffLens

22 similar comments
Copy link

difflens bot commented Sep 10, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 10, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 10, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 10, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 11, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 11, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 11, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 12, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 12, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 12, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 13, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 13, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 13, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 13, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 13, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 13, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 14, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 14, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 14, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 14, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 14, 2024

View changes in DiffLens

Copy link

difflens bot commented Sep 14, 2024

View changes in DiffLens

@renovate renovate bot force-pushed the renovate/actions-setup-dotnet-4.x branch from 83fb860 to ced098e Compare October 24, 2024 17:40
Copy link

difflens bot commented Oct 24, 2024

View changes in DiffLens

1 similar comment
Copy link

difflens bot commented Oct 24, 2024

View changes in DiffLens

@renovate renovate bot force-pushed the renovate/actions-setup-dotnet-4.x branch from ced098e to 1ebf888 Compare December 27, 2024 00:11
Copy link

difflens bot commented Dec 27, 2024

View changes in DiffLens

1 similar comment
Copy link

difflens bot commented Dec 27, 2024

View changes in DiffLens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants