Skip to content

Drop the trackdubllc NUGET_USER fallback in the release workflow - #41

Merged
tonythethompson merged 1 commit into
mainfrom
claude/nuget-user-no-fallback
Oct 23, 2026
Merged

tonythethompson merged 1 commit into
mainfrom
claude/nuget-user-no-fallback

Conversation

@tonythethompson

@tonythethompson tonythethompson commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Removes the 'trackdubllc' fallback from the NuGet/login step's user in release.yml.

  • Why: the NUGET_USER secret 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 …").
  • Now: a Check NuGet user step comes before the login. If neither vars.NUGET_USER nor secrets.NUGET_USER is set, it fails with an error that names the setting.

Only release.yml changes. It runs on v* tags, so it takes effect at the next release.

🤖 Generated with Claude Code

View guided diff Turn on auto-fix

Summary by CodeRabbit

  • Chores
    • NuGet publishing now stops with a clear error when the account name is missing, rather than attempting to log in with a default account.
    • Publishing requires the account name to be configured as a repository variable or secret.

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>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T01:39:43.291296Z b751957 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: b6d95f07-85c0-478a-b167-9bdc952504b7
📥 Commits

Reviewing files that changed from the base of the PR and between c9bc459 and b751957.

📒 Files selected for processing: 1
  • .github/workflows/release.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The NuGet.org publishing job now checks for a configured NUGET_USER before OIDC login. The login step uses the repository variable or secret value and no longer falls back to trackdubllc.

Changes: NuGet.org publishing

Layer / File(s) Summary
Validate NuGet user before login
.github/workflows/release.yml
The job exits with an error if NUGET_USER is empty. The OIDC login uses the repository variable or secret value without a fallback username.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to b7519

The release workflow now fails clearly when the NuGet user is unconfigured and otherwise uses the configured identity without the stale fallback.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main change: removing the hardcoded trackdubllc fallback for NUGET_USER in the release workflow.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
✨ Simplify code
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

MCP server "Context7": 1 tool is paused until its current definition is approved, so CodeRabbit can't use it. Paused: query-docs. Review and approve it to resume use.

MCP server "GitHub Copilot": 1 tool is paused until its current definition is approved, so CodeRabbit can't use it. Paused: search_repositories. Review and approve it to resume use.

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

Comment @coderabbitai help to get the list of available commands.

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.

@tonythethompson
tonythethompson merged commit 4695bae into main Oct 23, 2026
8 checks passed
@tonythethompson
tonythethompson deleted the claude/nuget-user-no-fallback branch October 23, 2026 02:04
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