Skip to content

chore(deps): update tunit to 1.19.16#5109

Merged
thomhurst merged 1 commit intomainfrom
renovate/tunit
Mar 9, 2026
Merged

chore(deps): update tunit to 1.19.16#5109
thomhurst merged 1 commit intomainfrom
renovate/tunit

Conversation

@thomhurst
Copy link
Owner

This PR contains the following updates:

Package Type Update Change
TUnit nuget patch 1.19.111.19.16
TUnit.AspNetCore nuget patch 1.19.111.19.16
TUnit.Assertions nuget patch 1.19.111.19.16
TUnit.Assertions.FSharp nuget patch 1.19.111.19.16
TUnit.Core nuget patch 1.19.111.19.16
TUnit.Engine nuget patch 1.19.111.19.16
TUnit.Playwright nuget patch 1.19.111.19.16

Release Notes

thomhurst/TUnit (TUnit)

v1.19.16: 1.19.16

What's Changed
Other Changes
Dependencies

Full Changelog: v1.19.11...v1.19.16


Configuration

📅 Schedule: 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 Renovate Bot.

@thomhurst thomhurst added dependencies Pull requests that update a dependency file PATCH renovate-bot labels Mar 9, 2026
@thomhurst thomhurst enabled auto-merge (squash) March 9, 2026 01:58
Copy link
Contributor

@claude claude bot left a comment

Choose a reason for hiding this comment

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

Code Review: chore(deps): update tunit to 1.19.16

This is a routine Renovate Bot PR bumping TUnit self-referential package dependencies from 1.19.11 to 1.19.16 across 6 files.

Summary

The changes are clean and correct:

  • Directory.Packages.props — centrally bumps 6 TUnit packages (TUnit, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Assertions, TUnit.Assertions.FSharp)
  • Template project files — bump pinned versions in distributed project templates

Observation Worth Noting

TUnit.Playwright is pinned directly in TUnit.Templates/content/TUnit.Playwright/TestProject.csproj but is not centrally managed in Directory.Packages.props. All other TUnit packages in the templates are centrally managed. This inconsistency is minor but could lead to Playwright template version drift if future updates miss it (though Renovate appears to handle it correctly here). Consider adding TUnit.Playwright to Directory.Packages.props for consistency — not a blocker for this PR.

Verdict

The update is straightforward, the versions are consistent across all changed files, and the patch jump (5 versions: 1.19.11 → 1.19.16) aligns with the referenced release notes. No concerns with this PR.

✅ Approved.

Copy link
Contributor

@claude claude bot left a comment

Choose a reason for hiding this comment

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

Code Review: chore(deps): update tunit to 1.19.16

This PR has been previously reviewed and approved. No new changes have been made since then.

Re-review Summary

The diff remains a straightforward, consistent version bump of all TUnit-family packages from 1.19.111.19.16 across:

  • Directory.Packages.props — 6 TUnit packages centrally bumped
  • Template project files — 5 files with pinned versions updated consistently

Previous Observation (Still Applicable)

TUnit.Playwright is pinned directly in TUnit.Templates/content/TUnit.Playwright/TestProject.csproj but is not centrally managed in Directory.Packages.props, unlike the other TUnit packages. Renovate handles this correctly for now, but centralizing it would improve consistency. This is not a blocker.

Verdict

All versions are consistent across changed files. The PR is clean and correct. ✅ No new concerns — previous approval stands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file PATCH renovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants