V9.0.8/service pack #125

gimlichael · 2025-08-06T20:17:49Z

This pull request updates the release notes for multiple NuGet packages to version 9.0.8. The primary change is the upgrade of dependencies to their latest versions, ensuring compatibility with the newest .NET Target Frameworks (TFMs). The updates apply across a wide range of packages, both for ASP.NET Core and core libraries.

Release note updates:

All affected .nuget/*/PackageReleaseNotes.txt files: Updated the version to 9.0.8 and clarified availability for .NET 9, .NET 8, and .NET Standard 2.0 where applicable. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19]

Dependency management:

All updated packages: Noted in release notes that dependencies have been changed to the latest versions, with respect to the supported TFMs. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19]

Summary by CodeRabbit

Chores
- Updated package dependencies to their latest versions across all packages, including support for .NET 9 and .NET 8.
- Refreshed Docker test environment image for improved compatibility.
- Updated changelog to reflect the new service update (version 9.0.8).
- Incremented various test and runtime package versions to ensure up-to-date builds and testing environments.

coderabbitai · 2025-08-06T20:17:58Z

Walkthrough

This change updates package release notes for multiple Cuemon libraries to version 9.0.8, reflecting dependency updates for .NET 9, .NET 8, and .NET Standard 2.0/2.1 where applicable. It also updates test environment Docker tags, dependency versions in Directory.Packages.props, and adds a corresponding changelog entry.

Changes

Cohort / File(s)	Change Summary
Release Notes Updates (.NET 9/8/Standard) `.nuget/*/PackageReleaseNotes.txt`	Add version 9.0.8 entries specifying updated dependencies for .NET 9, .NET 8, and .NET Standard.
Central Dependency Version Management `Directory.Packages.props`	Update package versions for Codebelt.Extensions.Xunit, xunit.runner.visualstudio, Microsoft.*.
Test Environment Update `testenvironments.json`	Update Docker-Ubuntu image tag for test runner environment.
Changelog `CHANGELOG.md`	Add changelog entry for version 9.0.8, noting dependency-focused service update.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

V9.0.3/package maintenance #113: Updates release notes and dependencies from 9.0.2 to 9.0.3, similar maintenance pattern as this PR.
⬆️ bump dependencies #122: Prior dependency and version bumps, including Directory.Packages.props and environment updates, part of ongoing version maintenance.
V9.0.2/package maintenance #112: Previous release notes and dependency updates for 9.0.2, related to metadata and dependency maintenance.

Poem

A hop, a skip, a version bump,
Dependencies fresh, no code to dump.
Release notes grow, the changelog sings,
Docker tags and packages sprout new wings.
🐇 With every tidy, careful sweep,
The garden of code stays clean and neat!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch v9.0.8/service-pack

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai generate unit tests to generate unit tests for this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 1

♻️ Duplicate comments (22)

.nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt (1)

4-5: Consistent, concise wording for dependency note
Same wording issue as noted in the Text.Json package. Recommend the shorter, neutral wording for consistency across all release-note files.

.nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt (1)

4-5: Adopt the neutral phrasing for dependency updates
See earlier comment; suggest replacing the marketing phrasing with the concise wording for consistency.

.nuget/Cuemon.Net/PackageReleaseNotes.txt (1)

4-5: Align wording with other packages
Replace “latest and greatest with respect to TFMs” with the neutral variant proposed earlier to keep the release notes professional and uniform.

.nuget/Cuemon.Xml/PackageReleaseNotes.txt (1)

4-5: Apply the concise dependency-update wording
As with the other release-note files, recommend adopting the neutral phrasing for this bullet.

.nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt (2)

1-1: Duplicate: remove leading BOM/ZWNBSP – same issue as noted in Cuemon.Threading notes.

5-5: Duplicate: streamline ALM wording – apply the same tightened wording suggested earlier.

.nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt (2)

1-1: Duplicate: remove leading BOM/ZWNBSP.

5-5: Duplicate: streamline ALM wording – adopt the concise wording previously suggested.

.nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt (2)

1-1: Duplicate: remove leading BOM/ZWNBSP.

5-5: Duplicate: streamline ALM wording – adopt the concise wording previously suggested.

.nuget/Cuemon.Core.App/PackageReleaseNotes.txt (2)

1-1: Duplicate: remove leading BOM/ZWNBSP.

5-5: Duplicate: streamline ALM wording – adopt the concise wording previously suggested.

.nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt (1)

4-5: Same wording issue as noted in Cuemon.Data.Integrity

Apply the tightened phrasing suggested earlier for consistency across all packages.

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

4-5: Same wording issue as noted in Cuemon.Data.Integrity

Apply the tightened phrasing suggested earlier for consistency across all packages.

.nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt (1)

4-5: Same wording issue as noted in Cuemon.Data.Integrity

Apply the tightened phrasing suggested earlier for consistency across all packages.

.nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt (1)

4-5: Same wording issue as noted in Cuemon.Data.Integrity

Apply the tightened phrasing suggested earlier for consistency across all packages.

.nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt (1)

4-5: Same wording improvement applies

Please apply the wording change suggested for the Cryptography package here as well to keep release notes consistent.

.nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt (1)

4-5: Same wording improvement applies

See earlier comment regarding “latest and greatest … with respect to TFMs”.

.nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt (1)

4-5: Same wording improvement applies

Refer to the first file’s suggestion for tightening the release-note wording.

.nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt (1)

4-5: Same wording improvement applies

Apply the concise wording update noted for the Cryptography package to maintain uniformity across all package release notes.

.nuget/Cuemon.IO/PackageReleaseNotes.txt (1)

4-5: See previous comment – same wording issue.
The same edit applies here.

.nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt (1)

4-5: See previous comment – same wording issue.
The same edit applies here.

🧹 Nitpick comments (26)

CHANGELOG.md (1)

9-11: Ensure Changelog section structure consistency

Earlier entries (e.g., 9.0.7, 9.0.6) keep the “### Changed / Added / Fixed …” sub-sections to stay compliant with the “Keep a Changelog” format.
Consider adding at least a ### Changed section – even if it only contains “Dependencies updated to latest versions across all packages” – to avoid breaking downstream tooling that parses those headings.
Also remember to append the reference link for [9.0.8] at the bottom of the file if you maintain compare-links.
.nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt (1)
1-6: Tone & clarity improvement for release notes

The informal phrase “latest and greatest” and the wordy “with respect to” can be replaced with concise, professional wording.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - CHANGED Dependencies to latest versions for all supported TFMs
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt (1)
1-6: Align wording with other documentation

Same wording issue as in the previous file; consider adopting a crisper sentence for consistency across all release notes.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - CHANGED Dependencies to latest versions for all supported TFMs
.nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt (1)
1-6: Refine phrasing for professionalism

Recommend tightening the language as shown below.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - CHANGED Dependencies to latest versions for all supported TFMs
.nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt (1)
1-6: Consistent, concise wording

Apply the same phrasing adjustment for uniformity.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - CHANGED Dependencies to latest versions for all supported TFMs
.nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt (1)
4-5: Tone down marketing wording and tighten phrasing
The phrase “latest and greatest with respect to TFMs” is slightly marketing-ish and wordy for technical release notes. Consider something more concise and neutral, e.g.:
- CHANGED Dependencies to latest and greatest with respect to TFMs
+ CHANGED Updated dependencies to the latest stable versions aligned with supported TFMs
.nuget/Cuemon.Threading/PackageReleaseNotes.txt (2)
1-1: Remove stray BOM/ZWNBSP character at beginning of file

The Unicode FEFF (zero-width no-break space) before “Version” can cause diff noise and tooling issues. Delete it so the file starts with a plain ASCII “V”.

5-5: Tone & brevity – tighten the ALM bullet

“latest and greatest with respect to TFMs” is informal and wordy. Consider something like:
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest versions across supported TFMs
This keeps the release note concise and professional.
.nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt (1)
4-5: Replace colloquial wording in ALM bullet

The phrase “latest and greatest with respect to TFMs” is informal and slightly wordy for release-note copy. Consider tightening the language.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest versions across supported TFMs
.nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt (1)
4-5: Prefer concise, neutral wording for release-note entries

Trim the informal “latest and greatest … with respect to” phrasing to something more business-like:
- CHANGED Dependencies to latest and greatest with respect to TFMs
+ CHANGED Updated dependencies to the latest versions aligned with supported TFMs
.nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt (1)
5-5: Re-phrase bullet for professional tone and brevity

“latest and greatest with respect to TFMs” is marketing-style and verbose. Prefer a concise, neutral wording:
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest compatible versions for the supported TFMs
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt (1)
5-5: Tighten wording of the ALM entry

Same comment as for other packages – consider the more formal phrasing below for consistency across release notes:
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest compatible versions for the supported TFMs
.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt (1)
5-5: Use consistent, neutral language

Replace informal/wordy bullet with a concise statement:
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest compatible versions for the supported TFMs
.nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt (1)
5-5: Align wording with other release-note entries

Recommend the following adjustment:
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest compatible versions for the supported TFMs
.nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt (1)
5-5: Minor wording improvement

Apply the streamlined phrasing for clarity and consistency:
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest compatible versions for the supported TFMs
.nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt (1)
5-5: Tone & conciseness of change description can be improved

“latest and greatest with respect to TFMs” sounds informal and slightly wordy for release notes. A crisper, more professional phrasing keeps the notes concise.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest versions for supported TFMs
.nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt (1)
5-5: Use a shorter, more professional wording

Same wording nit as in other packages.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest versions for supported TFMs
.nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt (1)
5-5: Release-note phrasing nit

Recommend trimming “latest and greatest with respect to TFMs” for a more neutral, compact sentence.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest versions for supported TFMs
.nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt (1)
5-5: Consistent, concise wording

Suggest aligning with a crisper wording used elsewhere.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest versions for supported TFMs
.nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt (1)
5-5: Minor wording refinement

The informal phrase “latest and greatest” can be replaced by a straightforward “latest”.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - UPDATED dependencies to the latest versions for supported TFMs
.nuget/Cuemon.Resilience/PackageReleaseNotes.txt (1)
1-6: Tighten wording and drop the BOM marker

The invisible BOM character (U+FEFF) at the beginning of the file can cause diff noise and encoding issues in some tools. Save the file as UTF-8 without BOM.

The phrase “latest and greatest with respect to TFMs” is a bit chatty/wordy for formal release notes. Consider something shorter and more neutral, e.g. “Updated dependencies to the latest compatible versions for all supported TFMs”.
-Version 9.0.8
+Version 9.0.8
 …
-# ALM
-- CHANGED Dependencies to latest and greatest with respect to TFMs
+# ALM
+- CHANGED Updated dependencies to the latest compatible versions for all supported TFMs
.nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt (1)
1-6: Polish phrasing and remove BOM

Same two minor issues as in the previous file:

Remove the leading BOM (U+FEFF).

Replace “latest and greatest with respect to TFMs” with a crisper sentence.
-Version 9.0.8
+Version 9.0.8
 …
-# ALM
-- CHANGED Dependencies to latest and greatest with respect to TFMs
+# ALM
+- CHANGED Updated dependencies to the latest compatible versions for all supported TFMs
.nuget/Cuemon.Data/PackageReleaseNotes.txt (1)
1-6: Consistent, concise wording & BOM removal

Repeat of the earlier nitpicks:
-Version 9.0.8
+Version 9.0.8
 …
-# ALM
-- CHANGED Dependencies to latest and greatest with respect to TFMs
+# ALM
+- CHANGED Updated dependencies to the latest compatible versions for all supported TFMs
This keeps phrasing consistent across packages and removes the superfluous BOM.
.nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt (1)
1-6: Minor editorial clean-up

Apply the same BOM removal and wording tweak as for the other release-note files:
-Version 9.0.8
+Version 9.0.8
 …
-# ALM
-- CHANGED Dependencies to latest and greatest with respect to TFMs
+# ALM
+- CHANGED Updated dependencies to the latest compatible versions for all supported TFMs
.nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt (1)
1-6: Standardise language and strip BOM

For uniformity with the other package notes:
-Version 9.0.8
+Version 9.0.8
 …
-# ALM
-- CHANGED Dependencies to latest and greatest with respect to TFMs
+# ALM
+- CHANGED Updated dependencies to the latest compatible versions for all supported TFMs
This also removes the leading BOM character.
.nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt (1)
4-5: Tone/clarity: replace informal & wordy phrasing.

“latest and greatest with respect to TFMs” is (a) informal and (b) wordy.
A crisper, professional alternative improves readability and keeps the style consistent with many OSS projects.
- - CHANGED Dependencies to latest and greatest with respect to TFMs
+ - CHANGED Dependencies updated to the latest compatible versions for all supported TFMs

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9341198 and c804536.

📒 Files selected for processing (45)

.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)
testenvironments.json (1 hunks)

🧰 Additional context used

🪛 LanguageTool

.nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt