⬆️ bump dependencies to support .net9-rc2

[gimlichael]

PR Classification

Package version updates and test environment configuration change.

PR Summary

This pull request updates package versions and modifies the Docker image for the test environment.

• Directory.Build.props: Updated Codebelt.Extensions.Xunit.App package to 9.0.0-preview.10,
• Codebelt.Extensions.Swashbuckle.AspNetCore.csproj: Updated Codebelt.Extensions.Asp.Versioning package to 9.0.0-preview.3,
• Codebelt.Extensions.Swashbuckle.AspNetCore.Tests.csproj: Updated Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json package to 9.0.0-preview.11,
• testenvironments.json: Updated Docker image for Docker-Ubuntu test environment.

Summary by CodeRabbit

• New Features

  • Updated package versions for improved functionality and compatibility.

• Bug Fixes

  • Enhanced Docker environment configuration with a new image version.

• Chores

  • Updated project properties for various testing-related packages to ensure optimal performance.

[coderabbitai]

Walkthrough

The pull request includes updates to several project files, primarily focusing on version changes for various package references and a Docker image in the configuration files. Specifically, the Codebelt.Extensions.Xunit.App, Codebelt.Extensions.Asp.Versioning, and Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json packages have had their versions incremented. Additionally, the dockerImage property in testenvironments.json has been updated to reflect a new version of the Docker image used for testing environments.

Changes

File	Change Summary
Directory.Build.props	Updated Codebelt.Extensions.Xunit.App package version from 9.0.0-preview.8 to 9.0.0-preview.10.
src/Codebelt.Extensions.Swashbuckle.AspNetCore/Codebelt.Extensions.Swashbuckle.AspNetCore.csproj	Updated Codebelt.Extensions.Asp.Versioning package version from 9.0.0-preview.2 to 9.0.0-preview.3.
test/Codebelt.Extensions.Swashbuckle.AspNetCore.Tests/Codebelt.Extensions.Swashbuckle.AspNetCore.Tests.csproj	Updated Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json package version from 9.0.0-preview.9 to 9.0.0-preview.11.
testenvironments.json	Updated dockerImage property from "gimlichael/ubuntu-testrunner:net6.0.425-net8.0.401-9.0.100-rc.1.24452.12" to "gimlichael/ubuntu-testrunner:6.0.427-net8.0.403-9.0.100-rc.2.24474.11".

Possibly related PRs

• ⬆️ bumb dependencies #3: The changes in this PR also involve updating the Codebelt.Extensions.Xunit.App package version in the Directory.Build.props file, which directly relates to the version update in the main PR.

Poem

🐰 In the garden of code, we hop and play,
With versions updated, we brighten the day.
From Xunit to Docker, all fresh and new,
Each change a step, in our testing zoo.
So let’s celebrate, with a joyful cheer,
For in this code, we have nothing to fear! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6b2f384 and dc48e98.

📒 Files selected for processing (4)

• Directory.Build.props (1 hunks)
• src/Codebelt.Extensions.Swashbuckle.AspNetCore/Codebelt.Extensions.Swashbuckle.AspNetCore.csproj (1 hunks)
• test/Codebelt.Extensions.Swashbuckle.AspNetCore.Tests/Codebelt.Extensions.Swashbuckle.AspNetCore.Tests.csproj (1 hunks)
• testenvironments.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• test/Codebelt.Extensions.Swashbuckle.AspNetCore.Tests/Codebelt.Extensions.Swashbuckle.AspNetCore.Tests.csproj

🧰 Additional context used

🔇 Additional comments (4)

testenvironments.json (1)

12-12: LGTM! Docker image updated to latest versions.

The Docker image has been updated to include the latest versions of .NET:

• .NET 6.0: 6.0.427 (minor update)
• .NET 8.0: 8.0.403 (minor update)
• .NET 9.0: 9.0.100-rc.2.24474.11 (RC2 update)

This change aligns with the PR objective of supporting .NET 9 RC2 and keeps other .NET versions up-to-date.

To ensure the new Docker image is available and functions as expected, please run the following verification script:

This script will:

1. Pull the updated Docker image
2. List the .NET runtimes available in the image
3. Run a simple .NET "Hello, World!" program

Please review the output to confirm that the image is available and contains the expected .NET versions.

src/Codebelt.Extensions.Swashbuckle.AspNetCore/Codebelt.Extensions.Swashbuckle.AspNetCore.csproj (2)

15-15: Consider updating Swashbuckle.AspNetCore package.

While updating dependencies, it's worth checking if there's a newer version of Swashbuckle.AspNetCore available that's compatible with .NET 9 RC2. The current version is 6.8.1, but there might be a more recent version that better aligns with the target .NET version.

Let's check for the latest version of Swashbuckle.AspNetCore:

#!/bin/bash
# Description: Check the latest version of Swashbuckle.AspNetCore package
# Expected result: Display the latest version information

dotnet list package --highest-patch Swashbuckle.AspNetCore

If a newer version is available and compatible, consider updating it to ensure full compatibility with .NET 9 RC2.

---

14-14: Package version update looks good.

The Codebelt.Extensions.Asp.Versioning package has been updated from version 9.0.0-preview.2 to 9.0.0-preview.3. This change aligns with the PR objectives to bump dependencies for .NET 9 RC2 support.

To ensure consistency across the project, let's verify if there are any other occurrences of this package that might need updating:

Additionally, let's check if there are any hardcoded version strings that might need updating:

Directory.Build.props (1)

80-80: LGTM! Verify compatibility with other dependencies.

The update of Codebelt.Extensions.Xunit.App from version 9.0.0-preview.8 to 9.0.0-preview.10 aligns with the PR objective of bumping dependencies to support .NET 9 RC2. This change appears to be a minor update within the preview cycle.

To ensure compatibility, please run the following script to check for any version conflicts or breaking changes:

---

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 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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.81%. Comparing base (6b2f384) to head (dc48e98).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage   84.81%   84.81%           
=======================================
  Files          11       11           
  Lines         237      237           
  Branches        9        9           
=======================================
  Hits          201      201           
  Misses         36       36           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[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 SonarCloud