release: 0.32.0

[stainless-app]

Automated Release PR

0.32.0 (2026-02-07)

Full Changelog: v0.31.2...v0.32.0

Features

• auth: add reauth circuit breaker logic (917dc3d)

Chores

• switch npm publish to OIDC auth in stainless config (403d222)

---

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

---

Note

Medium Risk
Changes the release/publish pipeline and authentication method for npm publishing, which can break releases if misconfigured. SDK type change is additive and low risk.

Overview
Bumps the SDK release to 0.32.0 (manifest, package.json, src/version.ts, and changelog) and refreshes generated stats/spec metadata.

Publishing is switched to support npm OIDC: GitHub Actions now requests id-token permission, the workflows stop injecting NPM_TOKEN, bin/check-release-environment no longer requires a token, and bin/publish-npm can publish via OIDC (falling back to NPM_TOKEN when not running in Actions) using an OIDC-compatible npm binary.

The auth models add an optional can_reauth_reason field on both AuthAgent and ManagedAuth to explain why automatic re-auth is or isn’t possible.

^{Written by Cursor Bugbot for commit 6a8bd0c. This will update automatically on new commits. Configure here.}

[stainless-app]

🧪 Testing

To try out this version of the SDK, run:

npm install 'https://pkg.stainless.com/s/kernel-typescript/917dc3d4ed691b16b969fb4f723d45dc0324d896/dist.tar.gz'

Expires at: Mon, 09 Mar 2026 18:16:34 GMT
Updated at: Sat, 07 Feb 2026 18:16:34 GMT

[masnwilliams]

lgtm

[stainless-app]

🤖 Release is at https://github.com/kernel/kernel-node-sdk/releases/tag/v0.32.0 🌻

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Missing --provenance flag breaks OIDC npm publishing

High Severity

The npm publish command is missing the --provenance flag required for OIDC-based authentication. When NPM_TOKEN is not set, the script falls through to OIDC mode but the publish command on line 70 doesn't include --provenance. Without this flag, npm won't use the OIDC token for authentication, causing the publish to fail with an authentication error. The comment on line 65 says "Install OIDC compatible npm version" but the actual publish command doesn't enable OIDC authentication.

 

[cursor]

Release environment check script now performs no validation

Low Severity

The check-release-environment script now creates an empty errors array, checks if it has elements (it never will), and always outputs "The environment is ready to push releases!" without validating anything. This is dead code that provides false assurance. The release doctor workflow still invokes this script expecting it to catch configuration issues, but it will always succeed regardless of the actual environment state. The script either needs OIDC-related checks or removal.