release: 0.19.0#35
Conversation
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: This is an automated release PR with only internal/chore changes to a bootstrap script, not a change to kernel API endpoints or Temporal workflows. To monitor this PR anyway, reply with |
|
🧪 Testing To try out this version of the SDK: Expires at: Thu, 11 Jun 2026 12:40:34 GMT |
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b243e2b to
6dac974
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
6dac974 to
9f751f0
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
9f751f0 to
b9f3593
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes 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 b9f3593. Configure here.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b9f3593 to
6c7cd27
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
6c7cd27 to
277c1f0
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
277c1f0 to
459e311
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
459e311 to
05ff9ad
Compare
defaultHTTPClient performed an unchecked type assertion on http.DefaultTransport, which panicked for any caller that had wrapped the global transport (e.g. otelhttp.NewTransport for distributed tracing). When the assertion fails, fall back to the wrapped RoundTripper as-is — preserving the caller's wrapping at the cost of ResponseHeaderTimeout, which is strictly better than panicking.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
05ff9ad to
b1c2fe6
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b1c2fe6 to
20b9929
Compare
|
🤖 Release is at https://github.com/kernel/hypeman-go/releases/tag/v0.19.0 🌻 |
1 participant
Automated Release PR
0.19.0 (2026-05-12)
Full Changelog: v0.18.0...v0.19.0
Features
Bug Fixes
Chores
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
Medium risk because it changes default HTTP behavior (new client/transport timeout) and alters debug logging to redact headers, which could affect connectivity and troubleshooting behavior across all SDK consumers.
Overview
Release v0.19.0 updates generated SDK metadata/versioning and refreshes the OpenAPI spec reference.
Adds a new default
http.Clientthat cloneshttp.DefaultTransport(when possible) to set aResponseHeaderTimeout, and extendsDefaultClientOptionsto supportHYPEMAN_CUSTOM_HEADERSfor injecting arbitrary headers.Expands
Instanceresponses with lifecycle tracking fields (current_phase,current_phase_since,phase_durations_ms), redacts sensitive headers inoption.WithDebugLog, and refactors internal encoder cache keys to avoid embeddingreflect.Type(plus a small bootstrap script robustness tweak).Reviewed by Cursor Bugbot for commit 20b9929. Bugbot is set up for automated code reviews on this repo. Configure here.