⬆️ bump dependencies

[gimlichael]

This pull request includes updates to dependencies, Docker configurations, and test environments to ensure compatibility with newer versions and improve overall stability.

Dependency Updates

• Updated several package versions in Directory.Packages.props, including Codebelt.Extensions.Xunit, Microsoft.NET.Test.Sdk, Microsoft.Data.Sqlite, and System.Text.Json, to their latest versions for enhanced functionality and bug fixes. [1] [2] [3]

Docker Configuration Updates

• Updated the base and final nginx image versions in .docfx/Dockerfile.docfx from 1.27.4-alpine to 1.28.0-alpine for improved security and performance. [1] [2]

Test Environment Updates

• Updated the dockerImage in testenvironments.json to gimlichael/ubuntu-testrunner:mono-net8.0.411-9.0.301 to align with the latest runtime versions.

Summary by CodeRabbit

• Chores
  • Updated the nginx base image to a newer version for improved stability and security.
  • Upgraded several internal and test-related package dependencies to their latest versions.
  • Refreshed the Docker test environment image to ensure compatibility with recent updates.

[coderabbitai]

Walkthrough

This update revises dependency versions across several files. The Dockerfile switches to a newer nginx base image. The Directory.Packages.props file increments versions for multiple Codebelt.Extensions.*, Microsoft, and xUnit-related packages. The testenvironments.json file updates the Docker image tag for the Ubuntu test environment. No code logic or public API changes are introduced.

Changes

File(s)	Change Summary
.docfx/Dockerfile.docfx	Updated nginx base image from 1.27.4-alpine to 1.28.0-alpine in both build and runtime stages.
Directory.Packages.props	Bumped versions for Codebelt.Extensions.*, Microsoft, xUnit, Sqlite, and related packages.
testenvironments.json	Updated Docker-Ubuntu test environment image tag to newer mono/net versions.

Possibly related PRs

• ⬆️ bump dependencies #103: Updates some Codebelt.Extensions.* packages in Directory.Packages.props from release candidate to stable versions, similar to the package version changes in this PR.

Poem

In the warren of code, dependencies grow,
With a hop and a skip, we let old versions go.
Nginx is fresher, the tests will still run,
New numbers abound—oh, isn’t this fun?
A carrot for progress, a patch for the day,
The rabbit approves: hip-hip-hooray! 🥕

---

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

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.docfx/Dockerfile.docfx (1)

1-1: Ensure consistent multi-platform builds
Consider adding --platform=$BUILDPLATFORM to the final nginx stage for consistent multi-arch builds:

-FROM nginx:1.28.0-alpine AS final
+FROM --platform=$BUILDPLATFORM nginx:1.28.0-alpine AS final

This mirrors the base stage platform specification.

Also applies to: 11-11

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b57def7 and 498ee5f.

📒 Files selected for processing (3)

• .docfx/Dockerfile.docfx (2 hunks)
• Directory.Packages.props (3 hunks)
• testenvironments.json (1 hunks)

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

• GitHub Check: 🐧 Prepare Linux / 🏷️ Restore
• GitHub Check: 🪟 Prepare Windows / 🏷️ Restore

🔇 Additional comments (7)

Directory.Packages.props (6)

8-10: Central xUnit extensions bump approved
Upgrading Codebelt.Extensions.Xunit and related packages to 10.0.2 is consistent and aligns with minor patch semantics.

---

12-13: Verify test SDK upgrade compatibility
Bumping Microsoft.NET.Test.Sdk and Microsoft.TestPlatform.ObjectModel to 17.14.1 could affect test discovery or reporting.
Please validate that all pipelines and adapters are compatible with the updated SDKs.

---

22-22: xUnit Visual Studio runner patch bump OK
Updating xunit.runner.visualstudio to 3.1.1 is a non-breaking patch.

---

25-25: SQLite net4 package version bump approved
Upgrading Microsoft.Data.Sqlite to 8.0.17 for net4 is consistent with other net8 updates.

---

37-37: SQLite net8/netstandard2 package version bump approved
Aligning Microsoft.Data.Sqlite to 8.0.17 under net8/netstandard2 is correct.

---

45-50: Core libraries patch versions for .NET9 approved
Upgrading Microsoft.Data.Sqlite and related Microsoft.Extensions.* & System.Text.Json to 9.0.6 aligns with patch release best practices.

testenvironments.json (1)

12-12: Verify new test runner Docker image exists
The dockerImage tag was updated to gimlichael/ubuntu-testrunner:mono-net8.0.411-9.0.301.
Please confirm the image is available in the registry (e.g., docker pull gimlichael/ubuntu-testrunner:mono-net8.0.411-9.0.301).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.82%. Comparing base (e077271) to head (498ee5f).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #122      +/-   ##
==========================================
- Coverage   80.17%   79.82%   -0.35%     
==========================================
  Files         596      593       -3     
  Lines       18513    18283     -230     
  Branches     1902     1865      -37     
==========================================
- Hits        14843    14595     -248     
- Misses       3599     3618      +19     
+ Partials       71       70       -1     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[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