chore(deps): update dependency minimatch to v10

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
minimatch	resolutions	major	9.0.9 → 10.2.5

---

Release Notes

isaacs/minimatch (minimatch)

v10.2.5

Compare Source

v10.2.4

Compare Source

v10.2.3

Compare Source

v10.2.2

Compare Source

v10.2.1

Compare Source

v10.2.0

Compare Source

v10.1.3

Compare Source

v10.1.2

Compare Source

v10.1.1

Compare Source

v10.1.0

Compare Source

v10.0.3

Compare Source

v10.0.2

Compare Source

v10.0.1

Compare Source

v10.0.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 Renovate Bot.

[claude]

Code Review: chore(deps): update dependency minimatch to v10

This is a Renovate-generated dependency update bumping from → in the docs/ directory.

Summary

The change is confined to two files:

• docs/package.json — updates the resolutions override
• docs/yarn.lock — updates the resolved version and tightens the brace-expansion peer range from ^5.0.2 to ^5.0.5

Observations

Major version bump via resolutions
This is a yarn resolutions entry, meaning it forces all transitive consumers of minimatch (including packages that declared ^9.0.3) to receive 10.2.5. Since minimatch v10 is a major bump from v9, there are potentially breaking API changes (e.g., minimatch.minimatch() function signature changes, removed unsafe option, etc.). However, because this is only applied to the docs/ build tooling and not to the core TUnit library, the blast radius is minimal. The docs site CI checks should validate this.

No concerns with the brace-expansion peer range tightening
The lock file update from brace-expansion@^5.0.2 to ^5.0.5 is consistent — 5.0.5 is already present and locked, so this is purely a semver floor bump with no version change.

No TUnit core impact
This PR touches only the docs/ subdirectory and has no effect on the C# source, tests, or the Microsoft.Testing.Platform-based engine.

Verdict

✅ Looks good. This is a routine dependency bump scoped entirely to docs build tooling. The resolution override pattern is appropriate for managing transitive vulnerability fixes. Automerge once CI passes.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[claude]

Code Review: chore(deps): update dependency minimatch to v10

This is a Renovate-generated dependency update bumping minimatch from 9.0.7 to 10.2.5 in the docs/ directory.

Summary

The change is confined to two files:

• docs/package.json: updates the resolutions override
• docs/yarn.lock: updates the resolved version and tightens the brace-expansion peer range from ^5.0.2 to ^5.0.5

Observations

Major version bump via resolutions

This is a yarn resolutions entry, meaning it forces all transitive consumers of minimatch (including packages that declared ^9.0.3) to receive 10.2.5. Since minimatch v10 is a major bump from v9, there are potentially breaking API changes. However, because this is only applied to the docs/ build tooling and not to the core TUnit library, the blast radius is minimal. The docs site CI checks should validate this.

No concerns with the brace-expansion peer range tightening

The lock file update from brace-expansion@^5.0.2 to ^5.0.5 is consistent — 5.0.5 is already present and locked, so this is purely a semver floor bump with no version change.

No TUnit core impact

This PR touches only the docs/ subdirectory and has no effect on the C# source, tests, or the Microsoft.Testing.Platform-based engine.

Verdict

Looks good. This is a routine dependency bump scoped entirely to docs build tooling. The resolution override pattern is appropriate for managing transitive vulnerability fixes. Automerge once CI passes.

[claude]

This is a routine automated dependency update from Renovate Bot, upgrading the minimatch npm package in the docs/ directory from v9.0.9 to v10.2.5.

Scope: The changes are limited entirely to the docs/ directory (package.json and yarn.lock). This is documentation tooling only and has no impact on:

• The .NET test framework core
• Source generator or reflection engine modes
• AOT compatibility
• Any C# code, tests, or build artifacts

Change correctness: The diff looks correct:

• package.json resolution pinned from 9.0.9 to 10.2.5
• yarn.lock updated with the new resolved hash/integrity for minimatch@10.2.5
• The transitive dependency brace-expansion resolution constraint was correctly updated from ^2.0.2 to ^5.0.5 to match what minimatch v10 requires

Breaking change note: minimatch v10 is a major version bump (hence the MAJOR label). The brace-expansion dependency moved from v2 to v5, which is also a major bump. However, since this is purely a resolutions override in the docs package (used to avoid security advisories in transitive deps), the actual consuming packages haven't changed — this just ensures a safe resolved version is used. No docs functionality should be affected.

Approved — the change is correct, well-scoped, and safe to merge.

[claude]

Code Review: chore(deps): update dependency minimatch to v10

Changes Reviewed

• docs/package.json: minimatch resolution bumped from 9.0.9 → 10.2.5
• docs/yarn.lock: resolved version + integrity hash updated; brace-expansion dependency tightened from ^2.0.2 → ^5.0.5

Analysis

Scope is well-contained. Both files are under docs/ — this is purely documentation build tooling. No C# source, no TUnit engine, no source generator, no AOT-sensitive code is touched.

Major version bump is safe here. The resolutions override pattern is the correct mechanism for forcing a transitive dep to a safe version. Although minimatch v10 is a breaking change from v9, the resolutions block just ensures the resolved version is v10 — the actual consuming packages in docs/ haven't changed their declared dependency ranges. The docs CI pipeline is the right gate for catching any runtime incompatibility.

brace-expansion floor bump is consistent. Moving from ^2.0.2 to ^5.0.5 reflects that minimatch v10 dropped its brace-expansion v2 dependency in favor of v5. The already-pinned 5.0.5 in the lock file satisfies this constraint — no net version change.

Previous reviews covered the key points thoroughly. Nothing new to flag.

Verdict

✅ Approved. Routine Renovate-generated bump, correct and well-scoped. Safe to merge once CI passes.