V9.0.2/package maintenance #112
Conversation
WalkthroughThis pull request updates the release notes for multiple Cuemon packages from version 9.0.1 to 9.0.2. Each package’s notes now include an added availability line (e.g., .NET 9, .NET 8, sometimes with .NET Standard) and a new ALM entry noting dependency updates with respect to TFMs. Additionally, the CHANGELOG and Directory.Packages.props reflect updated dependency versions, the README now uses “scaled trunk” for the branching strategy, and test environment configurations have been updated. Changes
Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
Note 🎁 Summarized by CodeRabbit FreeYour organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (53)
README.md (1)
29-29: Branching Strategy Update: Check Grammar and Clarity
The new statement clearly communicates the transition from the older “git flow” to a “scaled trunk” based strategy. Consider revising “todays DevSecOps practices” to “today’s DevSecOps practices” for grammatical correctness.CHANGELOG.md (1)
9-12: New Changelog Entry for Version [9.0.2]
The added section correctly documents the new release with the date and a brief description, noting that this is a service update focusing on package dependencies. Please verify that this entry fully captures all the updates (e.g., revised dependency versions and updated TFMs if applicable) to ensure consistency with the overall package maintenance objectives..nuget/Cuemon.Core/PackageReleaseNotes.txt (1)
5-5: Consider Simplifying Dependency Note Language
The note “- CHANGED Dependencies to latest and greatest with respect to TFMs” is clear but a bit wordy. Consider a more concise phrasing such as “- Updated dependencies for TFMs” to improve readability.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt (1)
5-5: Refine Dependency Change Note
Similar to the previous file, the phrase “with respect to TFMs” could be simplified. A suggested alternative is “- Updated dependencies 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Net/PackageReleaseNotes.txt (1)
5-5: Improve Dependency Note Clarity
Consider rephrasing “- CHANGED Dependencies to latest and greatest with respect to TFMs” to a more succinct version such as “- Updated dependencies 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt (1)
5-5: Streamline Dependency Update Wording
The current phrasing “- CHANGED Dependencies to latest and greatest with respect to TFMs” can be made more concise. For example, consider “- Updated dependencies 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt (1)
5-5: Simplify Dependency Note
The note “- CHANGED Dependencies to latest and greatest with respect to TFMs” appears in several files. Consider a streamlined version such as “- Updated dependencies for TFMs” to improve clarity and consistency.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt (1)
4-5: Dependency Update Note WordingThe ALM section now includes the dependency update note. Consider refining the phrase “with respect to TFMs” for brevity (for example, “for TFMs”). This is a minor stylistic suggestion.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt (1)
4-5: ALM Section Dependency NoteThe dependency update note is present. As with similar files, consider simplifying “with respect to TFMs” to “for TFMs” to enhance clarity.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt (1)
4-5: Dependency Note Wording SuggestionThe ALM section uses “with respect to TFMs.” For a more concise note, consider rephrasing it as “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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt (1)
4-5: ALM Section Dependency WordingSimilar to the previous files, you might consider rephrasing “with respect to TFMs” to a shorter alternative (e.g., “for TFMs”) to improve readability.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt (1)
4-5: Dependency Note ClarityAs with the other release notes, consider rewording “with respect to TFMs” to a more succinct phrase such as “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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt (1)
4-5: ALM Section – Dependency Update NoteThe ALM section adds the note about dependency updates. To improve clarity, consider simplifying the phrase “with respect to TFMs” to something like “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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt (1)
4-5: ALM Section – Dependency Update NoteThe dependency update entry is clear; however, the wording “with respect to TFMs” is a bit wordy. A more concise phrasing such as “for TFMs” is recommended.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt (1)
4-5: ALM Section – Dependency Update NoteThe note on dependency updates is appropriate. Consider revising “with respect to TFMs” to “for TFMs” to enhance readability.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt (2)
4-5: ALM Section – Dependency Update NoteThe dependency update message is clear. For improved clarity, consider replacing “with respect to TFMs” with a shorter alternative such as “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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
51-52: New Feature Addition – DbTypeExtensionsThe new feature entry for the DbTypeExtensions class is clearly documented. Please ensure that this addition is accompanied by corresponding updates in documentation and tests.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~52-~52: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...e Cuemon.Extensions.Data namespace that consist of extension methods for the DbType enu...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
.nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt (3)
4-5: ALM Section – Dependency Update NoteThe ALM section accurately reflects the dependency update. For clarity, consider shortening “with respect to TFMs” to “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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
23-33: New Feature Addition – PreferredFaultDescriptor EnumThe addition of the PreferredFaultDescriptor enum is a key update. Ensure that related documentation, tests, and migration guides reflect this new feature thoroughly.
35-44: Improvements and EnhancementsThe improvements section lists several enhancements and adjustments (e.g., extending and modifying various classes and methods). Confirm that these changes have corresponding test coverage and documentation updates to support developers during migration.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~40-~40: You might be missing the article “the” here.
Context: ...NET 6 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[style] ~40-~40: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version: 8.1.0 Availability: .NE...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt (2)
1-6: Version & Availability Update Clarity
The new "Version 9.0.2" header and the associated "Availability: .NET 9, .NET 8 and .NET Standard 2.0" line are clearly presented. One minor suggestion is to consider simplifying the phrasing in the ALM section—specifically, replacing “with respect to TFMs” with a shorter alternative (for example, “for TFMs”) to improve readability.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
48-50: TFM Support Note Consistency
The addition of “ADDED TFM for net8.0” is a helpful clarification. However, the subsequent dependency note still uses the wordy “with respect to TFMs.” Consistently streamlining this phrase across the document would enhance clarity.🧰 Tools
🪛 LanguageTool
[style] ~49-~49: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Resilience/PackageReleaseNotes.txt (2)
1-6: Clear Version Update & Availability Declaration
The update to "Version 9.0.2" along with the updated availability so users know the supported frameworks is clear. As with the previous file, consider rephrasing “with respect to TFMs” in the ALM note to avoid unnecessary wordiness.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
48-50: Enhanced TFM Notice
The inclusion of “ADDED TFM for net8.0” improves framework coverage awareness. A brief rewording of the accompanying dependency update note would help keep the language concise and consistent.🧰 Tools
🪛 LanguageTool
[style] ~49-~49: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs # Breaking Changes - REMOVED Ser...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Core.App/PackageReleaseNotes.txt (2)
1-6: Consistent Version & Availability Update
The header update to "Version 9.0.2" and the expanded availability information are well integrated. As in other release notes, consider shortening the phrase “with respect to TFMs” for improved readability.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
46-50: ALM Section Refinements
The removal of support for TFM .NET 6 and the addition of support for TFM .NET Standard 2.0 are clearly communicated. A minor nitpick: revisiting the wording of the dependency update note to be more succinct would ensure uniformity with other release notes.🧰 Tools
🪛 LanguageTool
[style] ~47-~47: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs - REMOVED Support for TFM .NET 6 (...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Threading/PackageReleaseNotes.txt (3)
1-6: Updated Release Note Header
"Version 9.0.2" along with the new availability line is straightforward. The recurring phrase “with respect to TFMs” appears again; streamlining this wording might enhance the overall conciseness of the document.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
20-24: New Features Addition for Async Support
The "New Features" section introduces the AsyncPatterns, AsyncActionFactory, and AsyncFuncFactory classes, which is a strong addition to the Cuemon.Threading namespace. It would be beneficial to include cross-references to detailed documentation or usage examples for these new classes.🧰 Tools
🪛 LanguageTool
[uncategorized] ~22-~22: This expression is usually spelled with a hyphen.
Context: ...ry{TTuple} instances that encapsulate a Task based action delegate with a variable amount ...(BASED_HYPHEN)
53-55: Final ALM and TFM Update
The “ADDED TFM for net8.0” entry is clear; however, the adjacent dependency note again uses a wordy expression. A concise alternative would maintain consistency and clarity across all release notes.🧰 Tools
🪛 LanguageTool
[style] ~54-~54: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data/PackageReleaseNotes.txt (4)
1-6: Version and Availability Are Up-to-Date
Updating to "Version 9.0.2" with expanded availability is clearly communicated. As observed in the other files, consider simplifying “with respect to TFMs” in the ALM section to something more succinct.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
47-50: Improved TFM Support Notification
The entry “ADDED TFM for net8.0” is a useful update. Revising the dependency change note to use a shorter form could improve consistency and reduce redundancy across documents.🧰 Tools
🪛 LanguageTool
[style] ~49-~49: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs # Breaking Changes - REMOVED Dat...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
51-65: Detailed Breaking Changes Overview
The “Breaking Changes” section is extensive and clearly outlines the removals and renames (e.g., DataAdapter, DataCommand → DataStatement). This thorough detailing is excellent for informing developers about potential migration impacts. Providing links or migration guidelines in the future might further ease the transition.
67-79: Bug Fixes, Improvements & New Features Clarity
The subsequent sections for Bug Fixes, Improvements, and New Features are comprehensive and inform about both corrective and enhanced functionalities. Augmenting these entries with links to documentation or detailed release notes could further benefit users, though the current level of detail is sufficient..nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt (1)
5-5: Simplify Dependency Change Note
The phrase “with respect to TFMs” is somewhat wordy. Consider simplifying it to “for TFMs” (or a similar concise alternative) for improved clarity.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt (1)
5-5: Simplify Dependency Change Note
The dependency update note reads “- CHANGED Dependencies to latest and greatest with respect to TFMs”. For clarity and brevity, consider rephrasing it to something like “- Updated dependencies 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Xml/PackageReleaseNotes.txt (1)
5-5: Streamline Dependency Description
Consider revising “with respect to TFMs” to a simpler phrase such as “for TFMs” to improve readability.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt (1)
5-5: Simplify Dependency Change Note
As with the other files, the phrase “with respect to TFMs” could be shortened (for example, “for TFMs”) to enhance clarity and reduce wordiness.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt (1)
5-5: Streamline Dependency Update Note
The dependency update line (“- CHANGED Dependencies to latest and greatest with respect to TFMs”) would benefit from more concise wording. Consider rephrasing it to something like “- Updated dependencies 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt (1)
5-5: Wording Improvement SuggestionThe phrase “with respect to TFMs” appears on this line. Consider shortening it to “for TFMs” to improve clarity and reduce wordiness.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt (1)
5-5: Wording Improvement SuggestionSimilar to other files, consider replacing “with respect to TFMs” with a more concise phrasing like “for TFMs” for improved readability.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt (1)
5-5: Wording Improvement SuggestionAs with similar changes, consider simplifying “with respect to TFMs” to “for TFMs” to streamline the release note text.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt (1)
5-5: Wording Improvement SuggestionAgain, the phrase “with respect to TFMs” could be shortened to “for TFMs” to make the text more concise and easier to read.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt (1)
4-5: ALM Dependency Note – Consider ConcisenessThe ALM section now includes the line:
- CHANGED Dependencies to latest and greatest with respect to TFMsWhile this clearly indicates that dependency updates have been made, the phrase “with respect to TFMs” is somewhat wordy. Consider simplifying it to something like “Dependencies updated for latest TFMs” to improve readability.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt (1)
4-5: ALM Dependency Note – Streamline the MessageThe ALM entry:
- CHANGED Dependencies to latest and greatest with respect to TFMsworks as intended but could be streamlined. A suggestion is to reword it to “Dependencies updated for latest TFMs” for brevity.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.IO/PackageReleaseNotes.txt (1)
4-5: ALM Dependency Update Note – Consider RevisingThe note in the ALM section:
- CHANGED Dependencies to latest and greatest with respect to TFMscould be made more concise. For example, “Dependencies updated for latest TFMs” communicates the update clearly while reducing redundancy.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt (1)
4-5: ALM Dependency Note – Simplify for ClarityThe ALM section retains the recurrent message:
- CHANGED Dependencies to latest and greatest with respect to TFMsIt is recommended to simplify this to “Dependencies updated for latest TFMs” to improve clarity without losing the information.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt (1)
4-5: ALM Dependency Note – Suggest ConcisenessThe ALM section still states:
- CHANGED Dependencies to latest and greatest with respect to TFMsFor enhanced clarity and brevity, consider revising it to “Dependencies updated for latest TFMs”. This minor change can help maintain a consistent tone across all release notes.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt (1)
4-5: Refine Dependency Update Description
The dependency change note currently reads “- CHANGED Dependencies to latest and greatest with respect to TFMs”. Consider rewording this for clarity and conciseness (for example, “- UPDATED dependencies for TFMs to their latest 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt (1)
4-5: Streamline Dependency Note
Similar to the previous file, the dependency update note could be simplified. A suggested alternative is: “- UPDATED dependencies for TFMs to their latest 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt (1)
4-5: Optimize Dependency Update Messaging
As in the other files, consider shortening the phrase “with respect to TFMs.” For example: “- UPDATED dependencies for TFMs to the latest versions.” This will improve readability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt (1)
4-5: Clarify Dependency Change Statement
The dependency update note is somewhat wordy. A concise revision such as “- UPDATED dependencies for TFMs to the latest versions” may be clearer while preserving the intended meaning.🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt (1)
4-5: Refine Dependency Update Wording
The text “- CHANGED Dependencies to latest and greatest with respect to TFMs” appears in several files. For consistency and clarity, consider a more streamlined version such as “- UPDATED dependencies for TFMs to the latest 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt (1)
4-5: Suggestion: Simplify Dependency Update Description
The ALM section currently states:- CHANGED Dependencies to latest and greatest with respect to TFMsConsider a more concise phrasing (e.g., "Dependencies updated for latest TFMs" or "Dependencies updated per TFM requirements") to improve clarity and reduce wordiness.
Proposed Diff:
- - CHANGED Dependencies to latest and greatest with respect to TFMs + - CHANGED Dependencies updated for latest 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (46)
.nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Core.App/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Core/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Data/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.IO/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Net/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Resilience/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Threading/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Xml/PackageReleaseNotes.txt(1 hunks)CHANGELOG.md(1 hunks)Directory.Packages.props(3 hunks)README.md(1 hunks)testenvironments.json(1 hunks)
🧰 Additional context used
🪛 LanguageTool
.nuget/Cuemon.Security.Cryptography/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Resilience/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Hosting/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.SqlClient/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Generic/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.IO/PackageReleaseNotes.txt
[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Net/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Xml/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Data.Integrity/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Threading/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Runtime.Caching/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Data/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Xml/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Threading/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Core.App/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Xml/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.Mvc/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.Authentication/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.App/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.Razor.TagHelpers/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Specialized/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Net/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Authentication/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Diagnostics/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt
[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.Integrity/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Reflection/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Runtime.Caching/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Diagnostics/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Text/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 9.0.1 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
⏰ Context from checks skipped due to timeout of 90000ms (9)
- GitHub Check: 🛠️ Build (Release, netstandard2.1)
- GitHub Check: 🛠️ Build (Debug, netstandard2.1)
- GitHub Check: 🛠️ Build (Debug, net8.0)
- GitHub Check: 🛠️ Build (Release, netstandard2.0)
- GitHub Check: 🛠️ Build (Debug, netstandard2.0)
- GitHub Check: 🛠️ Build (Release, net9.0)
- GitHub Check: 🛠️ Build (Debug, net9.0)
- GitHub Check: 🛠️ Build (Release, net8.0)
- GitHub Check: 🪟 Prepare Windows
🔇 Additional comments (53)
testenvironments.json (2)
7-7: WSL Distribution Update ConfirmedThe WSL-Ubuntu environment’s
wslDistributionhas been updated to "Ubuntu-24.04" as expected. Please verify that this newer distribution version is compatible with your testing processes.
12-12: Docker Image Version Update is ConsistentThe Docker-Ubuntu environment’s
dockerImagehas been updated to "gimlichael/ubuntu-testrunner:net8.0.407-9.0.202", which aligns with the dependency updates and versioning changes outlined in the PR objectives. Confirm that the updated image meets your TFM requirements..nuget/Cuemon.Core/PackageReleaseNotes.txt (1)
1-2: Version Header and Availability Updated
The new header "Version 9.0.2" along with the availability line is correctly updated and clearly reflects the PR objective..nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt (2)
1-2: Version Header Update Confirmed
The update to "Version 9.0.2" and the new availability information are properly implemented as per the requirements.
18-18: Support Removal Documented
The removal note “- REMOVED Support for TFM .NET 6 (LTS)” is clearly stated. Ensure that this change is consistently reflected in any related documentation..nuget/Cuemon.Net/PackageReleaseNotes.txt (2)
1-2: Header Update Validated
The header "Version 9.0.2" and availability information ("Availability: .NET 9, .NET 8 and .NET Standard 2.0") are updated correctly in line with the PR objectives.
18-18: Removal of TFM .NET 6 (LTS) Noted
The removal is clearly communicated. Maintain consistency with similar changes in other package release notes..nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt (2)
1-2: Version and Availability Headers Confirmed
The new version header "Version 9.0.2" and availability information meet the PR requirements.
12-12: Removal of IHostingEnvironment Documented
The removal note “- REMOVED Support for IHostingEnvironment interface (TFM netstandard2.0)” is clear. Verify that any dependent documentation is updated accordingly..nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt (2)
1-2: Version Header Update in Place
The updated header ("Version 9.0.2") and availability line are correctly implemented.
18-18: Support Removal for TFM .NET 6 (LTS) Confirmed
The removal entry (“- REMOVED Support for TFM .NET 6 (LTS)”) is clearly written. Ensure that this update is reflected consistently across related packages..nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update VerifiedThe version has been correctly updated to 9.0.2, and the availability line now reflects support for .NET 9, .NET 8, and .NET Standard 2.0.
.nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt (2)
1-2: Version and Availability Update VerifiedThe version and availability information are correctly updated to 9.0.2 with support for .NET 9, .NET 8, and .NET Standard 2.0.
16-18: TFM Support Removal NoticeThe note regarding the removal of support for TFM .NET 6 (LTS) is clear. Please verify that this change aligns with your overall product support policy.
🧰 Tools
🪛 LanguageTool
[style] ~17-~17: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs - REMOVED Support for TFM .NET 6 (...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt (1)
1-2: Correct Version and Availability UpdateThe file correctly reflects the version update to 9.0.2 along with the revised availability details.
.nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt (2)
1-2: Version and Availability Update ConfirmedThe release note header is updated correctly to version 9.0.2 with the current availability information.
16-18: TFM Removal Notice VerificationThe removal of support for TFM .NET 6 (LTS) is clearly documented. Please confirm that this modification is consistent with your broader TFM support strategy.
🧰 Tools
🪛 LanguageTool
[style] ~17-~17: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs - REMOVED Support for TFM .NET 6 (...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt (3)
1-2: Version and Availability Update ConfirmedThe version update to 9.0.2 and the inclusion of availability for .NET 9, .NET 8, and .NET Standard 2.0 are correctly reflected.
16-19: Additional TFM Support ChangesThe ALM section now documents the removal of support for TFM .NET 6 (LTS) and the addition of support for TFM .NET Standard 2.0. Please ensure these changes are consistent with the product’s supported frameworks.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~17-~17: You might be missing the article “the” here.
Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs - REM...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[style] ~17-~17: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs - REMOVED Support for TFM .NET 6 (...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
21-31: Content Consistency CheckThe subsequent sections (New Features, Improvements, and Bug Fixes) seem comprehensive. It would be good to double-check that these details remain accurate and relevant following the version update.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~25-~25: A punctuation mark might be missing here.
Context: ...Converter, RemoveAllOf and RemoveAllOf{T} - EXTENDED JsonSerializerOptionsExtensions...(AI_EN_LECTOR_MISSING_PUNCTUATION)
.nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt (1)
1-2: Version and Availability UpdateThe header now correctly indicates Version 9.0.2 and shows the updated availability information (.NET 9, .NET 8 and .NET Standard 2.0). This aligns with the overall PR objective.
.nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt (1)
1-2: Version and Availability UpdateThe release note header properly upgrades the version to 9.0.2 and includes the updated availability (.NET 9, .NET 8 and .NET Standard 2.0). This looks consistent with the intended changes.
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt (1)
1-2: Version and Availability UpdateThe updated header correctly reflects Version 9.0.2 with the accompanying availability details (.NET 9 and .NET 8). This matches the PR objectives well.
.nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt (1)
1-2: Version and Availability UpdateThe release notes now correctly update to Version 9.0.2 with the availability details (.NET 9, .NET 8 and .NET Standard 2.0) as required.
.nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt (2)
1-2: Version and Availability UpdateThe header correctly updates the package to Version 9.0.2 and shows the updated availability (.NET 9 and .NET 8), complying with the updated release information.
20-22: Breaking Changes NotificationThe removal of the BadRequestMessage property from the ApiKeySentinelOptions class is clearly noted. Please verify that any dependent code is updated accordingly to prevent integration issues.
.nuget/Cuemon.Resilience/PackageReleaseNotes.txt (1)
51-57: Comprehensive Breaking Changes & Improvements Section
The newly added “Breaking Changes” and “Improvements” sections provide valuable context—especially noting the removal of SerializableAttribute/ISerializable implementations with a relevant external link. This level of detail is very useful for consumers of the package..nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update Verified
The updated version ("Version 9.0.2") and the availability information (".NET 9, .NET 8 and .NET Standard 2.0") are correctly reflected at the top of the release notes..nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update Verified
The release notes correctly update the version to "9.0.2" and list the availability (".NET 9 and .NET 8") as expected..nuget/Cuemon.Xml/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update Verified
The top lines correctly reflect the update to "Version 9.0.2" and confirm availability for “.NET 9, .NET 8 and .NET Standard 2.0”..nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update Verified
The new version ("Version 9.0.2") along with the availability info (".NET 9 and .NET 8") is correctly updated at the top of the document..nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update Verified
The file properly updates the version to "9.0.2" and the availability details (".NET 9, .NET 8 and .NET Standard 2.0") are correct..nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt (1)
1-2: Version and Availability UpdateThe release notes now begin with "Version 9.0.2" and note “Availability: .NET 9 and .NET 8,” which aligns perfectly with the PR objectives for a consistent version bump and framework support update.
.nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt (1)
1-2: Version and Availability UpdateThe update to "Version 9.0.2" along with the availability line “.NET 9 and .NET 8” is clear and consistent with the overall package maintenance effort.
.nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt (1)
1-2: New Release Note HeadingThe heading now correctly reflects Version 9.0.2 and clearly specifies availability for .NET 9 and .NET 8. This update is transparent and meets the PR objectives.
.nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt (1)
1-2: Enhanced Availability InformationThe updated release notes now state "Version 9.0.2" and an availability line that includes “.NET 9, .NET 8 and .NET Standard 2.0.” This additional framework support detail is a valuable clarification and aligns with the update goals.
.nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update ConfirmedThe release notes are correctly updated to “Version 9.0.2” and now list “Availability: .NET 9 and .NET 8”. This aligns with the PR objective and ensures consistency among the packages.
.nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt (1)
1-2: Version and Availability UpdateThe update to “Version 9.0.2” along with the revised availability “.NET 9, .NET 8 and .NET Standard 2.0” is clear and consistent with the intended support changes.
.nuget/Cuemon.IO/PackageReleaseNotes.txt (1)
1-2: Version and Expanded Availability ConfirmedThe version has been updated to “Version 9.0.2” and the availability now explicitly includes “.NET 9, .NET 8, .NET Standard 2.1 and .NET Standard 2.0,” which correctly reflects the extended support intended for this package.
.nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt (2)
1-2: Version and Availability UpdateThe file now reflects “Version 9.0.2” and the availability “.NET 9 and .NET 8” correctly. The updates are straightforward and meet the PR objectives.
16-18: Removal of .NET 6 Support VerifiedThe entry:
- REMOVED Support for TFM .NET 6 (LTS)clearly communicates that .NET 6 support has been dropped. Please ensure that this change is properly documented in all related areas (e.g., build configurations and documentation).
🧰 Tools
🪛 LanguageTool
[style] ~17-~17: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs - REMOVED Support for TFM .NET 6 (...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt (1)
1-2: Version and Availability UpdateThe version update to “Version 9.0.2” and the availability “.NET 9, .NET 8 and .NET Standard 2.0” are correctly applied and in line with the overall package maintenance improvements.
.nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt (1)
1-2: Release Note Header Update
The new release entry correctly updates the package version to 9.0.2 and revises the availability to “.NET 9, .NET 8 and .NET Standard 2.0”. Please double-check if the leading BOM (Byte Order Mark) in line 1 is intentional..nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt (1)
1-2: Release Note Header Update
The version header now reflects Version 9.0.2 with updated availability “.NET 9, .NET 8 and .NET Standard 2.0”, which is in line with the PR objectives. Verify that the BOM present in line 1 is expected..nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt (1)
1-2: Update with Expanded Availability Info
The release header correctly updates the version to 9.0.2 and extends the availability information to “.NET 9, .NET 8, .NET Standard 2.1 and .NET Standard 2.0”. This added detail is helpful for consumers of the package..nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt (1)
1-2: Release Note Update
The header now properly reflects Version 9.0.2 with availability “.NET 9 and .NET 8”. This meets the PR objectives for updating the release notes..nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update Confirmed
The release notes now indicate Version 9.0.2 along with “Availability: .NET 9 and .NET 8”, which is consistent with the package maintenance objectives..nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt (1)
1-6: Version update looks good.The addition of version 9.0.2 with appropriate availability information and dependency update notes follows the established pattern in the release notes. This update aligns perfectly with the PR objectives of maintaining package 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt (1)
1-6: Version update correctly includes .NET Standard 2.0 support.The version 9.0.2 update properly maintains .NET Standard 2.0 compatibility, which is important for this particular package. The dependency update note is consistent with other packages in the PR.
🧰 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 9.0.1 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
Directory.Packages.props (3)
13-14: Testing dependency updates look appropriate.The updated versions for Microsoft.NET.Test.Sdk, Microsoft.TestPlatform.ObjectModel, and xunit.runner.visualstudio reflect minor version increments that should maintain compatibility while providing the latest fixes.
Also applies to: 23-23
26-26: Framework-specific dependency updates are well-organized.The updates to Microsoft.Data.Sqlite (for both net4 and net8/netstandard2) and System.Threading.Tasks.Extensions are appropriately segregated by target framework, following good package management practices.
Also applies to: 35-35, 38-38
46-51: Net9 package updates maintain version consistency.All .NET 9 specific packages have been properly updated from 9.0.1 to 9.0.2, maintaining version alignment with the overall package version. This ensures consistency across the ecosystem.
.nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt (1)
1-2: Version and Availability Update Verified
The new release entry clearly indicates version 9.0.2 along with the updated availability information for .NET 9 and .NET 8. This aligns perfectly with the PR objectives.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #112 +/- ##
=======================================
Coverage 80.12% 80.12%
=======================================
Files 593 593
Lines 18312 18312
Branches 1883 1883
=======================================
Hits 14672 14672
Misses 3572 3572
Partials 68 68 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
This pull request includes updates to the package release notes for multiple projects within the
.nugetdirectory. The changes primarily focus on updating the version number and availability information, as well as updating dependencies to their latest versions.Key changes include:
Version Updates and Availability
Dependency Updates
Summary by CodeRabbit
Chores
Documentation