feat: update client for Apify OpenAPI spec v2-2026-06-23T113219Z - #5
Merged
Conversation
Synchronizes the Go client with the latest Apify OpenAPI specification, bumping the targeted spec version from v2-2026-06-18T095846Z to v2-2026-06-23T113219Z. The spec delta over the in-scope API surface is fully additive: no new in-scope endpoints and no removed or renamed parameters, so there are no breaking changes to the public interface. Response models already capture unmodelled API fields in their Extra maps, so additive schema fields decode cleanly. - Bump API_SPEC_VERSION to v2-2026-06-23T113219Z (version.go). - Bump CLIENT_VERSION 0.2.2 -> 0.2.3 (version.go). - Add CHANGELOG.md [0.2.3] entry; update spec-version mention in README.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PysAtjinByQsN776iVSHX2
Strengthen the BuildUserAgent doc comment to record that rendering the isAtHome flag lowercase (true/false) is a deliberate, cross-client-consistent choice: the JS reference interpolates a JS boolean (lowercase) and the Rust sibling emits "true"/"false", while the requirements' capitalized example is Python-specific and treated as illustrative rather than normative. Comment-only; no behavior change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PysAtjinByQsN776iVSHX2
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.
Summary
Synchronizes the Go 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 live spec (217 in-scope operations) 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 and parameters; response models capture unmodelled fields in their
Extramaps, so additive schema changes decode cleanly. The documented out-of-scope set (synchronousrun-sync*,/v2/tools/*,/v2/browser-info) still matches theapify-client-jsreference scope.Changes
version.go—API_SPEC_VERSIONbumped tov2-2026-06-23T113219Z;CLIENT_VERSION0.2.2→0.2.3(additive spec sync, no public-interface change).CHANGELOG.md— new[0.2.3]entry.README.md— updated the spec-version mention.common.go— strengthened theBuildUserAgentdoc comment to explicitly record that theisAtHomeflag is rendered lowercase (true/false) for cross-client consistency with the JS reference and the Rust sibling (the requirements' capitalized example is Python-specific). Comment-only.Verification
gofmt -l .,go vet ./...,golangci-lint run,go build ./...clean.APIFY_TOKEN; the standaloneTest examplesstep (all 7 example programs + doc snippets) passes end-to-end.No public-interface change.
Generated by Claude Code