release: 0.90.0#604
Merged
stainless-app[bot] merged 9 commits intoMay 12, 2025
Merged
Conversation
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
ec0b1d7 to
4989256
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
24408c9 to
0da037e
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
5e8bc9a to
0da037e
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
c1a65ff to
b2a1763
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
6e617d2 to
0a90771
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
e94809b to
5dabc27
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
fd223f3 to
a94fb16
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
ca66576 to
cda7a4a
Compare
Contributor
Author
|
🤖 Release is at https://github.com/lithic-com/lithic-java/releases/tag/v0.90.0 🌻 |
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
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.90.0 (2025-05-12)
Full Changelog: v0.89.1...v0.90.0
⚠ 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
Chores
-Xbackend-threads=0option (3ac784c)Refactors
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