[Project Support]: Rx.NET (Reactive Extensions for .NET) - NuGet API key expired

[idg10]

Project

Rx.NET (Reactive Extensions for .NET)

Project Url

https://github.com/dotnet/reactive

Description

I just tried to publish a new release of Rx.NET to NuGet, and I'm getting an error that the API key has expired. Here is the failing release:

https://dev.azure.com/dotnet/Rx.NET/_releaseProgress?releaseId=870&_a=release-environment-logs&environmentId=1740

The last successful release was on 2026/06/03 (just over a couple of weeks ago), so this has happened recently.

I did not set up this Release definition - we inherited this from the previous owners of the project. As far as I can tell, it's using the "NuGet.org - Rx" service connection here:

https://dev.azure.com/dotnet/Rx.NET/_settings/adminservices?resourceId=d2c78657-a857-4bff-adf8-868d3f21f03d

Looking at the published packages at https://www.nuget.org/packages/System.Reactive/ I guess I must have updated the actual service connection at some point—the packages used to be published by clairenovotny but as of 2023, they all have my name attached. So presumably I did actually generate an API key, I just have no recollection of doing so.

I could try just generating another API key, but I suspect that API keys are no longer the preferred way to do this sort of thing. (I see a big orange Not recommended label in the NuGet.org UI.) Since this has just worked up until today, I've never actually poked around in it. If we need to replace this with a better approach, I'm happy to do that, but will need guidance.

Note that our package names all start with System, so whatever special dispensation enabled us to do that needs to carry on working.

Due By

Asap

[idg10]

Having gone into the Trusted Publishing section of my NuGet.org settings, I see this:

Trusted Publishing lets you publish NuGet packages securely without managing API keys. It currently supports publishing from GitHub Actions.

This suggests that Azure DevOps Pipelines are not currently supported.

So I have gone ahead and generated a new key. However, I'm leaving this ticket open in case there was some better way I was supposed to do this. But if API keys continue to be the only option for NuGet.org publishing from an Azure Pipeline, then I'm up and running again.