Skip to content

release: 0.1.0-alpha.12#114

Merged
stainless-app[bot] merged 33 commits into
mainfrom
release-please--branches--main--changes--next
Jan 7, 2026
Merged

release: 0.1.0-alpha.12#114
stainless-app[bot] merged 33 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jan 7, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.1.0-alpha.12 (2026-01-07)

Full Changelog: v0.1.0-alpha.11...v0.1.0-alpha.12

⚠ BREAKING CHANGES

  • client: extract auto pagination to shared classes
  • client: Migration: - If you were referencing the AutoPager class on a specific *Page or *PageAsync type, then you should instead reference the shared AutoPager and AutoPagerAsync types, under the core package
    • AutoPagerAsync now has different usage. You can call .subscribe(...) on the returned object instead to get called back each page item. You can also call onCompleteFuture() to get a future that completes when all items have been processed. Finally, you can call .close() on the returned object to stop auto-paginating early
    • If you were referencing getNextPage or getNextPageParams:
      • Swap to nextPage() and nextPageParams()
      • Note that these both now return non-optional types (use hasNextPage() before calling these, since they will throw if it's impossible to get another page)

Features

  • api: add test evaluation method (e8d8121)
  • api: api update (225da0c)
  • api: api update (a089f7f)
  • api: api update (e48acb3)
  • api: manual updates (fd5752e)
  • client: add a withOptions method (9ebe803)
  • client: allow providing some params positionally (134e615)
  • client: extract auto pagination to shared classes (d2fa723)
  • client: implement per-endpoint base URL support (710b626)

Bug Fixes

  • ci: release-doctor — report correct token name (6e8b2be)
  • client: bump max requests per host to max requests (5 -> 64) (21777c4)
  • client: don't close client on withOptions usage when original is gc'd (2595481)
  • client: remove @MustBeClosed for future returning methods (0e78fa9)

Chores

  • ci: enable for pull requests (5d83cd2)
  • ci: only run for pushes and fork pull requests (69737c8)
  • docs: grammar improvements (d1cacea)
  • internal: codegen related update (9c97d6d)
  • internal: codegen related update (d2c9111)
  • internal: codegen related update (942316f)
  • internal: codegen related update (9b5aa41)
  • internal: codegen related update (4881e6f)
  • internal: codegen related update (ce52e15)
  • sync repo (390e75d)

Documentation

  • add Spring AI sample application (4cc1fb8)
  • remove or fix invalid readme examples (9372b90)

Refactors

  • internal: minor ClientOptionsTest change (7d83620)

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 Bot added 30 commits May 9, 2025 03:00
refactor(client)!: refactor async auto-pagination
refactor(client)!: rename `getNextPage{,Params}` to `nextPage{,Params}`
refactor(client)!: swap `nextPage{,Params}` to return non-optional

# Migration

- If you were referencing the `AutoPager` class on a specific `*Page` or `*PageAsync` type, then you should instead reference the shared `AutoPager` and `AutoPagerAsync` types, under the `core` package
- `AutoPagerAsync` now has different usage. You can call `.subscribe(...)` on the returned object instead to get called back each page item. You can also call `onCompleteFuture()` to get a future that completes when all items have been processed. Finally, you can call `.close()` on the returned object to stop auto-paginating early
- If you were referencing `getNextPage` or `getNextPageParams`:
   - Swap to `nextPage()` and `nextPageParams()`
   - Note that these both now return non-optional types (use `hasNextPage()` before calling these, since they will throw if it's impossible to get another page)

There are examples and further information about pagination in the readme.
Refactor `HttpRequest` to always take a `baseUrl`, instead of storing this in `OkHttpClient`. This allows better reuse of `OkHttpClient` when changing the `baseUrl`.
@stainless-app stainless-app Bot merged commit 4f0a782 into main Jan 7, 2026
5 checks passed
@stainless-app stainless-app Bot deleted the release-please--branches--main--changes--next branch January 7, 2026 17:54
@stainless-app

stainless-app Bot commented Jan 7, 2026

Copy link
Copy Markdown
Contributor Author

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