Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

V9.0.1/package maintenance #9

Merged
merged 5 commits into from
Jan 30, 2025
Merged

V9.0.1/package maintenance #9

merged 5 commits into from
Jan 30, 2025

Conversation

gimlichael
Copy link
Member

@gimlichael gimlichael commented Jan 30, 2025

This pull request includes several updates across various files to upgrade dependencies, update version numbers, and make minor improvements. The most important changes include updating Docker images and target frameworks, modifying package release notes, and updating package versions.

Dependency and version updates:

Release notes and documentation:

Other improvements:

  • LICENSE: Updated the copyright year to include 2025.
  • README.md: Added a link to the full documentation generated by DocFx.
  • testenvironments.json: Updated the Docker image for the Docker-Ubuntu test environment.

Summary by CodeRabbit

Release Notes v9.0.1

  • Package Updates

    • Updated multiple packages to version 9.0.1
    • Added support for .NET 9 and .NET 8
    • Removed support for .NET 6
  • Documentation

    • Updated copyright year to 2024-2025
    • Added link to full documentation in README
    • Updated DocFx configuration
  • Infrastructure

    • Updated Docker image for test environments
    • Removed GitHub SourceLink package reference
  • Maintenance

    • Minor version increment and dependency management

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

coderabbitai bot commented Jan 30, 2025

Walkthrough

This pull request represents a comprehensive update across multiple project files, focusing on version increments, dependency updates, and minor configuration changes. The modifications span from updating the Nginx base image in the Dockerfile to incrementing package versions, updating copyright years, and adjusting test environment configurations. The changes primarily target .NET 9 and .NET 8 compatibility, with a service update approach that includes package dependency refinements and minor improvements.

Changes

File Change Summary
.docfx/Dockerfile.docfx Updated Nginx base image from 1.27.0-alpine to 1.27.3-alpine
.docfx/docfx.json Updated .NET target framework from net8.0 to net9.0, extended copyright year to 2024-2025
.nuget/*/PackageReleaseNotes.txt Version incremented from 9.0.0 to 9.0.1 across multiple packages, updated .NET version support
CHANGELOG.md Added new version entry for 9.0.1 dated January 30, 2025
Directory.Build.props Removed Microsoft.SourceLink.GitHub package reference
Directory.Packages.props Updated multiple package versions, including test and dependency packages
LICENSE Updated copyright year from 2024 to 2024-2025
README.md Added link to full DocFx documentation
testenvironments.json Updated Docker image version for Ubuntu test runner

Possibly related PRs

Poem

🐰 Hop, hop, version update time!
Packages dancing in perfect rhyme
Nginx, .NET, and JSON so bright
Dependencies aligned just right
A rabbit's code release delight! 🚀


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1ebc13c and d76dbf5.

📒 Files selected for processing (1)
  • Directory.Build.props (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • Directory.Build.props
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: 🧪 Test (windows-2022, Release)
  • GitHub Check: 📦 Pack (Release)
  • GitHub Check: 🧪 Test (windows-2022, Debug)
  • GitHub Check: 🧪 Test (ubuntu-22.04, Release)
  • GitHub Check: 🧪 Test (ubuntu-22.04, Debug)
  • GitHub Check: 📦 Pack (Debug)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

CodeRabbit Configuration File (.coderabbit.yaml)

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

Documentation and Community

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (6)
.nuget/Codebelt.Extensions.Newtonsoft.Json.App/PackageReleaseNotes.txt (1)

4-5: Enhance ALM section clarity and documentation.

Consider these improvements:

  1. Add "the" before "latest"
  2. Use more concise phrasing
  3. List the specific dependencies that were updated
 # ALM
-CHANGED Dependencies to latest and greatest with respect to TFMs
+CHANGED Dependencies to the latest versions for supported TFMs
+- Updated <list specific dependencies and their versions>
🧰 Tools
🪛 LanguageTool

[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ... 8
 

ALM

  • CHANGED Dependencies to latest and greatest with respect to TFMs
     
    V...

(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.0
Availability: ....

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

README.md (1)

9-10: Consider wrapping the URL in angle brackets.

The documentation link is a great addition! However, to comply with markdown best practices and resolve the markdownlint warning, consider wrapping the bare URL in angle brackets.

Apply this diff to fix the bare URL issue:

-Full documentation (generated by [DocFx](https://github.com/dotnet/docfx)) located here: https://newtonsoft.codebelt.net/
+Full documentation (generated by [DocFx](https://github.com/dotnet/docfx)) located here: <https://newtonsoft.codebelt.net/>
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

9-9: Bare URL used
null

(MD034, no-bare-urls)

.nuget/Codebelt.Extensions.AspNetCore.Newtonsoft.Json/PackageReleaseNotes.txt (1)

4-5: Consider adding specific dependency version changes.

The current note "CHANGED Dependencies to latest and greatest with respect to TFMs" could be more specific by listing the actual version changes.

Consider this format instead:

-CHANGED Dependencies to latest and greatest with respect to TFMs
+CHANGED Dependencies:
+  - Microsoft.AspNetCore.Mvc.NewtonsoftJson from 9.0.0 to 9.0.1 (net9)
+  - Microsoft.AspNetCore.Mvc.NewtonsoftJson from 8.0.10 to 8.0.12 (net8)
🧰 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.0
Availability: ....

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Codebelt.Extensions.AspNetCore.Mvc.Formatters.Newtonsoft.Json/PackageReleaseNotes.txt (1)

1-6: Consider documenting migration steps for breaking changes.

Version 9.0.1 follows significant breaking changes from 9.0.0, including the removal of HttpExceptionDescriptorResponseHandlerExtensions and namespace changes. Consider adding migration guidance for users updating from pre-9.0.0 versions.

Add a "Migration Guide" section:

# ALM
- CHANGED Dependencies to latest and greatest with respect to TFMs

+# Migration Guide
+For users upgrading from versions before 9.0.0:
+1. Replace `AddNewtonsoftJsonResponseHandler` calls with `AddNewtonsoftJsonExceptionResponseFormatter`
+2. Update namespace references from `Codebelt.Extensions.AspNetCore.Mvc.Formatters.Newtonsoft.Json.Converters` to `Codebelt.Extensions.AspNetCore.Newtonsoft.Json.Converters`
🧰 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.0
Availability: ....

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

CHANGELOG.md (1)

10-12: LGTM! Consider adding more specific details about dependency updates.

The changelog entry follows the proper format and clearly indicates this is a service update. However, it could be more helpful to list the specific package versions that were updated.

Consider expanding the entry to include specific dependency updates, for example:

 ## [9.0.1] - 2025-01-30
 
-This is a service update that primarily focuses on package dependencies and minor improvements.
+This is a service update that primarily focuses on package dependencies and minor improvements:
+
+### Dependencies
+- Updated nginx from 1.27.0-alpine to 1.27.3-alpine
+- Updated target framework from net8.0 to net9.0
.nuget/Codebelt.Extensions.Newtonsoft.Json/PackageReleaseNotes.txt (1)

4-5: Consider simplifying the ALM section wording.

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

Consider this alternative:

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

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

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between af320d2 and 1ebc13c.

📒 Files selected for processing (12)
  • .docfx/Dockerfile.docfx (1 hunks)
  • .docfx/docfx.json (2 hunks)
  • .nuget/Codebelt.Extensions.AspNetCore.Mvc.Formatters.Newtonsoft.Json/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Codebelt.Extensions.AspNetCore.Newtonsoft.Json/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Codebelt.Extensions.Newtonsoft.Json.App/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Codebelt.Extensions.Newtonsoft.Json/PackageReleaseNotes.txt (1 hunks)
  • CHANGELOG.md (1 hunks)
  • Directory.Build.props (0 hunks)
  • Directory.Packages.props (1 hunks)
  • LICENSE (1 hunks)
  • README.md (1 hunks)
  • testenvironments.json (1 hunks)
💤 Files with no reviewable changes (1)
  • Directory.Build.props
✅ Files skipped from review due to trivial changes (3)
  • LICENSE
  • .docfx/Dockerfile.docfx
  • testenvironments.json
🧰 Additional context used
🪛 LanguageTool
.nuget/Codebelt.Extensions.AspNetCore.Newtonsoft.Json/PackageReleaseNotes.txt

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

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Codebelt.Extensions.Newtonsoft.Json.App/PackageReleaseNotes.txt

[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ... 8
 

ALM

  • CHANGED Dependencies to latest and greatest with respect to TFMs
     
    V...

(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.0
Availability: ....

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Codebelt.Extensions.AspNetCore.Mvc.Formatters.Newtonsoft.Json/PackageReleaseNotes.txt

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

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

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

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

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

🪛 markdownlint-cli2 (0.17.2)
README.md

9-9: Bare URL used
null

(MD034, no-bare-urls)

⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: 🧪 Test (windows-2022, Release)
  • GitHub Check: 🧪 Test (windows-2022, Debug)
  • GitHub Check: 🧪 Test (ubuntu-22.04, Release)
  • GitHub Check: 📦 Pack (Release)
  • GitHub Check: 🧪 Test (ubuntu-22.04, Debug)
  • GitHub Check: 📦 Pack (Debug)
🔇 Additional comments (7)
.nuget/Codebelt.Extensions.Newtonsoft.Json.App/PackageReleaseNotes.txt (1)

1-2: LGTM! Version and availability are clearly documented.

The version increment and framework support are well-documented and align with the PR objectives.

README.md (1)

9-10: Verify the documentation site deployment.

Since this documentation link is being added alongside updates to the DocFx configuration and Nginx base image, let's verify that the documentation site is properly deployed and accessible.

✅ Verification successful

Documentation site is properly deployed and functional

The documentation site is successfully deployed with:

  • Correct framework version information (.NET 9, .NET 8, .NET Standard 2.0)
  • Complete API documentation
  • Proper DocFx template implementation
  • Working navigation and features
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the documentation site is accessible
# and properly reflects the updated framework version

# Check if the documentation site is accessible
curl -I https://newtonsoft.codebelt.net/

# Search for framework version references in the documentation
curl -s https://newtonsoft.codebelt.net/ | grep -i "net9.0"

Length of output: 684


Script:

#!/bin/bash
# Follow redirects and check multiple version formats
curl -sL https://newtonsoft.codebelt.net/ | grep -iE "net ?9\.0|framework|version"

# Check the specific API page from the redirect
curl -sL https://newtonsoft.codebelt.net/api/Codebelt.Extensions.Newtonsoft.Json.html | grep -iE "net ?9\.0|framework|version"

# Get a list of available documentation pages
curl -sL https://newtonsoft.codebelt.net/ | grep -o 'href="[^"]*"' | grep -i 'html'

Length of output: 1056


Script:

#!/bin/bash
# Get the full HTML content of the main page
curl -sL https://newtonsoft.codebelt.net/ > page.html
head -n 50 page.html

# Get the full HTML content of an API page
curl -sL https://newtonsoft.codebelt.net/api/Codebelt.Extensions.Newtonsoft.Json.html > api.html
head -n 50 api.html

# Look for metadata and version info in specific DocFx elements
cat page.html | grep -A 5 '<meta' || true
cat api.html | grep -A 5 '<meta' || true

Length of output: 10227

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

9-9: Bare URL used
null

(MD034, no-bare-urls)

Directory.Packages.props (3)

6-15: LGTM! Consistent version updates across Codebelt packages.

All Codebelt and Cuemon packages have been consistently updated to version 9.0.1.


27-30: LGTM! Framework-specific package versions are properly aligned.

The Microsoft.AspNetCore.Mvc.NewtonsoftJson package versions are correctly aligned with their respective target frameworks:

  • net9: 9.0.1
  • net8: 8.0.12

24-24: Verify compatibility with xunit.runner.visualstudio major version update.

The update from 2.8.2 to 3.0.1 is a major version change that might introduce breaking changes.

.docfx/docfx.json (1)

17-17: LGTM! Documentation configuration updates are accurate.

The changes correctly reflect:

  • Updated target framework to net9.0
  • Extended copyright year range to 2024-2025

Also applies to: 50-50

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

1-2: LGTM! Version and framework support are correctly updated.

The version number and framework availability are accurately specified and align with the PR objectives.

Copy link

codecov bot commented Jan 30, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.01%. Comparing base (6c566d8) to head (d76dbf5).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   78.01%   78.01%           
=======================================
  Files          24       24           
  Lines         905      905           
  Branches      111      111           
=======================================
  Hits          706      706           
  Misses        197      197           
  Partials        2        2           

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

@gimlichael gimlichael merged commit fadaad2 into main Jan 30, 2025
21 checks passed
@gimlichael gimlichael deleted the v9.0.1/package-maintenance branch January 30, 2025 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant