Skip to content

docs(aso): clarify list_builds limit=200 is page size, not a cap #24

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.

Sign up for GitHub

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
setoelkahfi merged 1 commit into from
Oct 11, 2026
Merged

docs(aso): clarify list_builds limit=200 is page size, not a cap #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions crates/aso/src/build.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,13 @@ pub trait BuildsApi {
/// Pass `&BuildFilter::default()` for every build, or set fields to
/// narrow by build number, pre-release (marketing) version, or
/// processing state.
///
/// The `limit=200` this sends is a *page size*, not a ceiling on the
/// result: [`Client::list_all`] follows Apple's `links.next` cursor until
/// the collection is exhausted, so an app with more than 200 builds still
/// returns all of them — 200 is just the largest page ASC allows for this
/// collection, which keeps the round-trip count down. Do not read the
/// vector's length as "the 200 most recent builds."
async fn list_builds(&self, app_id: &str, filter: &BuildFilter) -> Result<Vec<Build>>;

/// `GET /v1/builds/{id}` — a single build by its App Store Connect id.
Expand Down
Loading