deps: Update dependency Grynwald.SharedBuild to version 4 #558
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.0.10
->4.0.29
Release Notes
ap0llo/shared-build (Grynwald.SharedBuild)
v4.0.29
New Features
Bug Fixes
Breaking Changes
Details
Skip execution of the "ValidateCodeFormatting" task when build is running on Azure Pipelines
Running dotnet format on Azure Pipelines when using the .NET 9 SDK and Nerdbank.GitVersioning is installed causes the build to hang (see https://github.com/dotnet/sdk/issues/44951).
To work around this, skip the task when running on Azure Pipelines and emit a warning about the task being skipped
e6b1d12
Upgrade to .NET 9 and Cake 5
Breaking Change
ff033de
GitHub Actions Integration: Add GitHub Actions support
Add support to all tasks for running builds on GitHub Actions instead of Azure Pipelines.
3de7ec8
Include Cake.BuildSystems module by default
Include Cake.BuildSystems.Module in the SharedBuild package's dependencies and enable support for Azure Pipelines and GitHub Actions implicitly in UseSharedBuild().
This removes the need to explicitly install and load the modules in projects using the SharedBuild package.
718a316
Make reporting of code coverage more consistent (#152)
Adjust how code coverage reports are generated and make behavior consistent between local and CI builds
The combined coverage data (Cobertura.xml) will be placed directly in the code coverage output directory
The "Report" directory will always contain a HTML report (no longer a Azure Pipelines specific report when running on Azure Pipelines.
The HTML report as well as the Cobertura.xml is now published as pipeline artifact on both Azure Pipelines and GitHub Actions
The Azure Pipelines-specific HTML report that is shown in the web UI is now generated in a temporary directory (and only when publishing results to Azure Pipelines)
Pull Request: #152
Commit:
3ddb9b4
Fix detection of Pull Request builds on Azure Pipelines
0ed428f
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.
This PR was generated by Mend Renovate. View the repository job log.