deps: bump Grpc packages to 2.76.0 and Protobuf to 3.33.2

[peteski22]

What's Changed

📦 Dependency Updates

• Bump Google.Protobuf from 3.29.1 to 3.33.2
• Bump Grpc.AspNetCore from 2.70.0 to 2.76.0
• Bump Grpc.Tools from 2.70.0 to 2.76.0

Summary by CodeRabbit

Release Notes

• Chores
  • Updated NuGet package dependencies to latest versions, including protocol buffer and gRPC libraries to version 2.76.0+
  • Upgraded Microsoft.Extensions packages to 8.0.0 across the SDK
  • Updated system-level dependencies to align with .NET 8.0 compatibility standards

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The pull request updates NuGet package versions across project and lock files. Key updates include Google.Protobuf (3.29.1 → 3.33.2), Grpc.AspNetCore (2.70.0 → 2.76.0), and Microsoft.Extensions packages to 8.0.0, aligning with .NET 8.0 compatibility.

Changes

Cohort / File(s)	Summary
SDK Project Dependencies src/MozillaAI.Mcpd.Plugins.Sdk/MozillaAI.Mcpd.Plugins.Sdk.csproj	Updated direct package references: Google.Protobuf 3.29.1 → 3.33.2, Grpc.AspNetCore 2.70.0 → 2.76.0, Grpc.Tools 2.70.0 → 2.76.0
SDK Lock Files src/MozillaAI.Mcpd.Plugins.Sdk/packages.lock.json	Comprehensive version bumps across transitive dependencies; Google.Protobuf to 3.33.2, Grpc.AspNetCore and related packages to 2.76.0, Microsoft.Extensions family to 8.0.0; updated content hashes and dependency mappings throughout
Examples Plugin Lock File examples/MyPlugin/packages.lock.json	Updated transitive dependencies mirroring SDK changes; Google.Protobuf to 3.33.2, Grpc.AspNetCore suite to 2.76.0, Microsoft.Extensions packages to 8.0.0 with corresponding dependency trees

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: bumping Grpc packages to 2.76.0 and Protobuf to 3.33.2, which aligns with the primary dependency updates in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2755e53 and 17b3973.

📒 Files selected for processing (3)

• examples/MyPlugin/packages.lock.json
• src/MozillaAI.Mcpd.Plugins.Sdk/MozillaAI.Mcpd.Plugins.Sdk.csproj
• src/MozillaAI.Mcpd.Plugins.Sdk/packages.lock.json

🔇 Additional comments (2)

src/MozillaAI.Mcpd.Plugins.Sdk/packages.lock.json (1)

1-203: LGTM!

The lock file is consistent with the package reference updates in the .csproj. Direct dependencies and transitive dependency versions are properly resolved, with Microsoft.Extensions.* packages at 8.0.0 which is compatible with the .NET 9.0 target framework.

examples/MyPlugin/packages.lock.json (1)

1-203: LGTM!

The example project's lock file is correctly regenerated and consistent with the SDK's updated dependencies. The project reference to mozillaai.mcpd.plugins.sdk properly reflects the new package version ranges.