release: 2.0.0 #466
Open
release: 2.0.0 #466
+27,114
−14,948
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
21b1c8d to
bb85d0d
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
050ad47 to
7200cf6
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
1f89942 to
4587737
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
eb0d6ac to
4bf868a
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
7c0b462 to
f623bca
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
7367a5a to
f623bca
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
013b2fe to
6cdb671
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
3 times, most recently
from
6315bcf to
1da6c92
Compare
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
2.0.0 (2025-05-10)
Full Changelog: v1.6.1...v2.0.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
deploymentModelparams (bb85d0d)Chores
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