feat: Prepare next release cycle (4.10.0)

[HofmeisterAn]

What does this PR do?

-

Why is it important?

-

Related issues

-

[netlify]

✅ Deploy Preview for testcontainers-dotnet ready!

Name	Link
🔨 Latest commit	c4cf8cb
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-dotnet/deploys/6924843d6238140008a63e21
😎 Deploy Preview	https://deploy-preview-1586--testcontainers-dotnet.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Updated package version to 4.10.0.

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

Walkthrough

A version number is incremented from 4.9.0 to 4.10.0 in the project's build properties configuration file. No build logic, flow, or exported declarations are modified.

Changes

Cohort / File(s)	Summary
Version Bump Directory.Build.props	Updated PackageVersion property from 4.9.0 to 4.10.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• feat: Prepare next release cycle (4.9.0) #1561: Similar version bump in the same Directory.Build.props file (4.8.1→4.9.0), establishing a version release pattern.

Poem

🐰 A version hops forth, from nine to ten,
No logic bent, no code to mend,
Just numbers that gleam in the prop's domain,
A step forward taken—simple, plain!
✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is largely incomplete with only placeholder content (hyphens) in all mandatory and recommended sections.	Fill in all mandatory sections: explain what changes were made and why they are important. Optionally add related issues, testing instructions, and follow-ups.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately summarizes the main change: preparing the next release cycle by updating the package version to 4.10.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/prepare-next-release-cycle

---

📜 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 3f9de42 and c4cf8cb.

📒 Files selected for processing (1)

• Directory.Build.props (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-11-17T17:58:43.958Z

Learnt from: diegosasw
Repo: testcontainers/testcontainers-dotnet PR: 1583
File: src/Testcontainers.KurrentDb/Testcontainers.KurrentDb.csproj:7-7
Timestamp: 2025-11-17T17:58:43.958Z
Learning: In the testcontainers-dotnet repository, JetBrains.Annotations should use version 2023.3.0 to maintain consistency with the main Testcontainers csproj, rather than always using the latest available version.

Applied to files:

• Directory.Build.props

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (67)

• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.BigQuery, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Azurite, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Cassandra, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.BigQuery, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Azurite, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Cassandra, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.BigQuery, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Azurite, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Cassandra, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.BigQuery, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Cassandra, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ClickHouse, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.BigQuery, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Cassandra, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ClickHouse, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.BigQuery, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ClickHouse, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.BigQuery, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.CockroachDb, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ClickHouse, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.CockroachDb, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ClickHouse, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Consul, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.CockroachDb, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)
• GitHub Check: ci (Testcontainers.ActiveMq, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ClickHouse, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Bigtable, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.Consul, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.CockroachDb, ubuntu-24.04)
• GitHub Check: ci (Testcontainers.ArangoDb, ubuntu-24.04)
• GitHub Check: analyze (csharp)

🔇 Additional comments (1)

Directory.Build.props (1)

5-5: Version bump verified as complete and properly centralized.

The version change from 4.9.0 to 4.10.0 is isolated to Directory.Build.props (line 5) with no other hardcoded version references requiring updates. No conflicting v4.10.0 tag exists. The repository's automated changelog system means no manual CHANGELOG.md updates are needed. The change is clean and ready.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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