Skip to content

chore(deps): update _tunitpolyfillversion to 10.9.0#6237

Merged
thomhurst merged 1 commit into
mainfrom
renovate/_tunitpolyfillversion
Jun 13, 2026
Merged

chore(deps): update _tunitpolyfillversion to 10.9.0#6237
thomhurst merged 1 commit into
mainfrom
renovate/_tunitpolyfillversion

Conversation

@thomhurst

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
Polyfill nuget minor 10.8.110.9.0

Release Notes

SimonCropp/Polyfill (Polyfill)

v10.9.0

Compare Source


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 this update 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 Jun 13, 2026
@thomhurst thomhurst enabled auto-merge (squash) June 13, 2026 12:07
@codacy-production

codacy-production Bot commented Jun 13, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

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.

@claude claude Bot 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 standard Renovate bot dependency update bumping the Polyfill package version from 10.8.1 to 10.9.0 in TUnit.Core/TUnit.Core.targets.

Change summary:

  • Single-line version bump in <_TUnitPolyfillVersion> property inside TUnit.Core.targets
  • The Polyfill package is a compile-time-only dependency (source generator/analyzer) injected automatically for netstandard2.0, netstandard2.1, and legacy .NETFramework targets
  • PrivateAssets>all</PrivateAssets> ensures it does not leak into consuming projects' dependency graph

Assessment:
No architectural, correctness, or design concerns. The update is safe:

  • Polyfill is a minor version bump (10.8.110.9.0), which by semver should be additive/non-breaking
  • This package is compile-only (not runtime), so there is no AOT or runtime risk
  • The _TUnitNeedsPolyfill condition correctly gates injection to older TFMs only, so net8/9/10 consumers are unaffected

Approving as a routine dependency maintenance change.

@thomhurst thomhurst force-pushed the renovate/_tunitpolyfillversion branch from 029fa77 to a6e1229 Compare June 13, 2026 13:05

@claude claude Bot 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.

Code Review

PR: chore(deps): update _tunitpolyfillversion to 10.9.0
Change: Single-line version bump in TUnit.Core/TUnit.Core.targets

Assessment: No issues found ✓

This is a clean minor dependency update from Polyfill 10.8.110.9.0 (SimonCropp/Polyfill). The change is exactly what it needs to be — one line, no risk.

Observations:

  • The version string is pinned in a dedicated MSBuild property (_TUnitPolyfillVersion), which is the right pattern for a conditionally-included transitive dependency. Centralizing the version here makes future updates like this one trivial to review.
  • The Polyfill package is only applied to netstandard2.0, netstandard2.1, and .NETFramework targets (as guarded by _TUnitNeedsPolyfill), so the blast radius for any regression from this bump is limited to legacy TFM consumers only.
  • Codacy reports 0 new issues.

No concerns. Ready to merge.

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