Connect to the Createrun feed

Two feeds live on this server. https://nuget.createrun.ai/v3/index.json is anonymous and only lists public packages. https://nuget.createrun.ai/private/v3/index.json requires credentials and lists everything. Both speak NuGet protocol version 3.

1 · Add the public source

dotnet nuget add source https://nuget.createrun.ai/v3/index.json -n createrun

2 · Add the private source

dotnet nuget add source https://nuget.createrun.ai/private/v3/index.json -n createrun-private -u <user> -p <apikey> --store-password-in-clear-text

Any value works for -u; the API key in -p is what identifies you.

Linux and macOS need --store-password-in-clear-text. NuGet's password encryption is Windows-only, so without that flag the command fails on every other platform. Treat the resulting NuGet.Config as a secret file.

Do not add this feed to auditSources. It does not expose a VulnerabilityInfo resource, and NuGet will emit NU1905 on every restore.

3 · Push a package

dotnet nuget push <package>.nupkg -s https://nuget.createrun.ai/v3/index.json -k <apikey>

The key needs the push scope. Symbol packages (.snupkg) alongside the .nupkg are picked up by the same command.

CI credentials without NuGet.Config

On Linux and in CI, set the credentials through the environment instead of writing them to disk. The suffix after the underscore is the source name.

NuGetPackageSourceCredentials_createrun-private="Username=ci;Password=$CRNUG_KEY"

Or check in a NuGet.Config

<configuration>
  <packageSources>
    <add key="createrun" value="https://nuget.createrun.ai/v3/index.json" protocolVersion="3" />
    <add key="createrun-private" value="https://nuget.createrun.ai/private/v3/index.json" protocolVersion="3" />
  </packageSources>
</configuration>

Keep credentials out of this file — supply them through the environment variable above.

Getting a key

Sign in and open API keys. The raw key is displayed once when it is created or rotated; the server keeps only a hash of it.