Skip to content

fixes #38 / Update release-build.yml #39

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 7 commits into from
Jun 19, 2025

Conversation

AkrausGH
Copy link
Contributor

@AkrausGH AkrausGH commented Jun 19, 2025

Updated release-build.yml to use dotnet nuget push command.

Summary by CodeRabbit

  • Chores
    • Updated workflows and project files to target the latest .NET 8.0 framework.
    • Improved build and release workflows with updated tooling versions and streamlined commands for package publishing.

Updated release-build.yml to use dotnet nuget push command.
@AkrausGH AkrausGH linked an issue Jun 19, 2025 that may be closed by this pull request
Copy link

coderabbitai bot commented Jun 19, 2025

Walkthrough

The workflow for publishing packages to NuGet in the GitHub Actions release build was updated to use the dotnet nuget push command with Unix-style path globbing and updated command-line options, replacing the previous use of the nuget push command. Additionally, all projects and workflows were upgraded to target and use .NET 8.0 and GitVersion.Tool version 5.12.0.

Changes

File(s) Change Summary
.github/workflows/release-build.yml, .github/workflows/ci-build.yml Upgraded .NET setup action from v3 to v4, changed target SDK from 6.0.x to 8.0.x, and pinned GitVersion.Tool to v5.12.0 globally.
src/...FontAwesomeTagHelpers.Sample/.csproj, src/...FontAwesomeTagHelpers.Tests/.csproj, src/...FontAwesomeTagHelpers/*.csproj Updated target framework from .NET 6.0 to .NET 8.0 in sample, test, and main library projects.
.github/workflows/release-build.yml Changed NuGet package publishing step to use dotnet nuget push with Unix-style glob pattern and shortened CLI options.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant dotnet CLI
    participant NuGet Server

    GitHub Actions->>dotnet CLI: dotnet nuget push **/*.nupkg -s ... -k ...
    dotnet CLI->>NuGet Server: Upload .nupkg package(s) using API key
    NuGet Server-->>dotnet CLI: Response (success/failure)
    dotnet CLI-->>GitHub Actions: Publish result
Loading

Assessment against linked issues

Objective Addressed Explanation
Update workflow to use dotnet nuget push with correct glob and options (#38)

Assessment against linked issues: Out-of-scope changes

(No out-of-scope changes found.)

Poem

A hop to the cloud, a push to NuGet land,
With dotnet in paw, the workflow is grand.
No more backslashes, just forward we go,
Unix-y globs make the packages flow.
🐇✨ Onward to publish, let the carrots bestow!

✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch feature/38-update-production-release-for-nuget

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 auto-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.

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 (1)
.github/workflows/release-build.yml (1)

44-44: Normalize secret interpolation, quote globs, and optionally push symbols

The current step:

run: dotnet nuget push **/*.nupkg -s 'https://api.nuget.org/v3/index.json' -k ${{secrets.ICG_NUGET_API_KEY}}

can be tightened up to:

-run: dotnet nuget push **/*.nupkg -s 'https://api.nuget.org/v3/index.json' -k ${{secrets.ICG_NUGET_API_KEY}}
+run: dotnet nuget push "**/*.nupkg" -s "https://api.nuget.org/v3/index.json" -k ${{ secrets.ICG_NUGET_API_KEY }}

And, if you also publish symbol packages, add a second push step:

+  - name: Publish symbols to NuGet
+    run: dotnet nuget push "**/*.snupkg" -s "https://api.nuget.org/v3/index.json" -k ${{ secrets.ICG_NUGET_API_KEY }}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0882434 and 3fc81ab.

📒 Files selected for processing (1)
  • .github/workflows/release-build.yml (1 hunks)

@mitchelsellers
Copy link
Contributor

@AkrausGH This one is going to take a bit more updates to get current, if you want to try and tackle this it would be great. But the following is going to be needed.

  • Update the project to .NET 8.0
  • Update the build to ensure .NET 8.0 (Both this one, AND the other build file)

Then try again, we MAY need to replace the gitversion.yml file with a modified version as well

AkrausGH added 6 commits June 19, 2025 14:13
Changed the target frameworks for the three projects.  I also updated the release-build to refer to .NET 8.0.
Trying to change the "Ensure .NET Installed" command.
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 (2)
.github/workflows/ci-build.yml (1)

25-25: Remove trailing whitespace
YAMLLint flags trailing spaces on this line—please remove them to clear lint errors.

.github/workflows/release-build.yml (1)

26-26: Remove trailing whitespace
A trailing space was detected here. Removing it will resolve the YAMLLint error.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3fc81ab and 68c49ee.

📒 Files selected for processing (5)
  • .github/workflows/ci-build.yml (1 hunks)
  • .github/workflows/release-build.yml (2 hunks)
  • src/AspNetCore.Utilities.FontAwesomeTagHelpers.Sample/AspNetCore.Utilities.FontAwesomeTagHelpers.Sample.csproj (1 hunks)
  • src/AspNetCore.Utilities.FontAwesomeTagHelpers.Tests/AspNetCore.Utilities.FontAwesomeTagHelpers.Tests.csproj (1 hunks)
  • src/AspNetCore.Utilities.FontAwesomeTagHelpers/AspNetCore.Utilities.FontAwesomeTagHelpers.csproj (1 hunks)
✅ Files skipped from review due to trivial changes (3)
  • src/AspNetCore.Utilities.FontAwesomeTagHelpers.Tests/AspNetCore.Utilities.FontAwesomeTagHelpers.Tests.csproj
  • src/AspNetCore.Utilities.FontAwesomeTagHelpers.Sample/AspNetCore.Utilities.FontAwesomeTagHelpers.Sample.csproj
  • src/AspNetCore.Utilities.FontAwesomeTagHelpers/AspNetCore.Utilities.FontAwesomeTagHelpers.csproj
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/ci-build.yml

[error] 25-25: trailing spaces

(trailing-spaces)

.github/workflows/release-build.yml

[error] 26-26: trailing spaces

(trailing-spaces)

🔇 Additional comments (5)
.github/workflows/ci-build.yml (2)

22-24: Upgrade .NET Setup Action and Target SDK
Using actions/setup-dotnet@v4 with dotnet-version: 8.0.x correctly aligns the CI pipeline with the .NET 8 migration.


27-27: Pin GitVersion.Tool for Consistency
Specifying --version 5.12.0 ensures deterministic versioning across CI and release builds.

.github/workflows/release-build.yml (3)

23-25: Upgrade .NET Setup Action and Target SDK
Switching to actions/setup-dotnet@v4 and dotnet-version: 8.0.x keeps the release pipeline in sync with your .NET 8 upgrade.


28-28: Pin GitVersion.Tool for Reproducibility
Locking the tool to version 5.12.0 matches your CI config and prevents unexpected version bumps.


44-44: Switch to dotnet nuget push with Unix-Style Globs
Replacing nuget push with dotnet nuget push **/*.nupkg -s … -k … ensures cross-platform compatibility and uses the official .NET CLI.

Copy link
Contributor

@mitchelsellers mitchelsellers left a comment

Choose a reason for hiding this comment

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

This looks good, will address the other issue later

@mitchelsellers mitchelsellers merged commit 0de05d9 into main Jun 19, 2025
2 of 3 checks passed
@mitchelsellers mitchelsellers deleted the feature/38-update-production-release-for-nuget branch June 19, 2025 20:00
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.

Update Production Release for NuGet
2 participants