Publish TypeScript SDK with trusted credentials - #71843
Draft
jason810496 wants to merge 2 commits into
Draft
Conversation
boring-cyborg
Bot
added
area:dev-tools
area:ts-sdk
backport-to-v3-3-test
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
1 participant
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.
Why
Publishing the TypeScript SDK with a long-lived npm token would expose a reusable credential and would not establish verifiable build provenance.
How
ts-sdk/<version>tag.ts-sdk-npmGitHub environment.nextand stable versions underlatest.The actual publish step requires the
apache/airflowGitHub environment and npm trusted-publisher configuration described in the documentation.Was generative AI tooling used to co-author this PR?