Conversation
There was a problem hiding this comment.
Code Review
This is a Renovate bot PR bumping the TUnit family of NuGet packages from → in Directory.Packages.props.
Summary
All 6 TUnit packages are consistently updated together:
TUnitTUnit.AspNetCoreTUnit.AssertionsTUnit.Assertions.FSharpTUnit.CoreTUnit.Engine
Observations
Self-referential upgrade — This project uses TUnit to test itself, so it is updating its own external package references to a newer version. This is expected and correct; the Directory.Packages.props entries reference the published NuGet packages consumed by downstream consumers in the test/sample projects, not the locally-built source.
Version consistency — All 6 packages move to the same version (1.41.0), which is correct. A mismatch between e.g. TUnit.Core and TUnit.Engine could cause runtime compatibility issues.
v1.41.0 highlights relevant to this repo — The release includes a fix for TestFailedException unwrapping (#5776) and item-at Satisfies source typing (#5764), both of which originated in this repo, so consuming the updated NuGet aligns the external references with already-merged improvements.
Verdict
The change is minimal, mechanical, and correct. No architectural or design concerns. Safe to merge. ✅
There was a problem hiding this comment.
Code Review
This is a Renovate bot PR bumping the TUnit family of NuGet packages from 1.40.10 to 1.41.0 in Directory.Packages.props.
Summary
All 6 TUnit packages are consistently updated together:
TUnitTUnit.AspNetCoreTUnit.AssertionsTUnit.Assertions.FSharpTUnit.CoreTUnit.Engine
Observations
Self-referential upgrade — This project uses TUnit to test itself, so it is updating its own external package references to a newer version. This is expected and correct; the Directory.Packages.props entries reference the published NuGet packages consumed by downstream consumers in the test/sample projects, not the locally-built source.
Version consistency — All 6 packages move to the same version (1.41.0), which is correct. A mismatch between e.g. TUnit.Core and TUnit.Engine could cause runtime compatibility issues.
v1.41.0 highlights relevant to this repo — The release includes a fix for TestFailedException unwrapping (#5776) and item-at Satisfies source typing (#5764), both of which originated in this repo, so consuming the updated NuGet aligns the external references with already-merged improvements.
Verdict
The change is minimal, mechanical, and correct. No architectural or design concerns. Safe to merge.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This PR contains the following updates:
1.40.10→1.41.01.40.10→1.41.01.40.10→1.41.01.40.10→1.41.01.40.10→1.41.01.40.10→1.41.0Release Notes
thomhurst/TUnit (TUnit)
v1.41.0: 1.41.0TUnit Should() Assertions (beta)
This versions comes with a beta version of TUnit.Assertions.Should - meaning that you can do:
myCode.Should().BeEqualTo(fluentShouldSyntax);For more information see the docs: https://tunit.dev/docs/assertions/should-syntax
What's Changed
Other Changes
Dependencies
Full Changelog: v1.40.10...v1.41.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.