chore: sync Go client with Apify OpenAPI spec v2-2026-06-29T142258Z#9
Merged
Conversation
Bump API_SPEC_VERSION to v2-2026-06-29T142258Z (from v2-2026-06-25T142310Z) and CLIENT_VERSION to 0.4.2. An independent operation- and parameter-level audit against the new spec, with the JavaScript reference client as the parity authority for the in-scope surface, found no change to the in-scope API: the only underlying spec change in this window relocates the outputRecordKey query parameter (wire contract byte-for-byte identical) and edits prose on the out-of-scope run-sync endpoints. Version bump only, with no public interface change, so this is a patch release.
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 Apify Go client with OpenAPI specification
v2-2026-06-29T142258Z(fromv2-2026-06-25T142310Z) and bumpsCLIENT_VERSIONto0.4.2.An independent operation- and parameter-level audit of every in-scope operation against the new specification — with the JavaScript reference client (
apify-client-js/src) as the parity authority for which endpoints/parameters are in scope — found no change to the in-scope API surface: same paths, operations, query/header parameters, request bodies and response schemas. The sole underlying spec change between the two versions was theapify-docscommitb03fbc9("Clarify OUTPUT record vs output object in sync endpoints"), which relocates theoutputRecordKeyquery parameter (its wire contract is byte-for-byte identical) and edits prose on the out-of-scoperun-syncendpoints — no in-scope effect. So the spec bump is version-only, and this is a SemVer patch with no public interface change.The endpoints the client does not cover (
run-sync/run-sync-get-dataset-items,/v2/tools/decode-and-verify&encode-and-sign,/v2/browser-info, and the keyedPOSTcreate variants that duplicate coveredPUTwrites) remain confirmed out of scope — the reference client exposes none of them. The pay-per-eventChargeoperation (POST /v2/actor-runs/{runId}/charge) is already covered and matches the spec (eventName+countbody withidempotency-keyheader).Changes
version.go—API_SPEC_VERSION→v2-2026-06-29T142258Z;CLIENT_VERSION0.4.1→0.4.2.README.md— updated the Versioning-section spec reference to match.CHANGELOG.md— new[0.4.2]entry documenting the spec sync, the audit outcome, and the underlying spec commit.Verification
gofmt -l .clean;go vet ./...clean;go build ./...clean.go test ./...against the live API (APIFY_TOKEN) — unit tests and the integration + example/doc-snippet suite all pass.Generated by Claude Code