-
Notifications
You must be signed in to change notification settings - Fork 1
release: 0.57.0 #403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
stainless-app
merged 18 commits into
main
from
release-please--branches--main--changes--next
May 22, 2025
Merged
release: 0.57.0 #403
stainless-app
merged 18 commits into
main
from
release-please--branches--main--changes--next
May 22, 2025
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
177738c to
fb2505d
Compare
cdbbd7b to
f72c4ad
Compare
703185f to
31827ac
Compare
36d0ae6 to
7db8db6
Compare
4be82df to
ddcc77e
Compare
ac06745 to
68dcdd8
Compare
a195850 to
7f2fb10
Compare
52321b1 to
2b4abdf
Compare
3f59e75 to
b085373
Compare
9f4dc4c to
9df208b
Compare
b7e7d83 to
7ddd872
Compare
b5a36c3 to
7ddd872
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.
a2583f3 to
9affbde
Compare
b2ebd6b to
9460c52
Compare
4790c69 to
fca1dab
Compare
ea1993c to
7b5fb07
Compare
c1db2f2 to
1f7beef
Compare
Contributor
Author
|
🤖 Release is at https://github.com/orbcorp/orb-java/releases/tag/v0.57.0 🌻 |
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.57.0 (2025-05-22)
Full Changelog: v0.56.0...v0.57.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
Bug Fixes
Performance Improvements
Chores
-Xbackend-threads=0option (b085373)Documentation
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