release: 0.1.0-alpha.12 #113
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![stainless-app[bot]](https://avatars.githubusercontent.com/in/378072?s=60&v=4){kind=small}
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
5f178b9 to
ce52e15
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
5a5343a to
134e615
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b54d299 to
9372b90
Compare
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
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
a06334e to
d2fa723
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
37c240f to
d1cacea
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
6fc34f8 to
0e78fa9
Compare
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
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
cc31857 to
710b626
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
fa5de3f to
9ebe803
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
8afe3d0 to
5d83cd2
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
10dfb1f to
21777c4
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
494f464 to
6e8b2be
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
32e2e4c to
69737c8
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
7ad9d23 to
2595481
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
24e891a to
7d83620
Compare
|
Note: this release PR has been open for more than 60 days. Until this PR is merged, we will temporarily stop pushing codegen updates due to changes to Stainless' codegen. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.1.0-alpha.12 (2025-07-01)
Full Changelog: v0.1.0-alpha.11...v0.1.0-alpha.12
⚠ BREAKING CHANGES
AutoPagerclass on a specific*Pageor*PageAsynctype, then you should instead reference the sharedAutoPagerandAutoPagerAsynctypes, under thecorepackageAutoPagerAsyncnow has different usage. You can call.subscribe(...)on the returned object instead to get called back each page item. You can also callonCompleteFuture()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 earlygetNextPageorgetNextPageParams:nextPage()andnextPageParams()hasNextPage()before calling these, since they will throw if it's impossible to get another page)Features
withOptionsmethod (9ebe803)Bug Fixes
withOptionsusage when original is gc'd (2595481)@MustBeClosedfor future returning methods (0e78fa9)Chores
Documentation
Refactors
ClientOptionsTestchange (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