Skip to content

V0.4.3/package maintenance #13

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

Merged
merged 6 commits into from
May 29, 2025
Merged

V0.4.3/package maintenance #13

merged 6 commits into from
May 29, 2025

Conversation

gimlichael
Copy link
Member

@gimlichael gimlichael commented May 29, 2025

This pull request introduces several updates aimed at improving dependency management, streamlining workflows, and ensuring compatibility with the latest frameworks and tools. The most significant changes include upgrading dependencies, refactoring GitHub Actions workflows, and updating Docker configurations.

Dependency Updates:

  • Updated various NuGet package versions in Directory.Packages.props, including Cuemon.Extensions.IO (9.0.4 → 9.0.5), Microsoft.NET.Test.Sdk (17.13.0 → 17.14.0), and Savvyio.Domain (4.0.2 → 4.0.3), among others.
  • Added a new release note for version 0.4.3 in .nuget/Codebelt.SharedKernel/PackageReleaseNotes.txt, highlighting upgraded dependencies for all supported target frameworks.
  • Updated the changelog in CHANGELOG.md to include details about version 0.4.3, which focuses on package dependency updates.

Workflow Refactoring:

  • Simplified GitHub Actions workflows in .github/workflows/pipelines.yml by replacing inline job definitions with reusable workflows, such as codebeltnet/jobs-dotnet-build, codebeltnet/jobs-dotnet-pack, and codebeltnet/jobs-dotnet-test. This reduces duplication and improves maintainability. [1] [2]

Docker Configuration Updates:

  • Updated the base Docker images in .docfx/Dockerfile.docfx to use the --platform=$BUILDPLATFORM flag and upgraded nginx (1.27.3 → 1.27.5) and codebeltnet/docfx (2.77.0 → 2.78.3) for improved compatibility and security.

Test Environment Update:

  • Updated the Docker image for the "Docker-Ubuntu" test environment in testenvironments.json to gimlichael/ubuntu-testrunner:net8.0.409-9.0.300 for compatibility with the latest .NET versions.

Summary by CodeRabbit

  • Chores
    • Upgraded several dependencies and Docker images to their latest compatible versions.
    • Updated test environment Docker image for Ubuntu.
    • Refactored CI/CD pipeline to use reusable workflows, improving maintainability and standardization.
  • Documentation
    • Added release notes and changelog entries for version 0.4.3, highlighting updated dependencies and .NET 8/9 support.

@gimlichael gimlichael self-assigned this May 29, 2025
Copy link

coderabbitai bot commented May 29, 2025

Walkthrough

This update revises dependency versions in project configuration files, updates Docker and test runner images to newer versions, and refactors the CI workflow to use reusable GitHub Actions workflows. Release notes and changelogs are updated to reflect the new package version and dependency upgrades, with no changes to exported code entities.

Changes

File(s) Change Summary
.docfx/Dockerfile.docfx Upgraded nginx and docfx base images; added explicit build platform flags; simplified final stage usage.
.github/workflows/pipelines.yml Refactored jobs to use reusable workflow calls; updated job dependencies and matrix; minor formatting.
Directory.Packages.props Updated versions of several NuGet package dependencies.
testenvironments.json Updated Docker image version for the "Docker-Ubuntu" test environment.
.nuget/Codebelt.SharedKernel/PackageReleaseNotes.txt, CHANGELOG.md Added entries for version 0.4.3, noting dependency updates and .NET 8/9 support.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant Reusable Workflows

    Developer->>GitHub Actions: Push code/PR triggers pipeline
    GitHub Actions->>Reusable Workflows: Call build workflow (with params)
    GitHub Actions->>Reusable Workflows: Call pack workflow (after build)
    GitHub Actions->>Reusable Workflows: Call test workflow (after build)
    GitHub Actions->>Reusable Workflows: Call deploy workflow (after pack)
    Reusable Workflows-->>GitHub Actions: Return job results
    GitHub Actions-->>Developer: Report pipeline status
Loading

Possibly related PRs

  • codebeltnet/shared-kernel#7: Previous Dockerfile base image and docfx build script upgrades, showing a direct progression in Docker build environment maintenance.
  • codebeltnet/shared-kernel#11: Earlier upgrade of nginx base image in the same Dockerfile, related to the current update's further version bump.
  • codebeltnet/shared-kernel#12: Related package version management updates in project configuration files, complementing the current dependency version changes.

Poem

A rabbit hops with nimble feet,
Upgrading packages, so neat!
Docker and workflows, shiny and new,
Test runners fresh, dependencies too.
With changelogs penned and notes in place—
Onward we hop, embracing the race!
🐇✨


📜 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 5403b41 and 52db0c1.

📒 Files selected for processing (1)
  • .github/workflows/pipelines.yml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/pipelines.yml
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: call-codeql / 🛡️ Security Analysis
  • GitHub Check: call-sonarcloud / 🔬 Code Quality Analysis

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.
    • @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 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.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in 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.

Copy link

codecov bot commented May 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.50%. Comparing base (24bf76b) to head (52db0c1).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   88.50%   88.50%           
=======================================
  Files          11       11           
  Lines         200      200           
  Branches        8        8           
=======================================
  Hits          177      177           
  Misses         23       23           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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 (3)
.docfx/Dockerfile.docfx (1)

11-11: Ensure platform consistency for final stage
To maintain multi-platform support throughout the build, consider adding the --platform=$BUILDPLATFORM flag to the final stage.

-FROM nginx:1.27.5-alpine AS final
+FROM --platform=$BUILDPLATFORM nginx:1.27.5-alpine AS final
CHANGELOG.md (1)

7-9: Clarify 0.4.3 changelog entry
The entry for 0.4.3 repeats the generic description from 0.4.2. Consider specifying the key package upgrades to improve clarity for readers.

- This is a service update that focuses on package dependencies.
+ This release updates several package dependencies, including Cuemon.Extensions.IO (9.0.4→9.0.5), Microsoft.NET.Test.Sdk (17.13.0→17.14.0), and more. See `.nuget/Codebelt.SharedKernel/PackageReleaseNotes.txt` for full details.
.nuget/Codebelt.SharedKernel/PackageReleaseNotes.txt (1)

5-5: Align ALM description style across notes
The new bullet “Dependencies have been upgraded to the latest compatible versions for all supported target frameworks (TFMs)” is clear, but its phrasing differs from prior entries (e.g., “Dependencies to latest and greatest with respect to TFMs”). Consider unifying the tone/length across all ALM bullets for consistency.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 24bf76b and 3bc4adc.

📒 Files selected for processing (6)
  • .docfx/Dockerfile.docfx (1 hunks)
  • .github/workflows/pipelines.yml (2 hunks)
  • .nuget/Codebelt.SharedKernel/PackageReleaseNotes.txt (1 hunks)
  • CHANGELOG.md (1 hunks)
  • Directory.Packages.props (1 hunks)
  • testenvironments.json (1 hunks)
🧰 Additional context used
🪛 Hadolint (2.12.0)
.docfx/Dockerfile.docfx

[error] 6-6: Use COPY instead of ADD for files and folders

(DL3020)

🔇 Additional comments (9)
.docfx/Dockerfile.docfx (2)

1-1: Explicit multi-platform support
Specifying --platform=$BUILDPLATFORM for the base stage ensures the image is built correctly on multiple architectures.


4-4: Consistent multi-platform flag for build stage
Adding --platform=$BUILDPLATFORM to the DocFX build image aligns with the base stage and ensures reproducible multi-arch builds.

Directory.Packages.props (1)

6-12: Centralized package version bumps
All centrally managed NuGet packages have been updated to their latest patch versions for the 0.4.3 release. Please verify compatibility and ensure no breaking changes or vulnerabilities have been introduced by these upgrades.

Also applies to: 17-17

testenvironments.json (1)

12-12: Update Docker test runner image version
Upgraded the Docker-Ubuntu test environment to use gimlichael/ubuntu-testrunner:net8.0.409-9.0.300. Confirm that this image is published and compatible with the intended .NET SDK versions.

.github/workflows/pipelines.yml (4)

26-34: Adopt reusable workflow for build job
The build job now invokes codebeltnet/jobs-dotnet-build as a reusable workflow, reducing duplication and centralizing build logic. Inputs for configuration and strong-name-key-filename are correctly passed, and secrets are inherited.


37-46: Use reusable workflow for packaging
Refactored the pack job to call codebeltnet/jobs-dotnet-pack with configuration, artifact upload flag, and version from the build outputs. This aligns with the DRY principle.


49-60: Refactor test job to reusable workflow
The test job now leverages codebeltnet/jobs-dotnet-test with matrixed os and configuration inputs, plus the SkipSignAssembly flag. This change simplifies maintenance but please verify that the reusable workflow accepts runs-on via with.


90-91: Switch to reusable NuGet push workflow
The deploy job now calls codebeltnet/jobs-nuget-push with version and environment inputs, streamlining the release process. Dependencies are correctly specified.

.nuget/Codebelt.SharedKernel/PackageReleaseNotes.txt (1)

1-2: Release note entry for v0.4.3 looks good
The new version header and availability lines correctly introduce the 0.4.3 release with the supported TFMs.

Copy link

@gimlichael gimlichael merged commit cb72bf9 into main May 29, 2025
29 checks passed
@gimlichael gimlichael deleted the v0.4.3/package-maintenance branch May 29, 2025 21:41
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