Repository navigation
Drop the trackdubllc NUGET_USER fallback in the release workflow - #41
Conversation
The NUGET_USER secret supplies the nuget.org username; the hardcoded fallback named the repository's previous owner and could only ever produce a 401 from the token exchange. Fail early with a message naming the setting instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
There was a problem hiding this comment.
Review Summary
This PR makes a focused, correct change to the release.yml workflow. The hardcoded 'trackdubllc' fallback is removed, and a new "Check NuGet user" preflight step is added that fails fast with a clear, actionable error message when NUGET_USER is not configured — rather than silently producing a 401 from nuget.org's Trusted Publishing policy mismatch.
The logic is sound: both the new check step and the NuGet/login step use the same vars.NUGET_USER || secrets.NUGET_USER expression, so they remain in sync. The early exit prevents a confusing auth failure further down the job.
No defects found. ✅
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
Removes the
'trackdubllc'fallback from theNuGet/loginstep'suserinrelease.yml.NUGET_USERsecret supplies the nuget.org username, and the v0.6.0 rerun used it. The fallback named the repository's previous owner. Trusted Publishing needs the username of whoever created the policy, so the fallback could only ever produce the token-exchange 401 ("No matching trust policy owned by user …").Check NuGet userstep comes before the login. If neithervars.NUGET_USERnorsecrets.NUGET_USERis set, it fails with an error that names the setting.Only
release.ymlchanges. It runs onv*tags, so it takes effect at the next release.🤖 Generated with Claude Code
Summary by CodeRabbit