Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V4.0.1/package maintenance #31

Merged
merged 7 commits into from
Jan 31, 2025
Merged

V4.0.1/package maintenance #31

merged 7 commits into from
Jan 31, 2025

Conversation

gimlichael
Copy link
Member

@gimlichael gimlichael commented Jan 31, 2025

This pull request includes several updates to the project configuration files, dependency management, and package release notes. The most important changes involve updating the target framework, adding Dependabot configuration, and updating package release notes to reflect the latest dependencies.

Configuration updates:

Dependency management:

  • .github/dependabot.yml: Added a new Dependabot configuration to manage dependencies for nuget and github-actions ecosystems with a weekly update schedule.

Package release notes:

Summary by CodeRabbit

Based on the comprehensive summary of changes, here are the release notes:

Release Notes - Version 4.0.1

  • Dependency Updates

    • Updated package dependencies to their latest versions
    • Removed support for .NET 6 (LTS)
    • Added compatibility with .NET 9 and .NET 8
  • Minor Improvements

    • Updated copyright year to 2025
    • Minor refinements in package configurations
    • Updated test environment Docker image
  • Package Enhancements

    • Added ClientConfigurations property in Amazon messaging options
    • Updated extension methods with optional parameters
    • Refined marshalling and serialization interfaces
  • Documentation

    • Updated documentation links
    • Regenerated documentation with latest changes

This service update focuses on dependency management, framework compatibility, and minor improvements across the Savvyio ecosystem.

@gimlichael gimlichael self-assigned this Jan 31, 2025
Copy link

coderabbitai bot commented Jan 31, 2025

Walkthrough

This pull request encompasses a comprehensive update across multiple files in the Savvyio project, focusing on version 4.0.1. The changes primarily involve updating package versions, removing .NET 6 support, and preparing the project for .NET 9 compatibility. Key modifications include updating dependencies, copyright years, and release notes across various packages, along with minor configuration adjustments in build and test environment files.

Changes

File/Directory Change Summary
.docfx/Dockerfile.docfx Updated base image from nginx:1.27.0-alpine to nginx:1.27.3-alpine
.docfx/docfx.json Updated target framework to net9.0 and copyright year to 2025
.github/dependabot.yml Added new Dependabot configuration for NuGet and GitHub Actions
.nuget/*/PackageReleaseNotes.txt Updated to version 4.0.1, removed .NET 6 support, updated dependencies
CHANGELOG.md Added new version entry for 4.0.1
Directory.Build.props Updated copyright year to 2025, removed SourceLink GitHub reference
Directory.Packages.props Updated multiple package versions
LICENSE.md Updated copyright year to 2025
README.md Added duplicate documentation link
testenvironments.json Updated Docker image version

Possibly related PRs

Poem

🐰 A Rabbit's Versioning Tale 🚀

From six to nine, we leap with grace,
Dependencies dance at a faster pace
Nginx, DocFX, and packages align
Our code evolves, simply divine!

Version bump with a bunny's might! 🌟


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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (10)
.nuget/Savvyio.Extensions.Dispatchers/PackageReleaseNotes.txt (1)

5-5: Consider more concise wording.

The current wording "with respect to TFMs" could be simplified while maintaining technical accuracy.

Consider this alternative:

-CHANGED Dependencies to latest and greatest with respect to TFMs
+CHANGED Dependencies to latest versions for all target frameworks
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Commands.Messaging/PackageReleaseNotes.txt (1)

4-5: Consider improving the release notes clarity.

The phrase "with respect to TFMs" could be simplified to "for target frameworks" or just removed since it's implied.

-# ALM
-- CHANGED Dependencies to latest and greatest with respect to TFMs
+# ALM
+- CHANGED Dependencies to latest versions for all target frameworks
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Domain.EventSourcing/PackageReleaseNotes.txt (1)

5-5: Consider rephrasing for clarity.

The phrase "with respect to" can be simplified for better readability.

-- CHANGED Dependencies to latest and greatest with respect to TFMs
+- CHANGED Dependencies to latest and greatest for TFMs
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.Dapper/PackageReleaseNotes.txt (1)

5-5: Consider rephrasing for clarity.

The phrase "with respect to" can be simplified for better readability.

-- CHANGED Dependencies to latest and greatest with respect to TFMs
+- CHANGED Dependencies to latest and greatest for TFMs
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.EFCore.Domain/PackageReleaseNotes.txt (1)

5-5: Consider rephrasing for clarity.

The phrase "with respect to" can be simplified for better readability.

-- CHANGED Dependencies to latest and greatest with respect to TFMs
+- CHANGED Dependencies to latest and greatest for TFMs
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.EFCore.Domain.EventSourcing/PackageReleaseNotes.txt (1)

5-5: Consider rephrasing for clarity.

The phrase "with respect to" can be simplified for better readability.

-- CHANGED Dependencies to latest and greatest with respect to TFMs
+- CHANGED Dependencies to latest and greatest for TFMs
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.Domain/PackageReleaseNotes.txt (1)

5-5: Consider rephrasing for clarity.

The phrase "with respect to" can be simplified for better readability.

-- CHANGED Dependencies to latest and greatest with respect to TFMs
+- CHANGED Dependencies to latest and greatest for TFMs
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Commands/PackageReleaseNotes.txt (1)

5-5: Consider simplifying the wording.

The phrase "with respect to" could be simplified to "for" to improve readability.

-- CHANGED Dependencies to latest and greatest with respect to TFMs
+- CHANGED Dependencies to latest and greatest for TFMs
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Domain/PackageReleaseNotes.txt (1)

5-5: Consider simplifying the dependency update message.

The phrase "with respect to TFMs" is wordy. Consider a more concise alternative:

-- CHANGED Dependencies to latest and greatest with respect to TFMs
++ CHANGED Dependencies to latest versions for supported frameworks
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DapperExtensions/PackageReleaseNotes.txt (1)

1-5: Improve clarity in dependency update description.

The phrase "with respect to TFMs" is wordy. Consider a more concise alternative.

Apply this diff to improve clarity:

-# ALM
-- CHANGED Dependencies to latest and greatest with respect to TFMs
+# ALM
+- CHANGED Dependencies to latest versions for all target frameworks
🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 152e092 and e0b6682.

📒 Files selected for processing (39)
  • .docfx/Dockerfile.docfx (1 hunks)
  • .docfx/docfx.json (3 hunks)
  • .github/dependabot.yml (1 hunks)
  • .nuget/Savvyio.App/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Commands.Messaging/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Commands/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Core/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Domain.EventSourcing/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Domain/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.EventDriven.Messaging/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.EventDriven/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.Dapper/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DapperExtensions/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection.Dapper/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection.DapperExtensions/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection.Domain/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection.EFCore.Domain.EventSourcing/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection.EFCore.Domain/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection.EFCore/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection.QueueStorage/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection.SimpleQueueService/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.DependencyInjection/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.Dispatchers/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.EFCore.Domain.EventSourcing/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.EFCore.Domain/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.EFCore/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.Newtonsoft.Json/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.QueueStorage/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.SimpleQueueService/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Extensions.Text.Json/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Messaging/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Savvyio.Queries/PackageReleaseNotes.txt (1 hunks)
  • CHANGELOG.md (1 hunks)
  • Directory.Build.props (1 hunks)
  • Directory.Packages.props (1 hunks)
  • LICENSE.md (1 hunks)
  • README.md (1 hunks)
  • test/Savvyio.Domain.EventSourcing.Tests/TracedAggregateRootTest.cs (1 hunks)
  • testenvironments.json (1 hunks)
✅ Files skipped from review due to trivial changes (5)
  • test/Savvyio.Domain.EventSourcing.Tests/TracedAggregateRootTest.cs
  • LICENSE.md
  • .docfx/Dockerfile.docfx
  • testenvironments.json
  • CHANGELOG.md
🧰 Additional context used
🪛 LanguageTool
.nuget/Savvyio.Extensions.DependencyInjection/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.EventDriven/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Domain/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.EFCore/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Messaging/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.Newtonsoft.Json/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Commands/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Domain.EventSourcing/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.EFCore.Domain/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.EFCore.Domain.EventSourcing/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.EFCore.Domain.EventSourcing/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.Text.Json/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.EventDriven.Messaging/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.SimpleQueueService/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.Dapper/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Commands.Messaging/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.EFCore/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.Domain/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.Dispatchers/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.SimpleQueueService/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.EFCore.Domain/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.App/PackageReleaseNotes.txt

[duplication] ~5-~5: Possible typo: you repeated a word.
Context: ...ity: .NET 9 and .NET 8   # References - Savvyio - Savvyio.Commands - Savvyio.Commands.Messaging -...

(ENGLISH_WORD_REPEAT_RULE)

.nuget/Savvyio.Core/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.Dapper/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DapperExtensions/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.DapperExtensions/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.QueueStorage/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.QueueStorage/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Queries/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

🪛 markdownlint-cli2 (0.17.2)
README.md

33-33: Bare URL used
null

(MD034, no-bare-urls)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: 🛠️ Build (Release, net8.0)
  • GitHub Check: 🛠️ Build (Release, net9.0)
  • GitHub Check: 🛠️ Build (Debug, net8.0)
  • GitHub Check: 🛠️ Build (Debug, net9.0)
🔇 Additional comments (30)
.nuget/Savvyio.Extensions.Dispatchers/PackageReleaseNotes.txt (1)

1-2: LGTM! Version and availability information is accurate.

The version number and framework compatibility align with the PR objectives.

Directory.Packages.props (3)

33-35: Note the major version update in xunit.runner.visualstudio.

The update from 2.8.2 to 3.0.1 is a major version change. Please ensure all test projects are compatible with this update.


38-46: LGTM! Entity Framework Core updates look good.

The Entity Framework Core updates for both .NET 8 and .NET 9 are minor version increments and maintain version consistency across related packages.


7-10: Verify AWS and Azure package compatibility.

The AWS and Azure package updates are minor version increments. Please ensure these versions are stable and don't introduce breaking changes.

✅ Verification successful

AWS and Azure package versions are safe to use

The specified versions are stable and free from known vulnerabilities:

  • AWSSDK.SQS 3.7.400.86: No known security issues
  • Azure.Identity 1.13.2: Clear of all known vulnerabilities (requires >1.11.4)
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any known issues or breaking changes in the AWS and Azure packages
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NUGET, package: "AWSSDK.SQS") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
    }
  }
}'

gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NUGET, package: "Azure.Identity") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
    }
  }
}'

Length of output: 1168

Directory.Build.props (1)

16-16: LGTM! Copyright year updated.

The copyright year has been updated to 2025, which aligns with the current year.

.github/dependabot.yml (1)

1-17: Verify the open-pull-requests-limit setting.

The configuration sets open-pull-requests-limit: 0 for all ecosystems, which means Dependabot won't create any PRs. Is this intentional? Consider setting this to a positive number (e.g., 5 or 10) to allow Dependabot to create PRs for dependency updates.

.nuget/Savvyio.Messaging/PackageReleaseNotes.txt (1)

1-5: LGTM! Version and dependency updates are consistent.

The changes align with the PR objectives, maintaining support for .NET 9 and .NET 8 while updating dependencies.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.EFCore.Domain/PackageReleaseNotes.txt (1)

1-5: LGTM! Version and dependency updates are consistent.

The changes align with the PR objectives while preserving the documentation of important breaking changes from previous versions.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.Text.Json/PackageReleaseNotes.txt (1)

1-5: LGTM! Version and dependency updates are consistent.

The changes align with the PR objectives while preserving the documentation of important bug fixes from previous versions.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.EFCore/PackageReleaseNotes.txt (1)

1-5: LGTM! Version and dependency updates are consistent.

The changes align with the PR objectives while preserving the documentation of important breaking changes from previous versions.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.Newtonsoft.Json/PackageReleaseNotes.txt (1)

1-5: LGTM! Version and dependency updates are consistent.

The changes align with the PR objectives while preserving the documentation of important breaking changes, particularly the external dependency change from Cuemon to Codebelt.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.SimpleQueueService/PackageReleaseNotes.txt (1)

1-6: LGTM! Version update is consistent with PR objectives.

The version update to 4.0.1 and framework support for .NET 9 and .NET 8 aligns with the project's maintenance goals.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.EFCore/PackageReleaseNotes.txt (1)

1-6: LGTM! Version update is consistent with PR objectives.

The version update to 4.0.1 and framework support for .NET 9 and .NET 8 aligns with the project's maintenance goals.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.EFCore.Domain.EventSourcing/PackageReleaseNotes.txt (1)

1-6: LGTM! Version update is consistent with PR objectives.

The version update to 4.0.1 and framework support for .NET 9 and .NET 8 aligns with the project's maintenance goals.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.docfx/docfx.json (2)

23-23: LGTM! Framework update is consistent.

The TargetFramework update to "net9.0" aligns with the project's move to .NET 9 support.

Also applies to: 56-56


89-89: LGTM! Copyright year update is accurate.

The copyright year has been correctly updated to include 2025.

.nuget/Savvyio.Commands/PackageReleaseNotes.txt (2)

1-6: LGTM! Version update is consistent with PR objectives.

The version update to 4.0.1 and framework support for .NET 9 and .NET 8 aligns with the project's maintenance goals.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)


1-6: Verify package compatibility with .NET 9.

Let's ensure all package references are compatible with .NET 9.

✅ Verification successful

Package and framework compatibility verified for .NET 9

The codebase is properly configured with:

  • Correct target frameworks (net9.0;net8.0)
  • Framework-specific package versions for .NET 9
  • Compatible package versions across all dependencies
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check package references for .NET 9 compatibility

# Find all project files
echo "Checking package references in .csproj files..."
fd -e csproj --exec cat {} \; | grep -A 1 "<PackageReference"

# Check target framework in all project files
echo -e "\nChecking target frameworks..."
fd -e csproj --exec cat {} \; | grep -A 1 "<TargetFramework"

Length of output: 3315


Script:

#!/bin/bash
# Get complete project files content to analyze framework targets and package versions
echo "=== Project Files Analysis ==="
fd -e csproj -x sh -c 'echo "\nFile: {}"; cat "{}"'

Length of output: 50049


Script:

#!/bin/bash
# Check for centralized build and package configuration
echo "=== Checking Directory.Build.props ==="
find . -name "Directory.Build.props" -type f -exec cat {} \;

echo -e "\n=== Checking Directory.Packages.props ==="
find . -name "Directory.Packages.props" -type f -exec cat {} \;

echo -e "\n=== Checking global.json ==="
find . -name "global.json" -type f -exec cat {} \;

Length of output: 7949

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.EventDriven/PackageReleaseNotes.txt (1)

5-5: Consider simplifying the dependency update message.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.EventDriven.Messaging/PackageReleaseNotes.txt (1)

5-5: Consider simplifying the dependency update message.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.SimpleQueueService/PackageReleaseNotes.txt (1)

5-5: Consider simplifying the dependency update message.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection/PackageReleaseNotes.txt (1)

5-5: Consider simplifying the dependency update message.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.DapperExtensions/PackageReleaseNotes.txt (1)

1-5: LGTM! Consider the same wording improvement.

The version update and availability information are correct. For consistency with other packages, consider applying the same wording improvement to the dependency update description.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.DependencyInjection.QueueStorage/PackageReleaseNotes.txt (1)

1-5: LGTM! Consider the same wording improvement.

The version update and availability information are correct. For consistency with other packages, consider applying the same wording improvement to the dependency update description.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.QueueStorage/PackageReleaseNotes.txt (1)

1-5: LGTM! Consider the same wording improvement.

The version update and availability information are correct. For consistency with other packages, consider applying the same wording improvement to the dependency update description.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Extensions.Dapper/PackageReleaseNotes.txt (2)

1-5: LGTM! Consider the same wording improvement.

The version update and availability information are correct. For consistency with other packages, consider applying the same wording improvement to the dependency update description.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)


1-6: Overall package release notes are consistent and well-structured.

The version updates, framework support, and dependency changes are consistently documented across all package release notes. The changes align well with the PR objectives of package maintenance and configuration updates.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.Queries/PackageReleaseNotes.txt (1)

1-5: LGTM! Version update and changelog are consistent.

The version update to 4.0.1 and the changelog entry about dependency updates align with the PR objectives for package maintenance.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Savvyio.App/PackageReleaseNotes.txt (1)

1-29: LGTM! Version update and references are well-documented.

The version update to 4.0.1 and the comprehensive list of references provide clear documentation of package dependencies.

🧰 Tools
🪛 LanguageTool

[duplication] ~5-~5: Possible typo: you repeated a word.
Context: ...ity: .NET 9 and .NET 8   # References - Savvyio - Savvyio.Commands - Savvyio.Commands.Messaging -...

(ENGLISH_WORD_REPEAT_RULE)

.nuget/Savvyio.Core/PackageReleaseNotes.txt (1)

1-5: LGTM! Version update and changelog are consistent.

The version update to 4.0.1 and the changelog entry about dependency updates align with the PR objectives for package maintenance.

🧰 Tools
🪛 LanguageTool

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs   Version: 4.0.0 Availability: .NE...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

README.md Outdated
@@ -30,6 +30,8 @@ All code quality analysis are done by [SonarCloud](https://sonarcloud.io/) and [

![License](https://img.shields.io/github/license/codebeltnet/savvyio) ![Build Status](https://github.com/codebeltnet/savvyio/actions/workflows/pipelines.yml/badge.svg?branch=main) [![codecov](https://codecov.io/gh/codebeltnet/savvyio/graph/badge.svg?token=3U45KRDGK6)](https://codecov.io/gh/codebeltnet/savvyio) [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=savvyio&metric=coverage)](https://sonarcloud.io/dashboard?id=savvyio) [![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.0-4baaaa.svg)](.github/CODE_OF_CONDUCT.md) [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/codebeltnet/savvyio/badge)](https://scorecard.dev/viewer/?uri=github.com/codebeltnet/savvyio)

Full documentation (generated by [DocFx](https://github.com/dotnet/docfx)) located here: https://docs.savvyio.net/
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Remove duplicate documentation link.

This line duplicates the documentation link that already exists in the README. Consider removing this redundant line to maintain clean documentation.

-Full documentation (generated by [DocFx](https://github.com/dotnet/docfx)) located here: https://docs.savvyio.net/
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

33-33: Bare URL used
null

(MD034, no-bare-urls)

Copy link

codecov bot commented Jan 31, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.54%. Comparing base (d943657) to head (e0b6682).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #31   +/-   ##
=======================================
  Coverage   89.54%   89.54%           
=======================================
  Files         158      158           
  Lines        3289     3289           
  Branches      331      331           
=======================================
  Hits         2945     2945           
  Misses        342      342           
  Partials        2        2           

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

@gimlichael gimlichael merged commit 9c093b3 into main Jan 31, 2025
2 of 6 checks passed
@gimlichael gimlichael deleted the v4.0.1/package-maintenance branch January 31, 2025 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant