ci: enable npm provenance via OIDC in release pipeline#761
Conversation
Migrates the semantic-release publishing pipeline from using a long-lived NPM_TOKEN to OIDC (NPM Trusted Connections). Added necessary `id-token: write` permission alongside existing permissions, removed the expired `NPM_TOKEN`, and configured `NPM_CONFIG_PROVENANCE: true` to bypass traditional token checks. Co-authored-by: georgesmith46 <40513209+georgesmith46@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Fixes the failing release pipeline by switching from the expired NPM token to tokenless OIDC publishing with NPM Trusted Connections (provenance).
PR created automatically by Jules for task 697043906920752844 started by @georgesmith46