8000 chore: Configure Renovate by renovate[bot] · Pull Request #43 · AwesomeAssertions/AwesomeAssertions · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: Configure Renovate #43

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Mar 2, 2025
Merged

chore: Configure Renovate #43

merged 2 commits into from
Mar 2, 2025

Conversation

renovate[bot]
Copy link
Contributor
@renovate renovate bot commented Feb 26, 2025 •
edited
Loading

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

  • docs/Gemfile (bundler)
  • .github/workflows/build.yml (github-actions)
  • .github/workflows/codeql.yml (github-actions)
  • docs/package.json (npm)
  • package.json (npm)
  • Directory.Build.props (nuget)
  • Src/FluentAssertions/FluentAssertions.csproj (nuget)
  • Tests/Approval.Tests/Approval.Tests.csproj (nuget)
  • Tests/Benchmarks/Benchmarks.csproj (nuget)
  • Tests/FSharp.Specs/FSharp.Specs.fsproj (nuget)
  • Tests/FluentAssertions.Equivalency.Specs/FluentAssertions.Equivalency.Specs.csproj (nuget)
  • Tests/FluentAssertions.Extensibility.Specs/FluentAssertions.Extensibility.Specs.csproj (nuget)
  • Tests/FluentAssertions.Specs/FluentAssertions.Specs.csproj (nuget)
  • Tests/TestFrameworks/MSTestV2.Specs/MSTestV2.Specs.csproj (nuget)
  • Tests/TestFrameworks/MSpec.Specs/MSpec.Specs.csproj (nuget)
  • Tests/TestFrameworks/NUnit3.Specs/NUnit3.Specs.csproj (nuget)
  • Tests/TestFrameworks/NUnit4.Specs/NUnit4.Specs.csproj (nuget)
  • Tests/TestFrameworks/TUnit.Specs/TUnit.Specs.csproj (nuget)
  • Tests/TestFrameworks/XUnit2.Specs/XUnit2.Specs.csproj (nuget)
  • Tests/TestFrameworks/XUnit3.Specs/XUnit3.Specs.csproj (nuget)
  • Tests/TestFrameworks/XUnit3Core.Specs/XUnit3Core.Specs.csproj (nuget)
  • Tests/UWP.Specs/UWP.Specs.csproj (nuget)
  • Tests/VB.Specs/VB.Specs.vbproj (nuget)
  • global.json (nuget)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

What to Expect

With your current configuration, Renovate will create 19 Pull Requests:

chore(deps): replace dependency npm-run-all with npm-run-all2 ^5.0.0
  • Schedule: ["at any time"]
  • Branch name: renovate/npm-run-all-replacement
  • Merge into: main
  • Upgrade npm-run-all to ^5.0.0
chore(deps): update dependency bogus to 35.6.2
  • Schedule: ["at any time"]
  • Branch name: renovate/bogus-35.x
  • Merge into: main
  • Upgrade Bogus to 35.6.2
chore(deps): update dependency coverlet.collector to 6.0.4
  • Schedule: ["at any time"]
  • Branch name: renovate/coverlet.collector-6.x
  • Merge into: main
  • Upgrade coverlet.collector to 6.0.4
chore(deps): update dependency meziantou.analyzer to 2.0.188
  • Schedule: ["at any time"]
  • Branch name: renovate/meziantou.analyzer-2.x
  • Merge into: main
  • Upgrade Meziantou.Analyzer to 2.0.188
chore(deps): update xunit-dotnet monorepo
fix(deps): update dependency cspell to v8.17.5
  • Schedule: ["at any time"]
  • Branch name: renovate/cspell-monorepo
  • Merge into: main
  • Upgrade cspell to 8.17.5
chore(deps): update dependency microsoft.net.test.sdk to 17.13.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vstest-monorepo
  • Merge into: main
  • Upgrade Microsoft.NET.Test.Sdk to 17.13.0
chore(deps): update dependency microsoft.testing.extensions.codecoverage to 17.14.1
chore(deps): update dependency publicapigenerator to 11.4.2
  • Schedule: ["at any time"]
  • Branch name: renovate/publicapigenerator-11.x
  • Merge into: main
  • Upgrade PublicApiGenerator to 11.4.2
chore(deps): update dependency reflectify to 1.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/reflectify-1.x
  • Merge into: main
  • Upgrade Reflectify to 1.5.0
chore(deps): update dependency roslynator.analyzers to 4.13.1
  • Schedule: ["at any time"]
  • Branch name: renovate/roslynator.analyzers-4.x
  • Merge into: main
  • Upgrade Roslynator.Analyzers to 4.13.1
chore(deps): update dependency system.threading.tasks.extensions to 4.6.0
chore(deps): update dependency tunit to 0.14.13
  • Schedule: ["at any time"]
  • Branch name: renovate/tunit-0.x
  • Merge into: main
  • Upgrade TUnit to 0.14.13
chore(deps): update dependency verify.xunit to 28.13.0
  • Schedule: ["at any time"]
  • Branch name: renovate/verify.xunit-28.x
  • Merge into: main
  • Upgrade Verify.Xunit to 28.13.0
chore(deps): update dependency xunit.stafact to 1.2.69
  • Schedule: ["at any time"]
  • Branch name: renovate/xunit.stafact-1.x
  • Merge into: main
  • Upgrade Xunit.StaFact to 1.2.69
chore(deps): update mstest monorepo
chore(deps): update dependency nunit3testadapter to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/nunit3testadapter-5.x
  • Merge into: main
  • Upgrade NUnit3TestAdapter to 5.0.0
chore(deps): update dependency onchange to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/onchange-7.x
  • Merge into: main
  • Upgrade onchange to ^7.0.0
chore(deps): update dependency xunit.runner.visualstudio to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/major-xunit-dotnet-monorepo
  • Merge into: main
  • Upgrade xunit.runner.visualstudio to 3.0.2

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

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

@meenzen meenzen mentioned this pull request Feb 26, 2025
Closed
28 tasks
@github-actions GitHub Actions
Copy link
github-actions bot commented Feb 26, 2025 •
edited
Loading

Test Results

    36 files  ±0      36 suites  ±0   2m 26s ⏱️ +8s
 6 108 tests ±0   6 108 ✅ ±0  0 💤 ±0  0 ❌ ±0 
37 999 runs  ±0  37 999 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 76a23e9. ± Comparison against base commit 166f679.

This pull request removes 10 and adds 8 tests. Note that renamed tests count towards both. 
FluentAssertions.Specs.Streams.StreamAssertionSpecs+HaveLength ‑ When_a_throwing_stream_should_have_a_length_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
FluentAssertions.Specs.Streams.StreamAssertionSpecs+HaveLength ‑ When_a_throwing_stream_should_have_a_length_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
FluentAssertions.Specs.Streams.StreamAssertionSpecs+HavePosition ‑ When_a_throwing_stream_should_have_a_position_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
FluentAssertions.Specs.Streams.StreamAssertionSpecs+HavePosition ‑ When_a_throwing_stream_should_have_a_position_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
FluentAssertions.Specs.Streams.StreamAssertionSpecs+NotHaveLength ‑ When_a_throwing_stream_should_not_have_a_length_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
FluentAssertions.Specs.Streams.StreamAssertionSpecs+NotHaveLength ‑ When_a_throwing_stream_should_not_have_a_length_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
FluentAssertions.Specs.Streams.StreamAssertionSpecs+NotHavePosition ‑ When_a_throwing_stream_should_not_have_a_position_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
FluentAssertions.Specs.Streams.StreamAssertionSpecs+NotHavePosition ‑ When_a_throwing_stream_should_not_have_a_position_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetLengthExceptionMessage'.)
Object name: 'GetPositionExceptionMessage'.)

FluentAssertions.Specs.Streams.StreamAssertionSpecs+HaveLength ‑ When_a_throwing_stream_should_have_a_length_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetLengthExceptionMessage'.)
FluentAssertions.Specs.Streams.StreamAssertionSpecs+HaveLength ‑ When_a_throwing_stream_should_have_a_length_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetLengthExceptionMessage'.)
FluentAssertions.Specs.Streams.StreamAssertionSpecs+HavePosition ‑ When_a_throwing_stream_should_have_a_position_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetPositionExceptionMessage'.)
FluentAssertions.Specs.Streams.StreamAssertionSpecs+HavePosition ‑ When_a_throwing_stream_should_have_a_position_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetPositionExceptionMessage'.)
FluentAssertions.Specs.Streams.StreamAssertionSpecs+NotHaveLength ‑ When_a_throwing_stream_should_not_have_a_length_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetLengthExceptionMessage'.)
FluentAssertions.Specs.Streams.StreamAssertionSpecs+NotHaveLength ‑ When_a_throwing_stream_should_not_have_a_length_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetLengthExceptionMessage'.)
FluentAssertions.Specs.Streams.StreamAssertionSpecs+NotHavePosition ‑ When_a_throwing_stream_should_not_have_a_position_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetPositionExceptionMessage'.)
FluentAssertions.Specs.Streams.StreamAssertionSpecs+NotHavePosition ‑ When_a_throwing_stream_should_not_have_a_position_it_should_fail(exception: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetPositionExceptionMessage'.)

♻️ This comment has been updated with latest results.

@coveralls
Copy link
coveralls commented Feb 26, 2025 •
edited
Loading

Pull Request Test Coverage Report for Build 13543461622

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 97.403%
Totals Coverage Status
Change from base Build 13476589386: 0.0%
Covered Lines: 12286
Relevant Lines: 12470
💛 - Coveralls

@meenzen
Copy link
Collaborator
meenzen commented Feb 26, 2025

Dang, that's a lot of updates.

@cbersch
Copy link
Contributor
cbersch commented Feb 26, 2025

I wouldn't upgrade to .net9:

chore(deps): update dotnet monorepo to v9 (major)

Schedule: ["at any time"]
Branch name: renovate/major-dotnet-monorepo
Merge into: main
Upgrade System.Collections.Immutable to 9.0.2
Upgrade dotnet-sdk to 9.0.200

@ScarletKuro
Copy link
Contributor

Would probably exclude the nuke Build/ as well

@sonarqubecloud SonarQubeCloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@ScarletKuro ScarletKuro requested a review from a team February 27, 2025 09:12
@IT-VBFK
Copy link
Contributor
IT-VBFK commented Feb 27, 2025 •
edited
Loading

Why exactly do we exclude the build project? Since Renovate ignores PackageDownloads ATM, the only thing what's receiving updates ist NUKE itself and a few minor deps, but why we don't want to?

@ScarletKuro
Copy link
Contributor

Why exactly do we exclude the build project? Since Renovate ignores PackageDownloads ATM, the only thing what's receiving updates ist NUKE itself and a few minor deps, but why we don't want to?

At work, I always update Nuke manually because often there are breaking changes in new major versions. Also, they weren't even ready for the .NET 9 release beforehand because they were still using Binary Serialization, which they didn't address for about two weeks (IIRC).

@IT-VBFK
Copy link
Contributor
IT-VBFK commented Feb 27, 2025

Clear now :)

@ITaluone
Copy link
Contributor

At work, I always update Nuke manually because often there are breaking changes in new major versions. Also, they weren't even ready for the .NET 9 release beforehand because they were still using Binary Serialization, which they didn't address for about two weeks (IIRC).

On the other hand... it's "just" the build project, and Renovate won't merge a PR when the check failed...

@meenzen
Copy link
Collaborator
meenzen commented Mar 2, 2025

We can always adjust these settings if required. Merging for now.

@meenzen meenzen merged commit 00814e2 into main Mar 2, 2025
12 checks passed
@ScarletKuro ScarletKuro deleted the renovate/configure branch March 2, 2025 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@cbersch cbersch cbersch approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@coveralls @meenzen @cbersch @ScarletKuro @IT-VBFK @ITaluone
0