release: 0.11.0

[stainless-app]

Automated Release PR

0.11.0 (2026-08-01)

Full Changelog: v0.10.0...v0.11.0

Features

• api: align reply extraction contracts (#26) (9876ffd)
• api: api update (88a9325)
• api: api update (117f17e)

Bug Fixes

• make draft release lookup reliable (#21) (0b282f6)
• publish assets before immutable release (#18) (958f2c4)
• release: reuse verified CLI draft (#28) (278b326)
• use published Go SDK for releases (#27) (1df3aca)

Chores

• add FUNDING.yml pointing to xquik.com (cef589d)
• add per-file license evidence (ed6a2e2)
• internal: codegen related update (5825005)
• prepare v0.5.1 (8f1b0bf)
• prepare v0.5.2 (55d27ef)
• sync repo (407156b)
• update SDK settings (e20e024)
• update SDK settings (f5f5697)

Documentation

• add Contributor Covenant 2.1 Code of Conduct (#2192) (c253bcb)
• add DeepWiki badge (a352c58)
• add independence disclosure (c6cd7ac)
• clarify repository discovery (5b30a9e)
• map common CLI tasks (#11) (1b4522c)

Build System

• bundle third-party license notices (62ed5de)
• deps: bump actions/setup-go from 6.5.0 to 7.0.0 (#20) (95c49b3)
• use patched Go release (11b2524)

---

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

---

Summary by cubic

Release 0.11.0 aligns reply extraction in the API and improves release reliability. It also updates Go tooling (actions/setup-go v7, patched Go).

• New Features

  • Align reply extraction contracts in the API for consistent parsing.
  • General API updates for scraper responses.

• Bug Fixes

  • Harden release flow: reliable draft lookup, publish assets before immutable release, reuse verified CLI draft, and use the published Go SDK.

^{Written for commit c63a2f5. Summary will update on new commits.}

Note

Release version 0.11.0

Bumps the version string in pkg/cmd/version.go, .release-please-manifest.json, and CHANGELOG.md from 0.10.0 to 0.11.0.

^{Macroscope summarized c63a2f5.}

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Warning

Review limit reached

@stainless-app[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9114f4e8-8d43-40a7-a17e-a6c6db415bab

📥 Commits

Reviewing files that changed from the base of the PR and between 08a474c and c63a2f5.

📒 Files selected for processing (3)

• .release-please-manifest.json
• CHANGELOG.md
• pkg/cmd/version.go

---

_{Comment @coderabbitai help to get the list of available commands.}

[kriptoburak]

Closing as a duplicate release loop. PR #31 already merged the identical feature, fix, chore, documentation, and build changelog into version 0.10.0, and main now reports 0.10.0. The v0.10.0 GitHub release remains a draft without a tag, so regenerating the same backlog as 0.11.0 is not a useful release delta. Publish or otherwise resolve the existing draft before preparing the next version.