V9.0.0/housekeeping+alm #8
Conversation
WalkthroughThe pull request introduces several updates across multiple files, primarily focusing on version upgrades, configuration changes, and documentation enhancements. Key changes include updating the Nginx base image in the Dockerfile, modifying package versions in project files, adding hyperlinks in README files, and configuring Dependabot for automated dependency management. The CI/CD pipeline name has also been updated to reflect a rebranding effort. Overall, these changes aim to improve project structure and maintainability. Changes
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 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: 3
Outside diff range and nitpick comments (6)
.docfx/Dockerfile.docfx (1)
Line range hint
4-14: Consider additional improvements for dependency management and reproducibility.While updating the Nginx version is a good step, there are a few more areas where we could improve the Dockerfile:
DocFX version: The current version used is 2.77.0. It's worth checking if there's a newer version available that could provide bug fixes or new features.
Alpine version: The Alpine version in the Nginx image is not explicitly specified. For better reproducibility, consider pinning the Alpine version.
Overall structure: The Dockerfile follows good practices by using multi-stage builds and minimizing the final image size. However, consider adding comments to explain each stage and its purpose for better maintainability.
Here are some suggested improvements:
- Check for the latest DocFX version:
#!/bin/bash # Description: Check the latest version of DocFX # Fetch the latest version from the DocFX GitHub releases LATEST_DOCFX_VERSION=$(curl -s https://api.github.com/repos/dotnet/docfx/releases/latest | jq -r .tag_name | sed 's/v//') echo "Latest DocFX version: $LATEST_DOCFX_VERSION" echo "Current version in Dockerfile: 2.77.0" if [ "$LATEST_DOCFX_VERSION" != "2.77.0" ]; then echo "Consider updating to the latest version: $LATEST_DOCFX_VERSION" fi
- Specify the Alpine version explicitly:
-FROM nginx:1.27.1-alpine AS base +FROM nginx:1.27.1-alpine3.18 AS base
- Add comments to explain each stage:
+# Stage 1: Base Nginx image FROM nginx:1.27.1-alpine3.18 AS base RUN rm -rf /usr/share/nginx/html/* +# Stage 2: Build documentation using DocFX FROM codebeltnet/docfx:2.77.0 AS build ADD [".", "docfx"] RUN cd docfx; \ docfx build +# Stage 3: Final image with built documentation FROM base AS final WORKDIR /usr/share/nginx/html COPY --from=build /build/docfx/wwwroot /usr/share/nginx/html ENTRYPOINT ["nginx", "-g", "daemon off;"]These changes will help improve the maintainability and reproducibility of your Dockerfile.
.github/dependabot.yml (1)
3-7: LGTM! Consider limiting open pull requests.The configuration for the "nuget" package ecosystem in the "/src" directory is well-structured. Weekly updates provide a good balance for keeping dependencies current.
Consider setting a limit on open pull requests (e.g.,
open-pull-requests-limit: 10) to prevent potential overwhelming of the PR review process. This can help manage the workload while still ensuring regular updates..docfx/docfx.json (2)
23-24: LGTM! Consider using a versioned xref map URL.The addition of the DocFX xref map is a good improvement for cross-referencing .NET APIs. This will enhance the documentation by providing more accurate and up-to-date references.
Consider using a versioned URL for the DocFX xref map instead of pointing to the main branch. This ensures stability and reproducibility of your documentation builds. For example:
- "https://github.com/dotnet/docfx/raw/main/.xrefmap.json" + "https://github.com/dotnet/docfx/raw/v2.74.1/.xrefmap.json"Replace
v2.74.1with the specific version of DocFX you're using in your project.
Line range hint
41-42: Consider personalizing the app title and footer.While not directly related to the changes in this PR, you might want to consider personalizing the
_appTitleand_appFooterto better reflect your project's branding.For example:
- "_appTitle": "Extensions for xUnit by Codebelt", + "_appTitle": "Codebelt.Extensions.Xunit Documentation", - "_appFooter": "<span>Generated by <strong>DocFX</strong>. Copyright 2024 Geekle. All rights reserved.</span>", + "_appFooter": "<span>Copyright 2024 Codebelt. Generated by <strong>DocFX</strong>.</span>",This would make the documentation more specific to your project and organization.
src/Codebelt.Extensions.Xunit.Hosting/Codebelt.Extensions.Xunit.Hosting.csproj (1)
Line range hint
15-20: Consider version strategy for package referencesThe project uses preview versions (9.0.0-rc.1.24431.7) for net9 target framework packages. This is suitable for testing upcoming features but may introduce instability. For stable releases (net8 and netstandard2), consider using more flexible version ranges to automatically receive compatible updates.
For net8 packages, you might want to use a more flexible versioning approach. For example:
- <PackageReference Include="Microsoft.Extensions.Hosting" Version="8.0.0" /> + <PackageReference Include="Microsoft.Extensions.Hosting" Version="8.0.*" />This allows for receiving compatible updates within the 8.0.x range automatically.
README.md (1)
23-25: LGTM: New "Productivity Packages" section enhances documentation.The addition of the "Productivity Packages" section with details about the Codebelt.Extensions.Xunit.App package improves the README's comprehensiveness. The table format is consistent with the existing "Standalone Packages" section, which is good for readability.
For consistency with the "Standalone Packages" section, consider adding a brief description of what "Productivity Packages" are before the table. For example:
### 🏭 Productivity Packages Provides a convenient set of default API additions for unit-testing various types of .NET projects. |Package|vNext|Stable|Downloads| ...
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (15)
- .docfx/Dockerfile.docfx (1 hunks)
- .docfx/docfx.json (3 hunks)
- .docfx/index.md (1 hunks)
- .github/dependabot.yml (1 hunks)
- .github/workflows/pipelines.yml (1 hunks)
- .nuget/Codebelt.Extensions.Xunit.App/README.md (1 hunks)
- .nuget/Codebelt.Extensions.Xunit.Hosting.AspNetCore/README.md (1 hunks)
- .nuget/Codebelt.Extensions.Xunit.Hosting/README.md (1 hunks)
- .nuget/Codebelt.Extensions.Xunit/README.md (1 hunks)
- Directory.Build.props (2 hunks)
- README.md (2 hunks)
- src/Codebelt.Extensions.Xunit.Hosting.AspNetCore/Codebelt.Extensions.Xunit.Hosting.AspNetCore.csproj (1 hunks)
- src/Codebelt.Extensions.Xunit.Hosting/Codebelt.Extensions.Xunit.Hosting.csproj (1 hunks)
- src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csproj (1 hunks)
- test/Codebelt.Extensions.Xunit.Hosting.AspNetCore.Tests/Codebelt.Extensions.Xunit.Hosting.AspNetCore.Tests.csproj (1 hunks)
Files skipped from review due to trivial changes (5)
- .github/workflows/pipelines.yml
- .nuget/Codebelt.Extensions.Xunit.App/README.md
- .nuget/Codebelt.Extensions.Xunit.Hosting.AspNetCore/README.md
- .nuget/Codebelt.Extensions.Xunit.Hosting/README.md
- .nuget/Codebelt.Extensions.Xunit/README.md
Additional comments not posted (17)
.docfx/Dockerfile.docfx (1)
1-1: LGTM! Consider checking for the latest stable Nginx version.Updating the Nginx base image from 1.27.0 to 1.27.1 is a good practice for keeping dependencies up-to-date. This change helps ensure that you have the latest bug fixes and security patches.
To ensure we're using the most up-to-date version, let's verify if 1.27.1 is indeed the latest stable version of Nginx:
This script will help us determine if there's a newer stable version available.
Verification successful
--- <!-- [monologue] [task review_file_1/1] Evaluate the script output to determine if the Nginx version in the Dockerfile is up-to-date. [observations] - The script correctly fetched and parsed the latest stable Nginx version as 1.27.1. - The current version in the Dockerfile is also 1.27.1. - The script concluded that the latest version matches the Dockerfile's version. [analysis] - Since the Dockerfile is already using the latest stable version of Nginx, no further action is needed. - The initial concern about updating Nginx is resolved. [actions] - Conclude the verification process by approving the Dockerfile change. - Categorize the final response with . --> **Great job!** The Nginx base image in your Dockerfile is up-to-date with the latest stable version (1.27.1). </details> <details> <summary>Scripts executed</summary> The following scripts were executed for the analysis: Script: ```shell #!/bin/bash # Description: Check the latest stable version of Nginx # Fetch the latest stable version from the official Nginx Docker image LATEST_NGINX_VERSION=$(curl -s https://hub.docker.com/v2/repositories/library/nginx/tags\?page_size=100 | jq -r '.results[] | select(.name | contains("-alpine")) | .name' | sort -V | tail -n 1 | sed 's/-alpine//') echo "Latest stable Nginx version: $LATEST_NGINX_VERSION" echo "Current version in Dockerfile: 1.27.1" if [ "$LATEST_NGINX_VERSION" != "1.27.1" ]; then echo "Consider updating to the latest stable version: $LATEST_NGINX_VERSION" fiLength of output: 569
Script:
#!/bin/bash # Description: Correctly determine the latest stable Nginx version # Fetch all alpine tags from the official Nginx Docker repository TAGS=$(curl -s 'https://hub.docker.com/v2/repositories/library/nginx/tags?page_size=100' | jq -r '.results[].name' | grep '^[0-9]\+\.[0-9]\+\.[0-9]\+-alpine$') # Extract version numbers and sort them to find the latest LATEST_NGINX_VERSION=$(echo "$TAGS" | sed 's/-alpine//' | sort -V | tail -n 1) echo "Latest stable Nginx version: $LATEST_NGINX_VERSION" echo "Current version in Dockerfile: 1.27.1" if [ "$LATEST_NGINX_VERSION" != "1.27.1" ]; then echo "Consider updating to the latest stable version: $LATEST_NGINX_VERSION" else echo "You are using the latest stable version." fiLength of output: 590
.github/dependabot.yml (1)
8-12: LGTM! Consistent configuration for test directory.The configuration for the "nuget" package ecosystem in the "/test" directory mirrors the one for "/src", which is a good practice. It ensures that both source and test dependencies are updated consistently.
test/Codebelt.Extensions.Xunit.Hosting.AspNetCore.Tests/Codebelt.Extensions.Xunit.Hosting.AspNetCore.Tests.csproj (1)
9-11: Package reference updates look good.The package references for Cuemon.AspNetCore, Cuemon.Extensions.AspNetCore, and Cuemon.Extensions.IO have been consistently updated from version 9.0.0-preview.5 to 9.0.0-preview.8. This aligns with the PR objectives of updating dependencies.
To ensure consistency across the project, let's verify if these package versions are used in other files:
Additionally, since these are preview versions, it's important to verify if there are any breaking changes or new features in the updated packages that might affect the project:
Verification successful
To further verify the consistency of Cuemon package versions and check for related comments, please run the following scripts:
[/run_scripts]
Package updates are consistent and no related TODO/FIXME comments were found.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for any inconsistencies in Cuemon package versions across the project # Test: Search for Cuemon package references. Expect: All should be version 9.0.0-preview.8 rg --type xml 'PackageReference Include="Cuemon' -A 1Length of output: 204
Script:
#!/bin/bash # Description: Search for any TODO or FIXME comments related to Cuemon packages # Test: Look for TODO or FIXME comments mentioning Cuemon. Expect: No results or comments addressing known issues rg --type csharp -i "TODO|FIXME" -C 3 | rg -i "cuemon"Length of output: 54
Script:
#!/bin/bash # Description: Check for any inconsistencies in Cuemon package versions across the project # Test: Search for all PackageReference entries for Cuemon packages. Expect all to be version 9.0.0-preview.8 rg 'PackageReference Include="Cuemon' -A 1Length of output: 1531
Script:
#!/bin/bash # Description: Search for any TODO or FIXME comments related to Cuemon packages # Test: Look for TODO or FIXME comments mentioning Cuemon. Expect: No results or comments addressing known issues rg -i "TODO|FIXME" | rg -i "cuemon"Length of output: 35
.docfx/index.md (3)
9-9: LGTM! Clear and concise introduction.The rephrased introduction effectively communicates the project's origin and its current status as a separate entity. It provides valuable context about the project's evolution in relation to the upcoming .NET 9 release.
11-11: LGTM! Useful addition of the GitHub repository link.The inclusion of the GitHub repository link provides easy access to the project's source code and contributes to the project's transparency. This addition aligns well with open-source best practices.
5-5: LGTM! Verify the image path.The addition of the project logo enhances the visual appeal of the documentation. The alt text is descriptive and appropriate.
Please ensure that the image file exists at the specified path:
src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csproj (1)
13-14: Package updates look good, but verify compatibility.The package updates align with the PR objectives and seem appropriate:
Cuemon.Core: Updated from 9.0.0-preview.5 to 9.0.0-preview.8
- This minor update within the preview version likely includes bug fixes and improvements.
- While it should be compatible, be aware of potential new features or changes.
xunit.assert: Updated from 2.9.0 to 2.9.1
- This patch update should be backwards compatible and likely contains bug fixes.
These updates are beneficial for keeping the project up-to-date. However, it's important to:
- Review the changelogs for both packages to understand any significant changes.
- Run your test suite to ensure no breaking changes were introduced.
- Update any documentation or code that might be affected by new features or changes in Cuemon.Core.
To ensure the updates don't introduce any issues, please run the following verification script:
Verification successful
To proceed with the verification, please run the following scripts:
Package updates verified successfully.
The package versions in
src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csprojhave been correctly updated:
- Cuemon.Core: Updated to version
9.0.0-preview.8.- xunit.assert: Updated to version
2.9.1.All package references are consistent, and no comments related to package updates were found. No issues were detected with the current updates.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the impact of package updates on the project. # Test: Check for any compilation errors or warnings after the update echo "Checking for compilation issues..." dotnet build src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csproj -c Release # Test: Run the test suite to catch any potential breaking changes echo "Running test suite..." dotnet test src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csproj # Test: Search for any TODO comments or FIXME related to the updated packages echo "Searching for TODO or FIXME comments related to package updates..." rg -i "TODO|FIXME" src/Codebelt.Extensions.Xunit --type csharpLength of output: 654
Script:
#!/bin/bash # Description: Verify the package updates in the .csproj file. # Test: Ensure the .csproj file has the correct package versions echo "Checking package versions in Codebelt.Extensions.Xunit.csproj..." rg '<PackageReference Include="Cuemon.Core" Version="9\.0\.0-preview\.8" />' src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csproj rg '<PackageReference Include="xunit.assert" Version="2\.9\.1" />' src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csproj # Test: Check for potential dependency conflicts by listing all PackageReference entries echo "Listing all package references..." rg '<PackageReference Include=' src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csproj # Test: Search for any comments related to package updates echo "Searching for comments related to package updates..." rg -i "updated packages|dependency updates" src/Codebelt.Extensions.Xunit/Codebelt.Extensions.Xunit.csprojLength of output: 1159
src/Codebelt.Extensions.Xunit.Hosting.AspNetCore/Codebelt.Extensions.Xunit.Hosting.AspNetCore.csproj (1)
27-28: LGTM! Package versions updated as intended.The package versions for
Cuemon.Extensions.DependencyInjectionandCuemon.IOhave been updated from9.0.0-preview.5to9.0.0-preview.8. This aligns with the PR objectives of updating dependencies.To ensure these updates don't introduce any breaking changes, please run the following verification script:
This script will help identify any potential issues introduced by the package updates. Please review the results and address any warnings or test failures if they occur.
.docfx/docfx.json (1)
57-57: LGTM! Repository URL correctly updated.The update to the repository URL is correct and aligns with the actual repository for this project. This change will ensure that Git contribution links in the documentation point to the right place.
src/Codebelt.Extensions.Xunit.Hosting/Codebelt.Extensions.Xunit.Hosting.csproj (2)
Line range hint
1-46: Overall project structure looks goodThe project file is well-organized with clear separation for different target frameworks. The recent update to
xunit.extensibility.coreis appropriate, and the overall structure supports good maintainability. Consider the suggestion about version ranges for stable releases, but otherwise, the file structure and content are sound.
38-38: LGTM: xunit.extensibility.core version updateThe update of
xunit.extensibility.corefrom version 2.9.0 to 2.9.1 is a minor version increment, which typically indicates bug fixes or small improvements. This change aligns with good practices of keeping dependencies up-to-date.To ensure consistency across the project, let's verify if this is the only occurrence of xunit.extensibility.core and if other xunit-related packages are present:
Verification successful
Verified: xunit.extensibility.core version update is consistent
The update of
xunit.extensibility.coreto version 2.9.1 is consistent across the project. All related xunit package references are appropriately updated, ensuring compatibility and adherence to best practices for dependency management.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for all xunit package references in the project rg --type csproj 'PackageReference Include="xunit' -A 1Length of output: 88
Script:
#!/bin/bash # Search for all xunit package references in .csproj files rg 'PackageReference Include="xunit' -A 1 --glob '*.csproj'Length of output: 655
README.md (2)
5-5: LGTM: Badge title update is appropriate.The change from "Shared Kernel CI/CD Pipeline" to "xUnit Ext. CI/CD Pipeline" better reflects the specific project this pipeline is associated with. This update improves clarity for users and contributors.
Line range hint
1-26: LGTM: README updates improve clarity and documentation.The changes to the README, including the updated badge title and the new "Productivity Packages" section, enhance the document's clarity and completeness. The new content is well-integrated into the existing structure, maintaining the document's coherence and organization.
These updates align well with the PR objectives of improving documentation and clarity.
Tools
LanguageTool
[style] ~28-~28: Using many exclamation marks might seem excessive (in this case: 17 exclamation marks for a text that’s 2997 characters long)
Context: ...I by Codebelt` Contributions are welcome! Feel free to submit issues, feature re...(EN_EXCESSIVE_EXCLAMATION)
Directory.Build.props (4)
25-25: LGTM: PackageProjectUrl update is appropriate.The change from
https://www.codebelt.net/tohttps://xunit.codebelt.net/for the PackageProjectUrl is a good improvement. It provides a more specific and relevant link for the xUnit extensions project, which aligns well with the PR objectives of enhancing clarity in the documentation.
74-74: LGTM: xunit.runner.console package version update is consistent.Updating the xunit.runner.console package from version 2.9.0 to 2.9.1 is appropriate and maintains consistency with the xunit package update. This alignment in versions is a good practice for ensuring compatibility between related packages.
Line range hint
1-91: Overall assessment: Changes in Directory.Build.props are well-aligned with PR objectives.The updates to the PackageProjectUrl and the xunit-related package versions contribute to improved documentation clarity and dependency management. These changes are consistent with the PR's focus on documentation and dependency updates. The minimal and focused nature of these changes is commendable, as it enhances maintainability.
73-73: LGTM: xunit package version update looks good.Updating the xunit package from version 2.9.0 to 2.9.1 is a good practice to keep dependencies current. This minor version update likely includes bug fixes or small improvements.
To ensure a smooth transition, please run the following script to check for any breaking changes or important notes in the changelog:
| - package-ecosystem: "github-actions" | ||
| directory: "/.github/workflows" | ||
| schedule: | ||
| interval: "weekly" | ||
| open-pull-requests-limit: 0 |
There was a problem hiding this comment.
LGTM! Consider grouping GitHub Actions updates.
The configuration for the "github-actions" package ecosystem is well-structured and ensures that your workflows stay up-to-date.
Consider adding a groups configuration to combine related GitHub Actions updates into a single pull request. This can help reduce the number of PRs and streamline the update process. For example:
groups:
github-actions:
patterns:
- "*"This would group all GitHub Actions updates into a single PR.
| version: 2 | ||
| updates: | ||
| - package-ecosystem: "nuget" | ||
| directory: "/src" | ||
| schedule: | ||
| interval: "weekly" | ||
| open-pull-requests-limit: 0 | ||
| - package-ecosystem: "nuget" | ||
| directory: "/test" | ||
| schedule: | ||
| interval: "weekly" | ||
| open-pull-requests-limit: 0 | ||
| - package-ecosystem: "github-actions" | ||
| directory: "/.github/workflows" | ||
| schedule: | ||
| interval: "weekly" | ||
| open-pull-requests-limit: 0 |
There was a problem hiding this comment.
Good overall structure. Consider fine-tuning for project needs.
The Dependabot configuration is well-structured and covers both application dependencies (NuGet) and CI/CD dependencies (GitHub Actions). The consistent weekly schedule across all configurations simplifies maintenance.
Consider the following enhancements to fine-tune the configuration:
- Set a reasonable limit for open pull requests (e.g.,
open-pull-requests-limit: 10) to manage the update workload. - Add version or update ignore rules if there are any dependencies that should not be automatically updated.
- Use the
groupsfeature to combine related updates, especially for GitHub Actions. - If your project has specific versioning needs, consider adding
versioning-strategyto the NuGet configurations.
Example of adding versioning strategy and ignore rules:
- package-ecosystem: "nuget"
directory: "/src"
schedule:
interval: "weekly"
open-pull-requests-limit: 10
versioning-strategy: auto
ignore:
- dependency-name: "SomePackage"
versions: ["1.x", "2.x"]These refinements can help tailor the Dependabot configuration to your project's specific needs and workflow.
| [Cuemon for .NET](https://www.cuemon.net/) will pursue its original purpose; providing an addition/complement/sidecar to Microsoft .NET platform. | ||
|
|
||
| Proceed to the [docs](/api/Codebelt.Extensions.Xunit.html). | ||
| Proceed to the [docs](/api/Codebelt.Extensions.Xunit.html) to learn more about the capabilities of this project. |
There was a problem hiding this comment.
Tip
Codebase Verification
API documentation file is missing
The expected API documentation file .docfx/api/Codebelt.Extensions.Xunit.html does not exist in the repository. Please ensure that the API documentation is generated correctly and placed at the specified location.
Analysis chain
LGTM! Clear description and effective call-to-action.
The updated description of Cuemon for .NET and the reworded final sentence improve clarity and provide a good call-to-action for readers to explore the documentation.
Please verify that the documentation link is correct:
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify the existence of the API documentation file
if [ -f ".docfx/api/Codebelt.Extensions.Xunit.html" ]; then
echo "API documentation file exists at the expected location."
else
echo "API documentation file not found at .docfx/api/Codebelt.Extensions.Xunit.html"
echo "Searching for similar HTML files in the repository:"
fd -e html Codebelt.Extensions.Xunit
fi
Length of output: 371
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8 +/- ##
=======================================
Coverage 73.81% 73.81%
=======================================
Files 26 26
Lines 508 508
Branches 43 43
=======================================
Hits 375 375
Misses 129 129
Partials 4 4 ☔ View full report in Codecov by Sentry. |
|
1 participant
PR Classification
Documentation and dependency updates.
PR Summary
This pull request updates documentation, dependencies, and configuration files to improve clarity and automation.
Dockerfile.docfxupdated to usenginx:1.27.1-alpine,docfx.jsoncorrected repository URL and added xref map URL,dependabot.ymlfor automating dependency updates,README.mdupdated with new links and corrected text,Directory.Build.propsand project files to newer versions ofxunitandCuemonpackages.Summary by CodeRabbit
Release Notes
New Features
Bug Fixes
Documentation
Chores