chore: sync Java client with Apify OpenAPI spec v2-2026-08-14T072928Z - #15
Open
Pijukatel wants to merge 2 commits into
Open
chore: sync Java client with Apify OpenAPI spec v2-2026-08-14T072928Z#15Pijukatel wants to merge 2 commits into
Pijukatel wants to merge 2 commits into
Conversation
Bump Version.API_SPEC_VERSION for the doc-only spec update that documents the already-implemented Task.isPublic / Task.publicConfig fields and the TaskPublicConfig schema (no new endpoints, no client code change). Correct doc comments that predated this spec version: Task.getIsPublic() and TaskPublicConfig no longer claim to be undocumented, and TaskClient.unpublish()'s doc comment (and the matching integration-test comment) no longer claims it needs less permission than publish() - the spec states both require write permission to the task's Actor, verified against the reference JS client and the live API. Trim two overlong comments (CompressionTest's brotli-fallback-gap rationale, TaskPublicConfig.getInputSchemaFields' restated Javadoc) to match the coding rules' conciseness requirement. Bump CLIENT_VERSION to 0.6.1 and sync the stale version strings in README.md (client version and API spec version were two releases behind).
github-actions
Bot
added
t-tooling
The Task-fields description of getIsPublic() still claimed the field was "not part of the documented Task schema... but the API returns it in practice" - the same false claim already corrected elsewhere in this PR, just missed at this second occurrence. Also note categorization explicitly as the one undocumented TaskPublicConfig field, for consistency with the class-level Javadoc fix.
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-08-14T072928Z. That spec revision documents the already-implementedTask.isPublic/Task.publicConfigfields and theTaskPublicConfigschema (no new endpoints, no client code change).Also corrects doc comments that predated this spec version:
Task.getIsPublic()andTaskPublicConfigno longer claim to be undocumented.TaskClient.unpublish()'s doc comment (and the matching integration-test comment) no longer claims it needs less permission thanpublish()- the spec states both require write permission to the task's Actor, which I verified against the reference JS client and the live API.CompressionTest's brotli-fallback-gap rationale,TaskPublicConfig.getInputSchemaFields' restated Javadoc).CLIENT_VERSIONbumped to0.6.1; also synced stale version strings inREADME.md(client version and API spec version were two releases behind).