GitAuto: [FEATURE] Upgrade RabbitMQ Client Library to Version 7.0.0

[gitauto-ai]

Resolves #596

What is the feature

Upgrade the RabbitMQ Client library from version 6.8.1 to 7.0.0 to incorporate the latest updates, bug fixes, and performance improvements. This ensures compatibility with new features and resolves existing issues addressed in the newer release.

Where / How to code and why

1. Update Dependency:

   • Modify the RabbitMQ.Client NuGet package reference in the project files to version 7.0.0.

2. Address Breaking Changes:

   • Review the RabbitMQ 7.0.0 release notes to identify breaking changes.
   • Adjust the existing codebase to accommodate these breaking changes, ensuring that all functionalities work correctly with the new version.

3. Testing:

   • Execute all unit and integration tests to verify that message publishing, consumption, connection stability, error handling, and any custom integrations function as expected with the updated library.

4. Documentation:

   • Update any relevant documentation to reflect the version upgrade and any changes in usage or configuration resulting from the update.

5. Compatibility Check:

   • Ensure that the updated RabbitMQ.Client library is compatible with other dependent libraries or components within the project.

This comprehensive approach adheres to modern best practices by ensuring dependencies are current, addressing breaking changes proactively, and maintaining system stability through thorough testing.

Anything the issuer needs to do

No action required.

Test these changes locally

git fetch origin
git checkout gitauto/issue-596-20250106-020847
git pull origin gitauto/issue-596-20250106-020847

Summary by Sourcery

Upgrade the RabbitMQ client library to version 7.0.0 to leverage the latest improvements and bug fixes.

Enhancements:

• Update the RabbitMQ.Client NuGet package to version 7.0.0.

Tests:

• Execute unit and integration tests to validate message processing, connection stability, and error handling.

[korbit-ai]

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, gitauto-ai[bot]!). We assume it knows what it's doing!

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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. (Beta)
• @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.

[gitauto-ai]

Committed the Check Run Deep Source Coverage report error fix! Running it again...

[AppVeyorBot]

❌ Build CrispyWaffle 9.1.149 failed (commit f96c266951 by @gitauto-ai[bot])

[AppVeyorBot]

❌ Build CrispyWaffle 9.1.175 failed (commit 72a2b0c639 by @guibranco)

[AppVeyorBot]

❌ Build CrispyWaffle 9.1.176 failed (commit 72a2b0c639 by @guibranco)

[guibranco]

@gstraccini csharpier

[gstraccini]

Running CSharpier on this branch! 🔧

[gstraccini]

✅ CSharpier result:

Formatted 194 files in 1191ms.

[AppVeyorBot]

❌ Build CrispyWaffle 9.1.272 failed (commit 8e0817eb63 by @gstraccini[bot])

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

6:51PM INF scanning for exposed secrets...
6:51PM INF 647 commits scanned.
6:51PM INF scan completed in 767ms
6:51PM INF no leaks found

[AppVeyorBot]

❌ Build CrispyWaffle 9.1.287 failed (commit b833feb1e5 by @guibranco)