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

chore(deps): update all dependencies #26

Merged
merged 1 commit into from
Aug 7, 2024
Merged

chore(deps): update all dependencies #26

merged 1 commit into from
Aug 7, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
BenchmarkDotNet 0.13.12 -> 0.14.0 age adoption passing confidence
Meziantou.Analyzer 2.0.162 -> 2.0.163 age adoption passing confidence
Swashbuckle.AspNetCore 6.6.2 -> 6.7.0 age adoption passing confidence
mu88.Shared 0.2.2 -> 0.5.0 age adoption passing confidence

Release Notes

dotnet/BenchmarkDotNet (BenchmarkDotNet)

v0.14.0: 0.14.0

Full changelog: https://benchmarkdotnet.org/changelog/v0.14.0.html

Highlights

  • Introduce BenchmarkDotNet.Diagnostics.dotMemory #​2549: memory allocation profile of your benchmarks using dotMemory, see @​BenchmarkDotNet.Samples.IntroDotMemoryDiagnoser
  • Introduce BenchmarkDotNet.Exporters.Plotting #​2560: plotting via ScottPlot (initial version)
  • Multiple bugfixes
  • The default build toolchains have been updated to pass IntermediateOutputPath, OutputPath, and OutDir properties to the dotnet build command. This change forces all build outputs to be placed in a new directory generated by BenchmarkDotNet, and fixes many issues that have been reported with builds. You can also access these paths in your own .csproj and .props from those properties if you need to copy custom files to the output.

Bug fixes

  • Fixed multiple build-related bugs including passing MsBuildArguments and .Net 8's UseArtifactsOutput.

Breaking Changes

  • DotNetCliBuilder removed retryFailedBuildWithNoDeps constructor option.
  • DotNetCliCommand removed RetryFailedBuildWithNoDeps property and BuildNoRestoreNoDependencies() and PublishNoBuildAndNoRestore() methods (replaced with PublishNoRestore()).
meziantou/Meziantou.Analyzer (Meziantou.Analyzer)

v2.0.163

Compare Source

NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/2.0.163

Full Changelog: meziantou/Meziantou.Analyzer@2.0.162...2.0.163

domaindrivendev/Swashbuckle.AspNetCore (Swashbuckle.AspNetCore)

v6.7.0

What's Changed
New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v6.6.2...v6.7.0

mu88/mu88.Shared (mu88.Shared)

v0.5.0

Features

v0.4.0

Features
  • log warning if OpenTelemetry endpoint is not set (2c4d63a)
Bug Fixes
  • map .NET RIDs to Golang architecture items on full strings (f435745)

v0.3.0

Features
  • map .NET RIDs to Golang architecture items (fa69789)

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Aug 5, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 3650240 to 2a3b0f0 Compare August 6, 2024 18:07
@mu88 mu88 merged commit 8918880 into main Aug 7, 2024
2 checks passed
@renovate renovate bot deleted the renovate/all branch August 7, 2024 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant