Skip to content

chore(deps): update tunit to 1.39.0#2510

Merged
thomhurst merged 1 commit intomainfrom
renovate/tunit
Apr 24, 2026
Merged

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

Conversation

@thomhurst
Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Change Age Confidence
TUnit 1.37.361.39.0 age confidence
TUnit.Assertions 1.37.361.39.0 age confidence
TUnit.Core 1.37.361.39.0 age confidence

Release Notes

thomhurst/TUnit (TUnit)

v1.39.0: 1.39.0

What's Changed
Other Changes
Dependencies

Full Changelog: thomhurst/TUnit@v1.37.36...v1.39.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.

@thomhurst thomhurst added dependencies Pull requests that update a dependency file MINOR renovate-bot labels Apr 24, 2026
@thomhurst thomhurst enabled auto-merge (squash) April 24, 2026 09:22
Copy link
Copy Markdown

@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 — Dependency Update: TUnit 1.37.36 → 1.39.0

This is a Renovate Bot-generated bump of three tightly-coupled TUnit packages:

  • TUnit 1.37.36 → 1.39.0
  • TUnit.Assertions 1.37.36 → 1.39.0
  • TUnit.Core 1.37.36 → 1.39.0

Overall Assessment: ✅ Looks Good

The change is minimal (3 lines in Directory.Packages.props) and follows correct practice.


Observations

All three packages bumped in lockstep — correct.
TUnit, TUnit.Assertions, and TUnit.Core are tightly coupled and must always be on the same version. Mismatching them can cause subtle runtime failures. This PR gets that right.

Version skip from 1.37.x → 1.39.0 (bypasses 1.38.x).
This skips the entire 1.38.x series. This is not a concern because 1.39.0 is cumulative, but it's worth noting that if any 1.38.x release introduced a behavioral change to test scheduling or assertion semantics, tests may surface that for the first time here rather than incrementally. The CI run will be the definitive signal.

What's in 1.39.0?
The release is primarily:

  • Performance improvements: reduced per-test allocations, less lock contention in scheduling/hook caches, collapsed async state-machine layers on the hot test path.
  • Mock bug fixes: several edge cases in generated mock correctness (explicit interface implementations, indexers, keyword identifiers, required-member constructors, null NRE protection). If this project uses TUnit's mocking features, these fixes are directly beneficial.

No breaking changes are indicated in the release notes.

Auto-merge is already enabled.
This is appropriate for a no-code dependency bump from a bot. The CI pipeline is the safety net.


No issues found. Safe to merge once CI passes.

@codacy-production
Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric Results
Complexity 0 (≤ 20 complexity)

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 6324ee2 into main Apr 24, 2026
12 checks passed
@thomhurst thomhurst deleted the renovate/tunit branch April 24, 2026 09:32
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 MINOR renovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants