chore(deps): update dependency polyfill to 11.2.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	minor	11.0.2 → 11.2.0

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v11.2.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 CLI.

[coderabbitai]

Warning

Review limit reached

@thomhurst, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 902ef61e-1412-4be4-a3f4-99c802fc05ea

📥 Commits

Reviewing files that changed from the base of the PR and between 3ebc0a4 and fd7a2f0.

📒 Files selected for processing (1)

• Directory.Packages.props

---

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Review

This is a Renovate-generated dependency bump: Polyfill 11.0.2 → 11.2.0 in Directory.Packages.props (central package management), a minor version update. No source files under src/ are touched, so none of the zero-allocation / hot-path / test-coverage gates in CLAUDE.md are implicated by this diff itself.

• Correctness/security: No code changes; nothing to evaluate beyond trusting the upstream Polyfill release. Release notes link is present but empty of detail in the PR body — worth a quick skim of the upstream changelog before merge since Polyfill generates/backports code used across the library, but that's a judgment call for the maintainer, not a blocking finding.
• Tests: N/A — pure package version bump, existing CI (build + test) is the correct gate.
• Design: N/A.
• Prior review comments: CodeRabbit hit its review rate limit and did not produce findings; no other human feedback exists on this PR to reconcile.

No actionable issues found in the diff.

[greptile-apps]

Greptile Summary

Updates the centrally managed Polyfill dependency from 11.0.2 to 11.2.0.

• Applies the new version to Dekaf's netstandard2.0 compatibility build through Central Package Management.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

The change is limited to a centrally managed compatibility-package version bump, and the available repository evidence establishes no broken restore, build, runtime, or packaging behavior.

Important Files Changed

Filename	Overview
Directory.Packages.props	Updates the centrally managed Polyfill package version; no concrete compatibility or build defect was established.

_{Reviews (1): Last reviewed commit: "chore(deps): update dependency polyfill ..." | Re-trigger Greptile}