release: 0.24.0 - #47
Conversation
Open Hypeman SDK promotion PRs automatically
Stainless-Generated-From: 0e041191e688420b16a12cbf61cb9203c4143311
Stainless-Generated-From: 723add2f9bed6ca947969e9efc9f62a874c6d56e
ci: use one PR for Hypeman Go releases
8f90238 to
fa28166
Compare
|
🧪 Testing To try out this version of the SDK: Expires at: Fri, 11 Sep 2026 14:15:50 GMT |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| func (r IngressRuleRequestHeaderAuth) RawJSON() string { return r.JSON.raw } | ||
| func (r *IngressRuleRequestHeaderAuth) UnmarshalJSON(data []byte) error { | ||
| return apijson.UnmarshalRoot(data, r) | ||
| } |
There was a problem hiding this comment.
Missing auth ToParam helper
Medium Severity
IngressRuleRequestHeaderAuth adds RawJSON and UnmarshalJSON plus a matching IngressRuleRequestHeaderAuthParam, but no ToParam method. Peer nested objects such as IngressMatch, IngressTarget, HealthCheckExec, and HealthCheckHTTP all expose ToParam, so response-to-request conversion for header auth is inconsistent with the rest of the SDK.
Reviewed by Cursor Bugbot for commit fa28166. Configure here.
Stainless-Generated-From: 76bbcd732af9bf9808b04f1321480628b62553a6
fa28166 to
7727261
Compare
7727261 to
f8f5daf
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f8f5daf. Configure here.
| --title 'chore: resolve SDK promotion conflict' --body-file "$body") | ||
| echo "::error title=SDK promotion conflict::Resolve the recovery PR: $recovery_url" | ||
| exit 1 | ||
| } |
There was a problem hiding this comment.
Conflict helper assumes active merge
Medium Severity
open_conflict_pr always runs git merge --abort before opening a recovery PR. That only works when git merge left an in-progress conflicted merge. If merge fails for other reasons (for example unrelated histories), there is no MERGE_HEAD, abort fails under set -e, and the recovery PR is never created.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit f8f5daf. Configure here.
|
🤖 Release is at https://github.com/kernel/hypeman-go/releases/tag/v0.24.0 🌻 |
2 participants
Automated Release PR
0.24.0 (2026-08-12)
Features
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
Reworks release/promotion CI that writes production branches and creates GitHub releases, so misconfiguration could block or mishandle publishes. SDK API changes are additive.
Overview
Releases
0.24.0with three SDK features and a redesigned staging→production release flow.SDK features
client.Pushesto create/list/get jobs that export ready images to remote registries (optional per-push credentials).request_header_authon ingress rules so proxying requires an exact custom header/value.qemu-microvmhypervisor backend across instance create/restore/fork and related types (with documented device/hotplug limits).Release automation
next(with conflict recovery PRs) instead of fast-forwardingmain.next→mainand creates the GitHub release on merge, using pinned Stainless release-please tooling and closing legacystainless/releasePRs.Reviewed by Cursor Bugbot for commit f8f5daf. Bugbot is set up for automated code reviews on this repo. Configure here.