release: 0.78.0

[stainless-app]

Automated Release PR

0.78.0 (2026-07-13)

Full Changelog: v0.76.0...v0.78.0

Features

• Add exact-match name filter to list endpoints (dd94a68)
• Add name-only rename for profiles and proxies (2fe4124)
• Auto-default refresh_on_profile_update when browser pool profile changes (adaf037)
• Document name uniqueness and query match semantics (670f7c3)
• Expose telemetry exception message in API/SDK (ddf0a65)
• Make the browser pool OpenAPI contract truthful (cfc4539)
• Persist and echo deployment source identity (f8605df)
• Support multiple audit log method exclusions (a3b8713)

Bug Fixes

• ci: bump @arethetypeswrong/cli to ^0.18.0 and run CI workflows on Node 24 (6fca519)

Documentation

• openapi: describe unified concurrency limit, deprecate max_pooled_sessions (CUS-275) (37d3e27)

---

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
The audit log exclude_method type change from string to string[] is a TypeScript breaking change for callers; the rest is additive API surface and documentation from OpenAPI codegen.

Overview
Release 0.78.0 bumps the package and OpenAPI-backed SDK from 0.76.0 to 0.78.0 (127 endpoints).

New client methods: client.profiles.update and client.profiles.update / client.proxies.update (PATCH, name-only rename), with exported ProfileUpdateParams, ProxyUpdateParams, and response types.

List params gain an optional name exact-match filter on API keys, browser pools, extensions, profiles, proxies, and projects; several resources also clarify query vs name semantics. Audit log exclude_method is now Array<string> instead of a single string.

Deployments responses add read-only source_type, source_url, source_ref, source_path, and source_checksum. Browser pool create/update docs describe replace-vs-omit fields, refresh_on_profile_update defaults when the profile changes, and chrome policy size limits. Org/project limits types document unified concurrency (pooled browsers count toward max_concurrent_sessions; max_pooled_sessions deprecated). Telemetry console error events document human-readable text. Managed auth proxy-by-name docs note exact-match and ambiguity rules.

CI and publish workflows use Node 24; @arethetypeswrong/cli is bumped to ^0.18.0. Tests are updated for the new params and audit-log array shape.

^{Reviewed by Cursor Bugbot for commit 7d7425a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[stainless-app]

🧪 Testing

To try out this version of the SDK:

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

Expires at: Wed, 12 Aug 2026 16:14:46 GMT
Updated at: Mon, 13 Jul 2026 16:14:46 GMT

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ce28e66. Configure here.}

[stainless-app]

Release version edited manually

The Pull Request version has been manually set to 0.78.0 and will be used for the release.

If you instead want to use the version number 0.77.0 generated from conventional commits, just remove the label autorelease: custom version from this Pull Request.

[IlyaasK]

lgtm

[stainless-app]

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

[firetiger-agent]

Monitoring impaired: HTTP logs source unavailable

Status: PR merged 2026-07-13; post-deploy monitoring unable to proceed.

Issue: The plan relies on Railway HTTP logs to validate post-deploy API error rates. The primary data source (opentelemetry/logs/railway-http-logs) went stale on 2026-07-05 and has been offline for 9+ days. Queries against this table return no data within the monitoring window.

Impact: Cannot confirm or deny whether API error rates remain within baseline post-merge. Monitoring is blind to:

• POST /org/limits 5xx rate
• PATCH /org/limits 5xx rate
• PATCH /projects/{id}/limits 400 rate
• Overall API error rate

Recommended action: Wait for Railway HTTP logs to resume flowing, or update the monitoring plan to query an alternative API health signal (e.g., Datadog, another observability backend). This is a data availability issue, not a code regression.

View monitor