feat: update client for Apify OpenAPI spec v2-2026-06-23T113219Z - #6
Merged
Conversation
Bump API_SPEC_VERSION from v2-2026-06-18T095846Z to v2-2026-06-23T113219Z and the crate version 0.2.3 -> 0.2.4. The spec delta over the in-scope (documented, non-synchronous, reference-client-matching) API surface is fully additive: no new in-scope endpoints, no removed or renamed parameters. All in-scope endpoints, query/header parameters and request bodies declared by the new specification remain covered, and the response models stay forward-compatible (unknown fields are captured in each model's `extra` map where present, otherwise ignored by serde), so additive schema changes deserialize cleanly. No public-interface changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PysAtjinByQsN776iVSHX2
…gelog intro Address the three non-blocking docs/CHANGELOG nits from the orchestrator review of the v2-2026-06-23T113219Z spec bump: - README Quick start: explain that the call::<T> type parameter is the Actor input body type and the turbofish is only needed because None is otherwise untyped. - examples/get_account.rs: reword the monthly_usage_for_date comment to a user-facing description instead of referencing the OpenAPI query param. - CHANGELOG [0.2.4]: trim the intro paragraph to match the [0.2.0] house style (first sentences + Changed bullets). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PysAtjinByQsN776iVSHX2
github-actions
Bot
added
the
t-tooling
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
3 participants
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.
Summary
Synchronizes the Rust client with the latest Apify OpenAPI specification, bumping the targeted spec version from
v2-2026-06-18T095846Ztov2-2026-06-23T113219Z.A full parameter-level audit of every in-scope operation against the existing client confirmed the delta over the in-scope surface is fully additive — no new in-scope endpoints, no removed or renamed parameters, no path changes. The existing client already covers all in-scope endpoints, query/header params and request bodies; response models flatten unknown fields (or are serde-default tolerant), so additive schema changes deserialize cleanly. The documented out-of-scope set (synchronous
run-sync*,/v2/tools/*,/v2/browser-info, keyed-POST create variants) still matches theapify-client-jsreference scope.Changes
src/version.rs—API_SPEC_VERSIONbumped tov2-2026-06-23T113219Z.Cargo.toml— crate version0.2.3→0.2.4(additive spec sync; also exposed viaCLIENT_VERSION).CHANGELOG.md— new[0.2.4]entry.README.md— added a sentence near the firstcallexample explaining thecall::<T>(...)input-type parameter / turbofish.examples/get_account.rs— reworded a comment to a user-facing description ofmonthly_usage_for_date.Verification
cargo fmt --all -- --checkandcargo clippy --all-targets -- -D warningsclean.APIFY_TOKEN);cargo test --doc22 doctests pass; all 7 example programs run end-to-end via theTest examplesstep.No public-interface change.
Generated by Claude Code