Skip to content

release: 0.80.0 - #137

Merged
stainless-app[bot] merged 6 commits into
mainfrom
release-please--branches--main--changes--next
Jul 19, 2026
Merged

release: 0.80.0#137
stainless-app[bot] merged 6 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.80.0 (2026-07-19)

Full Changelog: v0.79.0...v0.80.0

Features

  • Add example to ProxyCheckRequest.url so API reference sample shows it (b32ed11)
  • Expose browser sessions on auth timeline events (00728f0)
  • managed-auth: add TS CUA worker contract (KERNEL-1456) (5951dfa)
  • stlc: configurable CI runner and private-production-repo support in workflow templates (77f3c17)

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
Managed-auth submit and response shape changes affect authentication integrations; legacy fields remain but callers should migrate to canonical fields/choices.

Overview
Release 0.80.0 bumps package version metadata and refreshes the OpenAPI spec reference; most functional change is in managed auth client types aligned with the updated API.

Managed auth responses and SSE follow events now expose canonical fields and choices (with new ManagedAuthField / ManagedAuthChoice types), documented as preferred over legacy discovered_fields, MFA/SSO/sign-in option shapes. Submit requests add field_values and selected_choice_id while keeping older submit fields during deprecation. Auth connection timeline events gain browser_session_id.

CI runs-on for build/lint/test now uses depot-ubuntu-24.04 for any repo under the stainless-sdks/ org prefix, not only kernel-go. Tests use a realistic proxy check URL example (https://example.com).

Reviewed by Cursor Bugbot for commit 248ffe0. Bugbot is set up for automated code reviews on this repo. Configure here.

@stainless-app

stainless-app Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

Download and unzip: 'https://pkg.stainless.com/s/kernel-go/00728f053c7a478222312c4baf73c39c82fc0156/source.zip'. Run 'go mod edit -replace github.com/kernel/kernel-go-sdk=/path/to/unzipped_directory'.

Expires at: Tue, 18 Aug 2026 19:17:04 GMT
Updated at: Sun, 19 Jul 2026 19:17:04 GMT

@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 943796d to d877a12 Compare July 17, 2026 00:05
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from d877a12 to c675ec9 Compare July 18, 2026 02:08
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from c675ec9 to 98f8d25 Compare July 18, 2026 06:14
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 98f8d25 to 248ffe0 Compare July 19, 2026 19:16

@rgarcia rgarcia left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

verified the generated managed auth timeline event includes BrowserSessionID with the browser_session_id JSON field; release checks are green.

@stainless-app
stainless-app Bot merged commit aa6f1cb into main Jul 19, 2026
10 checks passed
@stainless-app

stainless-app Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant