chore(deps): update tunit to 1.57.0 - #6322
Conversation
There was a problem hiding this comment.
Code Review: chore(deps): update tunit to 1.57.0
Summary: Automated Renovate PR bumping all TUnit-family packages from 1.56.35 → 1.57.0 in Directory.Packages.props.
What's Changed
All 6 modified lines are version bumps in the centralized Directory.Packages.props file (Central Package Management):
TUnit1.56.35 → 1.57.0TUnit.Assertions1.56.35 → 1.57.0TUnit.Assertions.FSharp1.56.35 → 1.57.0TUnit.AspNetCore1.56.35 → 1.57.0TUnit.Core1.56.35 → 1.57.0TUnit.Engine1.56.35 → 1.57.0
Assessment
Correctness: All six packages are bumped together to the same version, which is the right approach — these are sibling packages released in lockstep and version mismatches between them would cause runtime errors.
Version 1.57.0 includes: (from release notes)
- : consolidated per-file ModuleInitializers into a merged — a meaningful perf improvement for large test projects.
- : resolved ambiguity on .NET 8 SDK — a genuine correctness fix.
- : generated mocks for qualified-name calls.
All fixes in 1.57.0 are changes this repository itself authored and merged, so there is no forward-compatibility risk.
No Issues Found
The change is minimal, correctly scoped, and all packages are kept in sync. Safe to merge.
There was a problem hiding this comment.
Code Review: chore(deps): update tunit to 1.57.0
Summary: Automated Renovate PR bumping all TUnit-family packages from 1.56.35 → 1.57.0 in Directory.Packages.props.
What's Changed
All 6 modified lines are version bumps in the centralized Directory.Packages.props file (Central Package Management):
TUnit1.56.35 → 1.57.0TUnit.Assertions1.56.35 → 1.57.0TUnit.Assertions.FSharp1.56.35 → 1.57.0TUnit.AspNetCore1.56.35 → 1.57.0TUnit.Core1.56.35 → 1.57.0TUnit.Engine1.56.35 → 1.57.0
Assessment
Correctness: All six packages are bumped together to the same version, which is correct — these are sibling packages released in lockstep, and version mismatches between them would cause runtime errors.
Version 1.57.0 includes (from release notes):
- Perf improvement: consolidated per-file ModuleInitializers into a merged
.cctor— meaningful for large test projects. - Fix: resolved
CS0121IsEqualToambiguity on .NET 8 SDK. - Fix: generated mocks for qualified-name
X.Mock()calls.
All fixes in 1.57.0 are changes this repository itself authored and merged, so there is no forward-compatibility risk.
No Issues Found
The change is minimal, correctly scoped, and all packages are kept in sync. 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 reviewerTIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Code Review
This is a Renovate-generated dependency update bumping all six TUnit self-referencing packages from 1.56.35 to 1.57.0 in Directory.Packages.props.
What the change does: Updates the versions used when dog-fooding TUnit against itself — a single-file, 6-line version bump with no logic changes.
Observations:
- All six packages are bumped consistently to the same version, which is correct — mixing versions across the TUnit family (Core/Engine/Assertions/AspNetCore) in the same consuming project would risk subtle incompatibilities.
- The 1.57.0 release includes meaningful upstream improvements (source-gen
.cctorconsolidation for perf, CS0121 ambiguity fix on .NET 8, qualified-name mock support), so the update is worth taking. - Automerge is enabled, which is appropriate for this class of routine self-update.
- No issues found — this is a clean, mechanical update.
Verdict: LGTM. Nothing to change here.
There was a problem hiding this comment.
Code Review
This is a Renovate-generated dependency update bumping all six TUnit self-referencing packages from 1.56.35 to 1.57.0 in Directory.Packages.props.
What the change does: Updates the versions used when dog-fooding TUnit against itself — a single-file, 6-line version bump with no logic changes.
Observations:
- All six packages are bumped consistently to the same version, which is correct — mixing versions across the TUnit family (Core/Engine/Assertions/AspNetCore) in the same consuming project would risk subtle incompatibilities.
- The 1.57.0 release includes meaningful upstream improvements (source-gen .cctor consolidation for perf, CS0121 ambiguity fix on .NET 8, qualified-name mock support), so the update is worth taking.
- Automerge is enabled, which is appropriate for this class of routine self-update.
- No issues found — this is a clean, mechanical update.
Verdict: LGTM. Nothing to change here.
This PR contains the following updates:
1.56.35→1.57.01.56.35→1.57.01.56.35→1.57.01.56.35→1.57.01.56.35→1.57.01.56.35→1.57.0Release Notes
thomhurst/TUnit (TUnit)
v1.57.0: 1.57.0What's Changed
Other Changes
Dependencies
Full Changelog: v1.56.35...v1.57.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.