Skip to content

chore(deps): update tunit to 1.53.0 - #6199

Merged
thomhurst merged 1 commit into
mainfrom
renovate/tunit
Jun 9, 2026
Merged

chore(deps): update tunit to 1.53.0#6199
thomhurst merged 1 commit into
mainfrom
renovate/tunit

Conversation

@thomhurst

Copy link
Copy Markdown
Owner

This PR contains the following updates:

PackageTypeUpdateChange
TUnitnugetminor1.51.01.53.0
TUnit.AspNetCorenugetminor1.51.01.53.0
TUnit.Assertionsnugetminor1.51.01.53.0
TUnit.Assertions.FSharpnugetminor1.51.01.53.0
TUnit.Corenugetminor1.51.01.53.0
TUnit.Enginenugetminor1.51.01.53.0

Release Notes

thomhurst/TUnit (TUnit)

v1.53.0: 1.53.0

What's Changed
Other Changes
Dependencies

Full Changelog: v1.51.0...v1.53.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@thomhurstthomhurst added dependencies Pull requests that update a dependency file MINOR renovate-bot labels Jun 9, 2026
@thomhurst
thomhurst enabled auto-merge (squash) June 9, 2026 00:56

@claudeclaudeBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a clean, mechanical Renovate-generated dependency bump with no architectural concerns.

Summary of changes: All 6 TUnit-family packages (TUnit, TUnit.Core, TUnit.Engine, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.AspNetCore) are bumped in lockstep from 1.51.0 to 1.53.0 in Directory.Packages.props. That's the correct approach — keeping the whole TUnit family on a single uniform version avoids subtle API/ABI mismatches between components.

One minor observation — package ordering: The TUnit entries in Directory.Packages.props are not alphabetically sorted with the rest of the file. TUnit.Assertions.FSharp appears before the Verify.* block, while the remaining five TUnit packages appear after it. This is a pre-existing issue (not introduced here), but it could cause a small readability/merge-conflict risk over time. Worth considering a one-off sort of the file.

No blocking issues — the change is correct, minimal, and the auto-merge setup is appropriate for this kind of routine maintenance.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics0 complexity

MetricResults
Complexity0

View in Codacy

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.

@thomhurst
thomhurst merged commit 2a42df7 into mainJun 9, 2026
13 of 14 checks passed
@thomhurst
thomhurst deleted the renovate/tunit branch June 9, 2026 01:18
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesPull requests that update a dependency fileMINORrenovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@thomhurst@renovate-bot