Skip to content

Conversation

gimlichael
Copy link
Member

@gimlichael gimlichael commented Jan 28, 2025

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

Dependency and version updates:

Documentation and metadata updates:

Release notes updates:

Summary by CodeRabbit

Release Notes for Version 9.0.1

  • Package Updates

    • Updated package dependencies to latest versions
    • Added support for .NET 9 and .NET 8
    • Incremented version numbers for multiple packages, including Codebelt.Extensions and YamlDotNet
  • Documentation

    • Updated copyright year to 2024-2025
    • Updated release notes for various packages
  • Infrastructure

    • Updated Docker image for test environments
  • Chores

    • Minor improvements and dependency management
    • Removed deprecated configuration settings and package references

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

coderabbitai bot commented Jan 28, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces significant updates to the project's infrastructure and dependencies, primarily focusing on version increments and compatibility with .NET 9. Changes include updating the Nginx base image, modifying the target framework in configuration files, incrementing package versions, and adjusting copyright years. Additionally, support for .NET 6 has been removed across various components, while new Docker image versions and release notes have been updated to reflect these changes.

Changes

File Change Summary
.docfx/Dockerfile.docfx Nginx base image updated from 1.27.0-alpine to 1.27.3-alpine
.docfx/docfx.json Updated TargetFramework to net9.0 and copyright year to 2024-2025
.nuget/*/PackageReleaseNotes.txt Version bumped from 9.0.0 to 9.0.1 across multiple packages, added .NET 9 and .NET 8 availability
CHANGELOG.md New version entry added for 9.0.1 dated January 28, 2025
Directory.Build.props Updated copyright year, removed Microsoft.SourceLink.GitHub package reference
Directory.Build.targets Removed MinVerTagPrefix property
Directory.Packages.props Updated multiple package versions (e.g., YamlDotNet, xunit, coverlet)
LICENSE Updated copyright notice to 2024-2025
testenvironments.json Updated Docker image version

Possibly related PRs

Poem

🐰 Hop, hop, version update time!
Dependencies dancing in line
.NET 9 shines so bright
Packages aligned just right
A rabbit's code refresh sublime! 🚀


📜 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 e933b0a and 7fe7613.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

CodeRabbit Configuration File (.coderabbit.yaml)

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

Documentation and Community

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🔭 Outside diff range comments (1)
Directory.Build.props (1)

Remove orphaned source link configuration or restore the package

The source link configuration properties are present but ineffective without the Microsoft.SourceLink.GitHub package. This creates misleading configuration as the properties suggest source link functionality that isn't actually available. Either:

  • Remove the orphaned properties (EmbedUntrackedSources, PublishRepositoryUrl, IncludeSymbols, SymbolPackageFormat)
  • Or restore the Microsoft.SourceLink.GitHub package to enable the intended functionality
🔗 Analysis chain

Line range hint 18-40: Verify impact of removing Microsoft.SourceLink.GitHub.

The Microsoft.SourceLink.GitHub package has been removed, but the following properties are still present:

  • EmbedUntrackedSources
  • PublishRepositoryUrl
  • IncludeSymbols
  • SymbolPackageFormat

Please verify if source link functionality is still required.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for source link configuration and usage

# Check if any other source link packages are referenced
rg -l "Microsoft.SourceLink" --type props --type csproj

# Verify if source link is still enabled in build output
find . -name "*.snupkg" -o -name "*.symbols.nupkg" | while read pkg; do
  echo "Checking source link in $pkg"
  dotnet symbol verify "$pkg" || true
done

Length of output: 149


Script:

#!/bin/bash
# Search for any SourceLink related packages and configurations
rg -l "Microsoft\.SourceLink|SourceLink" --type-add 'props:*.props' --type-add 'csproj:*.csproj' --type props --type csproj

# Check for any package references that might be related to source linking
rg -l "PackageReference.*Source" --type-add 'props:*.props' --type-add 'csproj:*.csproj' --type props --type csproj

# Look for any source debugging related configurations
rg "(EmbedUntrackedSources|PublishRepositoryUrl|IncludeSymbols|SymbolPackageFormat)" --type-add 'props:*.props' --type-add 'csproj:*.csproj' --type props --type csproj -A 1 -B 1

Length of output: 1371

🧹 Nitpick comments (2)
.nuget/Codebelt.Extensions.YamlDotNet.App/PackageReleaseNotes.txt (1)

1-5: Consider simplifying the dependency update note.

The version and availability information is correct, but consider simplifying "with respect to TFMs" to "for supported frameworks" or simply "across frameworks" for better readability.

-CHANGED Dependencies to latest and greatest with respect to TFMs
+CHANGED Dependencies to latest and greatest across 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)

.nuget/Codebelt.Extensions.AspNetCore.Mvc.Formatters.Text.Yaml/PackageReleaseNotes.txt (1)

4-5: Consider simplifying the ALM change description.

The phrase "with respect to TFMs" could be more concise.

-- CHANGED Dependencies to latest and greatest with respect to TFMs
++ CHANGED Dependencies to latest versions for all 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.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 cc4aba4 and cfca243.

📒 Files selected for processing (12)
  • .docfx/Dockerfile.docfx (1 hunks)
  • .docfx/docfx.json (2 hunks)
  • .nuget/Codebelt.Extensions.AspNetCore.Mvc.Formatters.Text.Yaml/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Codebelt.Extensions.AspNetCore.Text.Yaml/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Codebelt.Extensions.YamlDotNet.App/PackageReleaseNotes.txt (1 hunks)
  • .nuget/Codebelt.Extensions.YamlDotNet/PackageReleaseNotes.txt (1 hunks)
  • CHANGELOG.md (1 hunks)
  • Directory.Build.props (1 hunks)
  • Directory.Build.targets (0 hunks)
  • Directory.Packages.props (1 hunks)
  • LICENSE (1 hunks)
  • testenvironments.json (1 hunks)
💤 Files with no reviewable changes (1)
  • Directory.Build.targets
✅ Files skipped from review due to trivial changes (3)
  • LICENSE
  • .docfx/Dockerfile.docfx
  • testenvironments.json
🧰 Additional context used
🪛 LanguageTool
.nuget/Codebelt.Extensions.YamlDotNet.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.0
Availability: ....

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Codebelt.Extensions.AspNetCore.Text.Yaml/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.AspNetCore.Mvc.Formatters.Text.Yaml/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.YamlDotNet/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)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: 🛠️ Build (Release, net8.0)
  • GitHub Check: 🛠️ Build (Release, net9.0)
🔇 Additional comments (9)
Directory.Packages.props (2)

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

All Codebelt and Cuemon packages have been consistently updated to version 9.0.1, maintaining version alignment across the ecosystem.


22-24: Verify compatibility with xunit major version update.

The xunit.runner.visualstudio package has been updated to 3.0.1, which is a major version bump. While the changes look good, please ensure compatibility with the test suite.

✅ Verification successful

The xunit.runner.visualstudio 3.0.1 update is compatible with the current setup

The version difference between xunit core (2.9.3) and VS runner (3.0.1) is normal and safe, as the Visual Studio test runner is decoupled from the core xunit version. The codebase uses high-level test abstractions via Codebelt.Extensions.Xunit packages and doesn't directly interact with runner APIs.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any breaking changes in xunit.runner.visualstudio v3.0.1

# Search for xunit runner usage patterns that might be affected
rg -l "ITestRunner|TestRunner|RunnerSettings" --type cs

# Check release notes for breaking changes
curl -s "https://raw.githubusercontent.com/xunit/visualstudio.xunit/v3.0.1/CHANGELOG.md"

Length of output: 161


Script:

#!/bin/bash
# Find test projects and configurations
fd -e csproj | xargs grep -l "xunit" || true
fd TestSettings.json || true

# Get package info from NuGet
curl -s "https://api.nuget.org/v3/registration5-gz-semver2/xunit.runner.visualstudio/index.json" | jq -r '.items[0].items[] | select(.catalogEntry.version | startswith("3.0.")) | .catalogEntry.version,.catalogEntry.description'

# Look for any custom test configurations in MSBuild files
fd -e props -e targets | xargs grep -l "VSTest" || true

Length of output: 407


Script:

#!/bin/bash
# List all files to understand project structure
fd . --type f -e csproj -e props -e targets

# Find test projects content
fd "test" -t f -e csproj | xargs cat || true

# Look for xunit configurations
fd . -t f -e csproj -e props | xargs grep -i "xunit" || true

Length of output: 2971

Directory.Build.props (1)

19-19: LGTM! Copyright year updated appropriately.

The copyright year has been updated to include 2025, which is correct for the upcoming release.

.nuget/Codebelt.Extensions.AspNetCore.Text.Yaml/PackageReleaseNotes.txt (1)

1-5: LGTM! Release notes are consistent.

The version update and framework support information align with other package updates in this PR.

The same wording improvement suggestion applies here as in the YamlDotNet.App 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.0
Availability: ....

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

.nuget/Codebelt.Extensions.AspNetCore.Mvc.Formatters.Text.Yaml/PackageReleaseNotes.txt (1)

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

The version update and framework support are clearly documented.

.docfx/docfx.json (1)

50-50: LGTM! Copyright year is updated correctly.

The copyright year update to include 2025 is consistent with the PR objectives.

.nuget/Codebelt.Extensions.YamlDotNet/PackageReleaseNotes.txt (2)

1-2: LGTM! Version and framework support are well documented.

The version update and framework compatibility are clearly specified.


4-5: Same wording improvement needed as in AspNetCore.Mvc.Formatters.Text.Yaml/PackageReleaseNotes.txt.

For consistency, apply the same wording improvement here.

🧰 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-13: LGTM! Changelog entry follows the standard format.

The entry is well-structured, concise, and follows the Keep a Changelog format. The description accurately reflects the nature of this service update.

"filter": "filterConfig.yml",
"properties": {
"TargetFramework": "net8.0"
"TargetFramework": "ne9.0"
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix typo in TargetFramework value.

There's a typo in the framework moniker.

-        "TargetFramework": "ne9.0"
+        "TargetFramework": "net9.0"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"TargetFramework": "ne9.0"
"TargetFramework": "net9.0"

Copy link

@gimlichael gimlichael merged commit 6352b0a into main Jan 28, 2025
6 of 7 checks passed
@gimlichael gimlichael deleted the v9.0.1/package-maintenance branch January 28, 2025 22:16
@coderabbitai coderabbitai bot mentioned this pull request May 24, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jun 15, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jul 10, 2025
@coderabbitai coderabbitai bot mentioned this pull request Sep 15, 2025
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