chore: sync Java client with Apify OpenAPI spec v2-2026-09-02T154542Z

CHANGELOG.md

@@ -5,6 +5,19 @@ All notable changes to the Apify Java 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.6.3] - 2026-09-04
+
+### Changed
+
+- Bumped `Version.API_SPEC_VERSION` to `v2-2026-09-02T154542Z` and `Version.CLIENT_VERSION` to
+  `0.6.3`. The spec delta over this window loosened several schemas (`generalAccess` on `Run`,
+  storage resources, and `ActorDefinition.readme`/`input`/`changelog` are now nullable; some
+  `UserPrivateInfo` fields are no longer required; task `input` can now also be an array) and added
+  `Task.description`/`CreateTaskRequest.description`/`UpdateTaskRequest.description` plus a
+  `format: date-time` annotation on `DailyServiceUsages.date`. None of it changes this client:
+  every affected field is already modeled as nullable, passed through as raw JSON, or (for
+  `Task.description`) already implemented.
+
 ## [0.6.2] - 2026-08-28
 
 ### Changed

README.md

@@ -23,7 +23,7 @@ Maven (Maven Central is a default repository, so no extra configuration is neede
 <dependency>
   <groupId>com.apify</groupId>
   <artifactId>apify-client</artifactId>
-  <version>0.6.2</version>
+  <version>0.6.3</version>
 </dependency>
 ```
 
@@ -35,7 +35,7 @@ repositories {
 }
 
 dependencies {
-  implementation 'com.apify:apify-client:0.6.2'
+  implementation 'com.apify:apify-client:0.6.3'
 }
 ```
 
@@ -293,10 +293,10 @@ try {
 The public `com.apify.client.Version` class (`import com.apify.client.Version;`) exposes two
 constants:
 
-- `Version.CLIENT_VERSION` — the semantic version of this client (`0.6.2`).
+- `Version.CLIENT_VERSION` — the semantic version of this client (`0.6.3`).
 - `Version.API_SPEC_VERSION` — the version of the [Apify OpenAPI specification](https://docs.apify.com/api/openapi.json)
   (its `info.version` field) that this client's endpoints, parameters and models were last generated
-  and checked against (`v2-2026-08-27T071624Z`). It is a snapshot, not a live compatibility
+  and checked against (`v2-2026-09-02T154542Z`). It is a snapshot, not a live compatibility
   guarantee: the client keeps working against newer, backward-compatible spec revisions, but a
   feature added to the API after this snapshot has no corresponding method here yet.
 

pom.xml

@@ -6,7 +6,7 @@
 
     <groupId>com.apify</groupId>
     <artifactId>apify-client</artifactId>
-    <version>0.6.2</version>
+    <version>0.6.3</version>
     <packaging>jar</packaging>
 
     <name>Apify Java Client</name>

src/main/java/com/apify/client/Version.java

@@ -13,13 +13,13 @@ public final class Version {
    * The semantic version of this client library (see <a href="https://semver.org/">SemVer</a>).
    * Changes to the public interface other than additive ones are considered breaking changes.
    */
-  public static final String CLIENT_VERSION = "0.6.2";
+  public static final String CLIENT_VERSION = "0.6.3";
 
   /**
    * The version of the Apify OpenAPI specification this client was generated and verified against.
    * Corresponds to the {@code info.version} field of the Apify OpenAPI document.
    */
-  public static final String API_SPEC_VERSION = "v2-2026-08-27T071624Z";
+  public static final String API_SPEC_VERSION = "v2-2026-09-02T154542Z";
 
   private Version() {}
 }