chore: sync Java client with Apify OpenAPI spec v2-2026-09-10T091137Z - #18
Open
Pijukatel wants to merge 1 commit into
Open
chore: sync Java client with Apify OpenAPI spec v2-2026-09-10T091137Z#18Pijukatel wants to merge 1 commit into
Pijukatel wants to merge 1 commit into
Conversation
apify-service-account
added
the
t-tooling
Pijukatel
pushed a commit
that referenced
this pull request
Sep 11, 2026
The version bump in PR #18 missed README.md: pom.xml, Version.java, and CHANGELOG.md were updated to 0.6.4 but the Maven/Gradle snippets and the documented CLIENT_VERSION/API_SPEC_VERSION values still referenced 0.6.3 and the previous spec version. Update all four spots to match. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RSRQiKuykuXATHK8g1FDqU
Pijukatel
added
the
adhoc
Claude
Bumps Version.API_SPEC_VERSION to v2-2026-09-10T091137Z and the client version to 0.6.4. The only spec change since the last sync (apify-docs #2965) documents pagination response headers (adding X-Apify-Pagination-Desc) on 17 list endpoints and the offset/limit/desc query parameters on the webhook-dispatches-of-a-webhook list endpoint. The client already sends those query parameters via the shared AbstractCollectionClient/ListOptions plumbing, and additive response headers cannot break it, so no functional client change is required beyond the version bump.
Pijukatel
force-pushed
the
chore/spec-sync-v2-2026-09-10T091137Z
branch
from
September 11, 2026 22:03
68f47b5 to
0f303b6
Compare
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.
Bumps
Version.API_SPEC_VERSIONtov2-2026-09-10T091137Zand the client version to0.6.4.The only spec change since the last sync is apify-docs#2965, which documents pagination response headers (adding
X-Apify-Pagination-Desc) on 17 list endpoints and theoffset/limit/descquery parameters on the webhook-dispatches-of-a-webhook list endpoint. The client already sends those query parameters via the sharedAbstractCollectionClient/ListOptionsplumbing, and additive response headers cannot break it, so no functional code change is needed beyond the version bump.See
CHANGELOG.mdfor details.