Skip to content

release: 5.0.1#10

Open
stainless-app[bot] wants to merge 4 commits into
mainfrom
release-please--branches--main--changes--next
Open

release: 5.0.1#10
stainless-app[bot] wants to merge 4 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app Bot commented May 8, 2026

Automated Release PR

5.0.1 (2026-05-13)

Full Changelog: v5.0.0...v5.0.1

Bug Fixes

  • go: avoid panic when http.DefaultTransport is wrapped (f96d2e8)

Chores

  • redact api-key headers in debug logs (7672988)

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

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app Bot commented May 8, 2026

🧪 Testing

To try out this version of the SDK:

Download and unzip: 'https://pkg.stainless.com/s/beeper-desktop-api-go/3873bc6d3e5bc59ab5815e8c72157544771ae0fe/source.zip'. Run 'go mod edit -replace github.com/beeper/desktop-api-go/v5=/path/to/unzipped_directory'.

Expires at: Fri, 12 Jun 2026 02:43:10 GMT
Updated at: Wed, 13 May 2026 02:43:10 GMT

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 stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 972a52e to 9135384 Compare May 8, 2026 03:43
stainless-app Bot added 2 commits May 13, 2026 02:40
Pin all GitHub Actions referenced in generated workflows (both
first-party `actions/*` and third-party) to immutable commit SHAs.
Updating pinned actions is now a deliberate codegen-side bump rather
than implicit on every workflow run.
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 9135384 to d9d4269 Compare May 13, 2026 03:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

0 participants