Publish TypeScript SDKs to npm with OIDC#220
Merged
Merged
Conversation
IxayWolf
force-pushed
the
ivana/npm-oidc-publish
branch
8 times, most recently
from
May 15, 2026 10:01
afbe009 to
3465fbc
Compare
lorenzosignoretti
approved these changes
May 18, 2026
IxayWolf
force-pushed
the
ivana/npm-oidc-publish
branch
from
May 18, 2026 08:12
3465fbc to
bec7908
Compare
IxayWolf
force-pushed
the
ivana/npm-oidc-publish
branch
from
May 19, 2026 13:37
bec7908 to
442014f
Compare
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.
Summary
--access public, and--provenance.NPM_TOKEN; publishing now relies on GitHub OIDC plus npm trusted publisher config.npm@11.14.0vianpx -pfor dependency installs with--ignore-scripts --min-release-age=7.npm_tag.Environment / secrets
publish.MISTRAL_API_KEYis expected from thepublishenvironment for the examples workflow.publishenvironment.Required GitHub environment setup
publishenvironment must expose the needed secrets, includingMISTRAL_API_KEY.environment: publish, the environment branch policy must allow PR branches too. Right now it only allowsmain, so PR checks are rejected before any runner steps start.Required npm setup
Configure trusted publishers on npmjs.com for:
@mistralai/mistralai:.github/workflows/sdk_publish_mistralai_sdk.yaml, envpublish@mistralai/mistralai-azure:.github/workflows/sdk_publish_mistralai_azure_sdk.yaml, envpublish@mistralai/mistralai-gcp:.github/workflows/sdk_publish_mistralai_gcp_sdk.yaml, envpublishAll should point to repo
mistralai/client-ts.Verification
npx -p npm@11.14.0 npm install --ignore-scripts --min-release-age=7git diff --checkNote:
npm@11.14.0is used because it supportsmin-release-ageand is older than 7 days as of May 15, 2026.