Use OIDC for npm publish #162
                
     Merged
            
            
          
  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.
  
    
  
    
Note
Updates the release workflow to Node.js 22 and switches npm publishing to OIDC by granting id-token and removing the NPM_TOKEN secret.
.github/workflows/release.yml)actions/setup-nodetov6and Node version to22.xacross jobs.registry-urlwhere missing; keep pnpm caching.permissions: id-token: write.NPM_TOKENto an empty string to enable OIDC-based npm publish via Changesets.^11.6during release job.Written by Cursor Bugbot for commit 124ce8e. This will update automatically on new commits. Configure here.