CI failure: CD publish failing: NUGET_UPLOAD_TOKEN API key expired #49

What failed

Workflow CD (run 41261979534), job cd / build_and_publish, step Publish NuGet (uses EvergineTeam/Evergine.Bindings/.github/actions/nuget-publish@v1).

Error

Forbidden (www.nuget.org/redacted) 361ms
error: Response status code does not indicate success: 403 (The specified API key has expired. Please create a new API key at (www.nuget.org/redacted)
##[error]Process completed with exit code 1.

Failure key

CD:build_and_publish:Publish NuGet:nuget-api-key-expired

Diagnosis

The NUGET_UPLOAD_TOKEN secret used to authenticate against (api.nuget.org/redacted) has expired on nuget.org's side. This is not a workflow misconfiguration, a flaky/transient failure (re-running will not help — the key itself is expired), nor a generator/spec issue. The generated package (revision 28, triggered by a vk.xml` change) built and committed successfully; only the publish step failed.

Required action (needs human)

1. Sign in to the NuGet account that owns the Evergine.Bindings.Vulkan package.
2. Create a new API key at (www.nuget.org/redacted) with push permissions for this package (and any other packages sharing this token across the org, if applicable).
3. Update the NUGET_UPLOAD_TOKEN repository/organization secret with the new key.
4. Re-run the failed CD workflow (or wait for the next scheduled run) to confirm the publish succeeds.

No code or workflow changes are needed — this is purely a credential rotation task that requires access to the NuGet account and repository secrets, both outside this agent's capabilities.

Generated by 🩺 CI Doctor · copilot · sonnet50 · 27.6 AIC · ⌖ 11.5 AIC · ⊞ 7.5K · ◷