Repository navigation
chore(release): publish NuGet and RubyGems packages through gated trusted publishing - #709
Merged
Merged
Conversation
… trusted publishing for traceai-auto and traceai-roast
…usted publishing; point go/auto docs at v0.1.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publishes the .NET and Ruby auto-instrumentation packages through the same gated release route as Python, TypeScript, Java and Go.
Changes
main, after a successful build, when NuGet trusted publishing is configured (vars.NUGET_USER, environmentnuget). It was previously switched off.ruby-buildjob and arubypublish job fortraceai-autoandtraceai-roast, using RubyGems trusted publishing (OIDC, environmentrubygems,vars.RUBYGEMS_TRUSTED_PUBLISHING). It pushes only versions not yet on rubygems.org, and checks the registry before taggingruby-<gem>-vX.Y.Z.@v0.1.0.No stored registry keys are used, and nothing publishes until the trusted-publisher setup in RELEASING.md is done.