chore: sync Java client with Apify OpenAPI spec v2-2026-08-27T071624Z - #16
Merged
Conversation
Pijukatel
pushed a commit
that referenced
this pull request
Aug 28, 2026
…mment The comment on the EI_EXPOSE_REP exclusion for ApifyResource-derived getters described the type change as landing "(this PR)", but that change shipped in an earlier PR. Reworded to describe the exclusion's rationale without a temporal reference that goes stale. Review follow-up from PR #16.
Pijukatel
force-pushed
the
claude/busy-newton-nq1gxv
branch
from
August 28, 2026 11:03
6f452df to
412fb49
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
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.
Syncs the client's pinned OpenAPI specification version from
v2-2026-08-14T072928Zto the latest publishedv2-2026-08-27T071624Z.The spec delta over this range (removal of
CreateActorRequest.pricingInfos, aRequestBase/RequestWithoutIdbundling fix, and validation/enum autofixes toActorNotice, theErrorTypeenum, and a couple of documented error responses) lands entirely on surfaces the client either does not model or handles generically (untypedcreatebody, string-based errortype/status), so no functional code change is required — only the version pin and metadata are updated.Changes
src/main/java/com/apify/client/Version.java: bumpAPI_SPEC_VERSIONtov2-2026-08-27T071624ZandCLIENT_VERSIONto0.6.2.pom.xml: bump project version to0.6.2in lockstep.README.md,CHANGELOG.md: update accordingly.spotbugs-exclude.xml: reword a stale temporal reference in a comment.Verification
spotless:check,compile + spotbugs:check, and-Prelease package(javadoc build) all clean.