Add release.yml workflow; factor publish out of ci.yml#2
Merged
StuartMeeks merged 1 commit intomainfrom May 3, 2026
Merged
Conversation
Tag-driven publish to nuget.org now lives in its own workflow file (matches the layout the user asked for; aligned with how the Auth repo gates publishing on `refs/tags/v*`). - .github/workflows/release.yml — triggers on `v*` tag push. Restore → build → test → pack → upload-artifact → nuget push --skip-duplicate. Self-contained: doesn't depend on a CI workflow run completing first. - .github/workflows/ci.yml — drops the `tags` trigger and the publish job. CI now runs only on push-to-main and PRs; release.yml owns the tag flow end-to-end. Repo needs a NUGET_API_KEY secret for the push to succeed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/release.yml— triggers onv*tag push. Self-contained: restore → build → test → pack → upload-artifact → push to nuget.org with--skip-duplicate. Does not depend on a separate CI run completing first..github/workflows/ci.yml— drops thetagstrigger and the publish job. CI now runs on push-to-main and PRs only; release.yml owns the tag flow end-to-end.This matches the layout you asked for. Aligned with the Auth repo's logic for gating publication on
refs/tags/v*, just split into its own file for clarity.Required setup before tagging
The repo needs a
NUGET_API_KEYsecret. Add it via Settings → Secrets and variables → Actions → New repository secret.Test plan
v0.1.xtag and confirm release.yml fires, builds the package, and pushes to nuget.orgTag/publish flow after merge
🤖 Generated with Claude Code