Skip to content

Switch to NuGet trusted publishing #119

@martincostello

Description

@martincostello

We should switch from using API keys to publish packages to NuGet.org to the new Trusted Publishing feature: New Trusted Publishing enhances security on NuGet.org

This is more secure, and avoids the need to renew/rotate NuGet API keys.

See grafana/grafana-opentelemetry-dotnet#266 for an example of adopting this.

Image

As you have three different GitHub Actions workflows to publish the NuGet packages, you'll need to create a trusted publishing policy for each one. Values you'll need are below:

  • Repository organization: grafana
  • Repository name: pyroscope-dotnet
  • Workflow file: tag_managed_helper.yml or tag_tracing_opentracing_helper.yml or tag_tracing_opentelemetry_helper.yml

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions