Skip to content

chore(deps): update tunit to 1.19.11#5106

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

chore(deps): update tunit to 1.19.11#5106
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.01.19.11
TUnit.AspNetCore nuget patch 1.19.01.19.11
TUnit.Assertions nuget patch 1.19.01.19.11
TUnit.Assertions.FSharp nuget patch 1.19.01.19.11
TUnit.Core nuget patch 1.19.01.19.11
TUnit.Engine nuget patch 1.19.01.19.11
TUnit.Playwright nuget patch 1.19.01.19.11

Release Notes

thomhurst/TUnit (TUnit)

v1.19.11: 1.19.11

What's Changed
Other Changes
Dependencies

Full Changelog: v1.19.0...v1.19.11


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 8, 2026
@thomhurst thomhurst enabled auto-merge (squash) March 8, 2026 20:44
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.

Dependency Update Review: TUnit 1.19.0 → 1.19.11

This is a Renovate Bot-generated patch update bumping all TUnit packages (TUnit, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Playwright) from 1.19.0 to 1.19.11.

Changes Summary

All modifications are version bumps in two locations:

  1. Directory.Packages.props — central package version management for the main solution
  2. TUnit.Templates/content/*/ — hardcoded versions in project templates (5 template project files)

Observations

Template projects use hardcoded versions instead of central package management.
The template .csproj/.fsproj/.vbproj files under TUnit.Templates/content/ each specify explicit PackageReference versions rather than deferring to a central Directory.Packages.props. This is likely intentional since these are standalone template artifacts that get copied to users' machines and must be self-contained. However, it does mean every patch bump requires updating both Directory.Packages.props and each template project individually — as seen here with 5 separate template file changes for a single version bump.

If the template files could reference a shared version property (e.g., via a Directory.Build.props within the templates folder), it would reduce the surface area of version bump PRs like this one. That said, this may conflict with the requirement that templates be self-contained when installed via dotnet new.

The changelog content of 1.19.0 → 1.19.11 looks safe for this kind of internal self-referential update:

  • HTML report fixes (sort order, SVG icon)
  • Performance improvements (reduced list/enumerable allocations, char instead of string for joins)
  • No breaking changes indicated

Auto-merge is enabled, which is appropriate for a patch dependency update on packages that are developed and maintained within this same repository.

Verdict

The changes are correct and safe. No issues with the approach — this is a routine automated dependency update. The slight friction of updating template files separately from Directory.Packages.props is a pre-existing structural concern, not introduced by this PR.

@thomhurst thomhurst merged commit 79bfd9d into main Mar 8, 2026
15 checks passed
@thomhurst thomhurst deleted the renovate/tunit branch March 8, 2026 21:12
This was referenced Mar 9, 2026
This was referenced Mar 9, 2026
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