Skip to content

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Apr 24, 2025

Automated Release PR

0.10.0 (2025-08-22)

Full Changelog: v0.9.0...v0.10.0

⚠ 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

  • add retryable exception (d8e7b05)
  • client: add {QueryParams,Headers}#put(String, JsonValue) methods (2ed0bd5)
  • client: add a withOptions method (0fd4355)
  • client: add https config options (6730e8b)
  • client: allow configuring env via system properties (66d1af9)
  • client: allow providing some params positionally (decbdbc)
  • client: ensure compat with proguard (976cf03)
  • client: extract auto pagination to shared classes (e9248c0)
  • client: implement per-endpoint base URL support (729a979)

Bug Fixes

  • ci: release-doctor — report correct token name (76e5e15)
  • client: accidental mutability of some classes (95b2515)
  • client: bump max requests per host to max requests (5 -> 64) (ce8a40c)
  • client: don't close client on withOptions usage when original is gc'd (c17580b)
  • client: ensure error handling always occurs (53fa1ca)
  • client: r8 support (f06bc35)
  • client: remove @MustBeClosed for future returning methods (5d19342)

Performance Improvements

  • internal: make formatting faster (80067f7)

Chores

  • ci: add build job (3e6fe1e)
  • ci: bump actions/setup-java to v4 (3769b89)
  • ci: enable for pull requests (3e67a54)
  • ci: ensure docs generation always succeeds (266ed1d)
  • ci: only run for pushes and fork pull requests (7437b68)
  • ci: only use depot for staging repos (fc25618)
  • ci: reduce log noise (0b93a6a)
  • client: refactor closing / shutdown (09819df)
  • docs: grammar improvements (f8dd702)
  • example: fix run example comment (ab5aa6c)
  • increase max gradle JVM heap to 8GB (00333f4)
  • internal: add async lock helper (5904a7a)
  • internal: allow running specific example from cli (1f6ea51)
  • internal: bump ci test timeout (3d46fc5)
  • internal: codegen related update (23e9c7b)
  • internal: codegen related update (ee51402)
  • internal: dynamically determine included projects (8129561)
  • internal: java 17 -> 21 on ci (fc13394)
  • internal: reduce proguard ci logging (2c716b1)
  • internal: refactor delegating from client to options (70faee4)
  • internal: remove flaky -Xbackend-threads=0 option (96fdae2)
  • internal: remove unnecessary [...] in [@see](https://github.com/see) (a0ef543)
  • internal: support passing arguments to test script (87f7a5f)
  • internal: support running formatters directly (6a03471)
  • internal: update comment in script (b73560b)
  • internal: update java toolchain (7c8e53c)
  • remove memory upper bound from publishing step (1efb5d6)
  • update @stainless-api/prism-cli to v5.15.0 (dba7eae)

Documentation

Refactors

  • internal: minor ClientOptionsTest change (2e7263e)

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 stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 3aba691 to fc25618 Compare April 24, 2025 03:12
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from f141119 to fc13394 Compare April 24, 2025 03:15
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from bee2017 to 7c8e53c Compare May 2, 2025 04:03
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 55acb62 to 96fdae2 Compare May 7, 2025 05:49
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 1ffcfb2 to decbdbc Compare May 9, 2025 05:14
@stainless-app stainless-app bot changed the title release: 0.9.1 release: 0.10.0 May 9, 2025
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 267aa78 to decbdbc Compare May 9, 2025 05:14
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.
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 2ad84cd to e9248c0 Compare May 9, 2025 05:25
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 00b8b44 to f8dd702 Compare May 22, 2025 02:59
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 0dab993 to 5d19342 Compare May 29, 2025 04:55
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 force-pushed the release-please--branches--main--changes--next branch from fa210fd to 729a979 Compare June 12, 2025 04:44
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 52028bd to 0fd4355 Compare June 13, 2025 03:24
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from cba6c1a to 3e67a54 Compare June 17, 2025 07:41
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 72364ac to ce8a40c Compare June 24, 2025 04:19
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 8007685 to 76e5e15 Compare June 27, 2025 02:46
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 09a45da to 5904a7a Compare August 5, 2025 09:51
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 28e63b5 to ab5aa6c Compare August 6, 2025 10:16
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 264fdb6 to 00333f4 Compare August 8, 2025 04:11
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e7b7ee2 to dba7eae Compare August 9, 2025 05:45
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from eafa84f to b73560b Compare August 9, 2025 05:59
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from d7b0212 to e235503 Compare August 13, 2025 02:24
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e235503 to 526bf4b Compare August 13, 2025 16:55
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 526bf4b to 5b69fb5 Compare August 13, 2025 18:47
Running the formatter through Spotless is slow because Spotless synchronously runs the formatter on each file. Running the formatter directly parallelizes the formatting across cores.
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 5b69fb5 to 7c77c5a Compare August 13, 2025 21:40
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 7c77c5a to e6c1788 Compare August 14, 2025 19:29
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e6c1788 to 56054ee Compare August 20, 2025 17:15
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 56054ee to 2f5f705 Compare August 20, 2025 17:52
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 2f5f705 to e591de1 Compare August 21, 2025 19:14
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e591de1 to 11016c4 Compare August 22, 2025 01:37
@stainless-app stainless-app bot closed this Aug 22, 2025
@stainless-app stainless-app bot deleted the release-please--branches--main--changes--next branch August 22, 2025 20:13
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.

0 participants