Skip to content

feat: update client for Apify OpenAPI spec v2-2026-06-23T113219Z - #5

Merged
Pijukatel merged 2 commits into
masterfrom
claude/inspiring-shannon-60upn4
Jun 24, 2026
Merged

feat: update client for Apify OpenAPI spec v2-2026-06-23T113219Z#5
Pijukatel merged 2 commits into
masterfrom
claude/inspiring-shannon-60upn4

Conversation

@Pijukatel

Copy link
Copy Markdown
Collaborator

Summary

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.

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 Extra maps, so additive schema changes decode cleanly. The documented out-of-scope set (synchronous run-sync*, /v2/tools/*, /v2/browser-info) still matches the apify-client-js reference scope.

Changes

  • version.goAPI_SPEC_VERSION bumped to v2-2026-06-23T113219Z; CLIENT_VERSION 0.2.20.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 the BuildUserAgent doc comment to explicitly record that the isAtHome flag 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.
  • Unit tests pass; integration tests (26 funcs) pass against the live API with APIFY_TOKEN; the standalone Test examples step (all 7 example programs + doc snippets) passes end-to-end.

No public-interface change.


Generated by Claude Code

claude added 2 commits June 23, 2026 21:57
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
@Pijukatel Pijukatel added this to the v0 milestone Jun 24, 2026
@Pijukatel Pijukatel added the adhoc Ad-hoc unplanned task added during the sprint. label Jun 24, 2026
@github-actions github-actions Bot added the t-tooling Issues with this label are in the ownership of the tooling team. label Jun 24, 2026
@Pijukatel
Pijukatel merged commit 4b5f7fb into master Jun 24, 2026
2 of 3 checks passed
@Pijukatel
Pijukatel deleted the claude/inspiring-shannon-60upn4 branch July 8, 2026 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants