Up nugets

[mikmog]

Up nugets

Summary by CodeRabbit

• Chores
  • Upgraded several platform dependencies to enhance overall stability and performance, ensuring the system remains robust and ready for future improvements.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates package dependency versions in the src/backend/Directory.Packages.props file. It increments versions for a range of packages such as Microsoft.Azure.Functions.Worker.Extensions.EventGrid, Microsoft.Azure.Functions.Worker.Sdk, ApplicationInsights, various Microsoft.Extensions libraries, Microsoft.NET.Test.Sdk, and Testcontainers.MsSql.

Changes

File(s)

Change Summary

src/backend/Directory.Packages.props

Updated package versions: Microsoft.Azure.Functions.Worker.Extensions.EventGrid: 3.4.2 → 3.4.3; Microsoft.Azure.Functions.Worker.Sdk: 2.0.0 → 2.0.1; Microsoft.ApplicationInsights.WorkerService: 2.22.0 → 2.23.0; Microsoft.Extensions.Caching.Hybrid: 9.1.0-preview.1.25064.3 → 9.2.0-preview.1.25105.6; Multiple Microsoft.Extensions.* packages: 9.0.1 → 9.0.2; Microsoft.NET.Test.Sdk: 17.12.0 → 17.13.0; Testcontainers.MsSql: 4.0.0 → 4.3.0

Possibly related PRs

• Downgrade Microsoft.Azure.Functions.Worker.Extensions.EventGrid #36: Updates the version of Microsoft.Azure.Functions.Worker.Extensions.EventGrid in a related manner, though in the opposite direction.
• Up nugets backend #43: Involves modifications to the same src/backend/Directory.Packages.props file, including updates for Microsoft.Extensions.Caching.Hybrid and Microsoft.Extensions.Configuration.Abstractions.

Poem

Oh, I’m a rabbit with a joyful hop,
Watching package versions leap and pop,
Dependencies get a little tune-up treat,
Making code gardens fresh and neat,
I nibble on updates with a happy heart,
Tech carrots keep me running smart!
🐰

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4b45dfa and 2b8e523.

📒 Files selected for processing (1)

• src/backend/Directory.Packages.props (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (csharp)

🔇 Additional comments (1)

src/backend/Directory.Packages.props (1)

13-13:

❓ Verification inconclusive

Package updates look good with a few notes to consider.

Most of these updates are minor/patch versions which generally have low risk. However, there are a couple points worth highlighting:

1. The Microsoft.Extensions.Caching.Hybrid package on line 20 is still using a preview version, and has been updated from 9.1.0-preview to 9.2.0-preview. Preview packages may contain breaking changes or unstable features.

2. Testcontainers.MsSql on line 33 has jumped from 4.0.0 to 4.3.0, which is a more significant update that might include feature changes.

I recommend checking the release notes for these packages to understand any significant changes, especially for preview packages and the larger version jumps:

Also applies to: 16-17, 20-26, 33-33

---

🌐 Web query:

What are the notable changes in Testcontainers.MsSql from version 4.0.0 to 4.3.0?

💡 Result:

The notable changes in Testcontainers.MsSql between versions 4.0.0 and 4.3.0 primarily align with updates in the broader Testcontainers for .NET ecosystem. Key improvements include:

Network & Security Enhancements

• Added support for custom network configurations (e.g., NAT driver) to improve container networking flexibility[4].
• Fixed SSL/TLS certificate handling for mTLS on Windows in .NET 9, resolving PKCS#12 loading issues[4].

SQL Server-Specific Fixes

• Resolved path detection for sqlcmd utility execution, ensuring compatibility with container file structures[4].
• Improved error handling for SQL Server container startup failures with clearer diagnostics[4].

Core Library Improvements

• Introduced container reuse capabilities to reduce startup times for integration tests[4].
• Enhanced port binding logic to support multiple protocols (TCP/UDP/SCTP) and IPv6 configurations[4].
• Added automatic project detection (C#/F#/VB) for streamlined container configuration[4].

Usability & Debugging

• Implemented pausing/unpausing containers during test execution for advanced debugging scenarios[4].
• Upgraded logging integration to work seamlessly with xUnit.net's scoped loggers[4].

These changes collectively improve stability, flexibility, and developer experience when testing SQL Server integrations. For detailed migration guidance, refer to the Testcontainers for .NET release notes[4].

Citations:

• 1: https://micronaut-projects.github.io/micronaut-upgrade/snapshot/
• 2: https://pypi.org/project/testcontainers/3.5.0/
• 3: https://github.com/liquibase/liquibase/releases
• 4: https://github.com/testcontainers/testcontainers-dotnet/releases
• 5: https://www.atomicjar.com/2022/03/easy-jakarta-ee-integration-testing-with-the-payara-platform-and-testcontainers/
• 6: https://java.libhunt.com/testcontainers-java-changelog
• 7: https://www.nuget.org/packages/Testcontainers.MsSql/4.0.0
• 8: https://www.nuget.org/packages/Testcontainers/
• 9: https://github.com/Playtika/testcontainers-spring-boot/releases
• 10: https://dotnet.testcontainers.org/modules/mssql/

---

🌐 Web query:

What changes were made in Microsoft.Extensions.Caching.Hybrid 9.2.0-preview compared to 9.1.0-preview?

💡 Result:

The Microsoft.Extensions.Caching.Hybrid 9.2.0-preview introduces several updates compared to the 9.1.0-preview version, primarily focusing on framework compatibility and dependency alignment:

1. Expanded Framework Support

   • Adds explicit compatibility with .NET 9.0 alongside existing .NET 8.0 support[2].
   • Maintains backward compatibility with .NET Framework 4.6.2 and .NET Standard 2.0/2.1[2].

2. Dependency Updates

   • Upgrades core dependencies to version 9.0.2 for packages like:
     • Microsoft.Extensions.Caching.Abstractions
     • Microsoft.Extensions.Logging.Abstractions
     • System.Text.Json[2]

3. Preview Feature Refinements
   While specific functional changes aren't documented in the search results, preview releases typically include:

   • Performance optimizations for hybrid caching scenarios
   • Enhanced serialization configurability
   • Improved integration with distributed cache backends (Redis, SQL Server, etc.)[2]

For production use, note that both versions remain in preview, with the 9.2.0-preview being newer (released February 2025 vs January 2025 for 9.1.0-preview)[2]. Developers should verify compatibility with their specific .NET runtime versions when upgrading between previews.

Citations:

• 1: https://attariclasses.in/storage/assets/image/pdf/4vbEtrTDF0eNyTDhc1lUk2VEiuIH6RPpOd0c8t6q.pdf
• 2: https://www.nuget.org/packages/Microsoft.Extensions.Caching.Hybrid/
• 3: https://docs.mendix.com/releasenotes/studio-pro/9.0/
• 4: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html-single/9.2_release_notes/index
• 5: https://docs.jboss.org/infinispan/9.2/pdf/user_guide.pdf
• 6: https://deps.dev/npm/@teambit%2Fexport/0.0.749/compare
• 7: https://goteleport.com/docs/changelog/
• 8: https://learn.microsoft.com/en-us/azure/governance/policy/samples/fedramp-high
• 9: https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst
• 10: https://learn.microsoft.com/en-us/powershell/azure/release-notes-azureps?view=azps-13.2.0

---

Package Update Assessment: Verify Release Notes for Preview and Major Jumps

The package updates generally look good, but note the following:

• Microsoft.Extensions.Caching.Hybrid (line 20):
  The update from 9.1.0-preview to 9.2.0-preview now includes expanded support for .NET 9.0, updated core dependencies (like Microsoft.Extensions.Caching.Abstractions and Logging), and some preview refinements. Given that these are preview versions, please verify that these changes integrate without issues in your environment.

• Testcontainers.MsSql (line 33):
  The jump from 4.0.0 to 4.3.0 brings significant updates including custom network configuration support, improved SSL/TLS certificate handling, SQL Server-specific fixes, enhanced container reuse, and better logging features. It’s important to review the detailed release notes to understand any potential impacts on your integration tests.

I recommend checking the release notes for both packages to ensure full compatibility and stability.

Also applies to: lines 16-17, 20-26, and 33-33.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud