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

CHANGELOG.md

@@ -5,6 +5,19 @@ All notable changes to the Apify Go client are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.3] - 2026-06-23
+
+Updated to Apify OpenAPI specification `v2-2026-06-23T113219Z` (previously
+`v2-2026-06-18T095846Z`). 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.
+
+### Changed
+
+- Bumped `API_SPEC_VERSION` to `v2-2026-06-23T113219Z`.
+- Bumped `CLIENT_VERSION` to `0.2.3`.
+
 ## [0.2.2] - 2026-06-22
 
 Publishing compliance for the updated client requirements (apify-client-orchestration PR #7).

README.md

@@ -167,7 +167,7 @@ func main() {
 
 - `apify.CLIENT_VERSION` — the semantic version of this library.
 - `apify.API_SPEC_VERSION` — the Apify OpenAPI spec version this client was built against
-  (`v2-2026-06-18T095846Z`).
+  (`v2-2026-06-23T113219Z`).
 
 ### Releasing
 

common.go

@@ -214,8 +214,15 @@ type PaginationList[T any] struct {
 //
 // isAtHome is driven by the platform's APIFY_IS_AT_HOME environment variable (matching the
 // reference JS client, which reads it via @apify/consts) or the bare isAtHome variable from
-// the requirements doc; either being set marks the client "at home". The flag is rendered
-// lowercase (true/false) to stay byte-consistent with the JS reference. See CHANGELOG.md.
+// the requirements doc; either being set marks the client "at home".
+//
+// Casing note (deliberate): the flag is rendered lowercase (true/false). The requirements'
+// worked example shows the capitalized form (isAtHome/True | isAtHome/False), but that example
+// is Python-specific (Python's str(bool) is "True"/"False"). The "consistent with the JS
+// reference" requirement is same-priority, and the JS client interpolates a JS boolean, which
+// stringifies lowercase; the Rust sibling client emits lowercase too. Lowercase is therefore the
+// cross-client-consistent choice, and the literal capitalized example is treated as illustrative
+// rather than normative. See CHANGELOG.md.
 func BuildUserAgent(suffix string, isAtHomeFn func() bool) string {
 	atHome := "false"
 	if isAtHomeFn() {

version.go

@@ -4,10 +4,10 @@ package apify
 //
 // It follows Semantic Versioning (https://semver.org/). Changes to the public
 // interface (other than additive ones) are considered breaking changes.
-const CLIENT_VERSION = "0.2.2"
+const CLIENT_VERSION = "0.2.3"
 
 // API_SPEC_VERSION is the version of the Apify OpenAPI specification that this
 // client was generated and verified against.
 //
 // It corresponds to the `info.version` field of the Apify OpenAPI document.
-const API_SPEC_VERSION = "v2-2026-06-18T095846Z"
+const API_SPEC_VERSION = "v2-2026-06-23T113219Z"