Skip to content

chore: sync Go client with Apify OpenAPI spec v2-2026-07-01T115402Z#11

Open
Pijukatel wants to merge 1 commit into
masterfrom
claude/laughing-knuth-0fksfa
Open

chore: sync Go client with Apify OpenAPI spec v2-2026-07-01T115402Z#11
Pijukatel wants to merge 1 commit into
masterfrom
claude/laughing-knuth-0fksfa

Conversation

@Pijukatel

Copy link
Copy Markdown
Collaborator

Summary

Synchronizes the Go client with the latest Apify OpenAPI specification v2-2026-07-01T115402Z (previously v2-2026-06-30T091455Z).

An operation- and parameter-level audit of every in-scope endpoint against the new specification found the in-scope typed API surface unchanged: same paths, operations, parameters, request bodies and response schemas. No public API surface change, so this is a patch release (0.4.30.4.4).

Changes

  • Bump API_SPEC_VERSION to v2-2026-07-01T115402Z and CLIENT_VERSION to 0.4.4 (version.go).
  • Sync the API_SPEC_VERSION reference in the README "Versioning" section to match version.go.
  • Add CHANGELOG.md [0.4.4] entry.

Verification

  • gofmt -l . — clean
  • go vet ./... — clean
  • go build ./... — clean
  • go test ./... -p 1 (live API, APIFY_TOKEN set) — root package ok, integration tests package ok (48.7s), 0 failures.

Generated by Claude Code

Bump API_SPEC_VERSION to v2-2026-07-01T115402Z and CLIENT_VERSION to 0.4.4,
and sync the README Versioning reference. The in-scope typed API surface is
unchanged versus v2-2026-06-30T091455Z, so this is a patch release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants