Automated SDK update

This updates the SDK from internal repo commit segmentio/public-api@74422876.

Author: APIs and Common Services team

README.md

@@ -10,7 +10,7 @@ All endpoints in the API follow REST conventions and use standard HTTP methods.
 
 See the next sections for more information on how to use the Segment Public API Java SDK.
 
-Latest API and SDK version: 61.2.0
+Latest API and SDK version: 62.0.0
 
 ## Requirements
 
@@ -28,7 +28,7 @@ Add this dependency to your project's POM:
 <dependency>
   <groupId>com.segment.publicapi</groupId>
   <artifactId>segment-publicapi</artifactId>
-  <version>61.2.0</version>
+  <version>62.0.0</version>
   <scope>compile</scope>
 </dependency>
 ```
@@ -44,7 +44,7 @@ Add this dependency to your project's build file:
   }
 
   dependencies {
-     implementation "com.segment.publicapi:segment-publicapi:61.2.0"
+     implementation "com.segment.publicapi:segment-publicapi:62.0.0"
   }
 ```
 
@@ -58,7 +58,7 @@ mvn clean package
 
 Then manually install the following JARs:
 
-* `target/segment-publicapi-61.2.0.jar`
+* `target/segment-publicapi-62.0.0.jar`
 * `target/lib/*.jar`
 
 You are now ready to start making calls to Public API!

docs/DeletionAndSuppressionApi.md

@@ -21,7 +21,7 @@ All URIs are relative to *https://api.segmentapis.com*
 
 Create Cloud Source Regulation
 
-Creates a Source-scoped regulation.    Please Note: Suppression rules at the Workspace level take precedence over those at the Source level. If a user has been suppressed at the Workspace level, any attempt to un-suppress at the Source level is not supported and the processing of the request will fail in Segment        Config API omitted fields: - `attributes`, - `userAgent`       
+Creates a Source-scoped regulation.    Please Note: Suppression rules at the Workspace level take precedence over those at the Source level. If a user has been suppressed at the Workspace level, any attempt to un-suppress at the Source level is not supported and the processing of the request will fail in Segment    Config API omitted fields: - `attributes`, - `userAgent`  Rate limit headers will be updated to reflect regulation-specific limits (tracked separately for Segment-only vs Segment & Destination regulation types): - X-RateLimit-Remaining: Remaining requests for the regulation type category   - Segment-only Regulations: DELETE_INTERNAL, SUPPRESS_WITH_DELETE_INTERNAL, SUPPRESS_ONLY, UNSUPPRESS, DELETE_ARCHIVE_ONLY   - Segment & Destination Regulations: DELETE_ONLY, SUPPRESS_WITH_DELETE - X-RateLimit-Reset: RFC 5322 timestamp for when the quota resets (for example, Tue, 31 Dec 2024 23:59:59 GMT)   
 
 ### Example
 
@@ -84,7 +84,7 @@ public class Example {
 ### HTTP response details
 | Status code | Description | Response headers |
 |-------------|-------------|------------------|
-| **200** | OK |  -  |
+| **200** | OK |  * X-RateLimit-Remaining - Remaining requests in the current period for the regulation type category. Tracked separately for Segment-only vs Segment &amp; Destination regulation types. <br>  * X-RateLimit-Consumed - Number of requests consumed in the current period for the regulation type category. Tracked separately for Segment-only vs Segment &amp; Destination regulation types. <br>  * X-RateLimit-Reset - RFC 5322 timestamp indicating when the regulation quota resets for the specific regulation type category. <br>  |
 | **404** | Resource not found |  -  |
 | **422** | Validation failure |  -  |
 | **429** | Too many requests |  -  |
@@ -96,7 +96,7 @@ public class Example {
 
 Create Source Regulation
 
-Creates a Source-scoped regulation.    Please Note: Suppression rules at the Workspace level take precedence over those at the Source level. If a user has been suppressed at the Workspace level, any attempt to un-suppress at the Source level is not supported and the processing of the request will fail in Segment    • When called, this endpoint may generate the &#x60;Source Regulation Created&#x60; event in the [audit trail](/tag/Audit-Trail).  Config API omitted fields: - &#x60;attributes&#x60;, - &#x60;userAgent&#x60;       
+Creates a Source-scoped regulation.    Please Note: Suppression rules at the Workspace level take precedence over those at the Source level. If a user has been suppressed at the Workspace level, any attempt to un-suppress at the Source level is not supported and the processing of the request will fail in Segment    • When called, this endpoint may generate the &#x60;Source Regulation Created&#x60; event in the [audit trail](/tag/Audit-Trail).  Config API omitted fields: - &#x60;attributes&#x60;, - &#x60;userAgent&#x60;  Rate limit headers will be updated to reflect regulation-specific limits (tracked separately for Segment-only vs Segment &amp; Destination regulation types): - X-RateLimit-Remaining: Remaining requests for the regulation type category   - Segment-only Regulations: DELETE_INTERNAL, SUPPRESS_WITH_DELETE_INTERNAL, SUPPRESS_ONLY, UNSUPPRESS, DELETE_ARCHIVE_ONLY   - Segment &amp; Destination Regulations: DELETE_ONLY, SUPPRESS_WITH_DELETE - X-RateLimit-Reset: RFC 5322 timestamp for when the quota resets (for example, Tue, 31 Dec 2024 23:59:59 GMT)   
 
 ### Example
 
@@ -159,7 +159,7 @@ public class Example {
 ### HTTP response details
 | Status code | Description | Response headers |
 |-------------|-------------|------------------|
-| **200** | OK |  -  |
+| **200** | OK |  * X-RateLimit-Remaining - Remaining requests in the current period for the regulation type category. Tracked separately for Segment-only vs Segment &amp; Destination regulation types. <br>  * X-RateLimit-Consumed - Number of requests consumed in the current period for the regulation type category. Tracked separately for Segment-only vs Segment &amp; Destination regulation types. <br>  * X-RateLimit-Reset - RFC 5322 timestamp indicating when the regulation quota resets for the specific regulation type category. <br>  |
 | **404** | Resource not found |  -  |
 | **422** | Validation failure |  -  |
 | **429** | Too many requests |  -  |
@@ -171,7 +171,7 @@ public class Example {
 
 Create Workspace Regulation
 
-Creates a Workspace-scoped regulation.    • When called, this endpoint may generate the &#x60;Workspace Regulation Created&#x60; event in the [audit trail](/tag/Audit-Trail).  Config API omitted fields: - &#x60;attributes&#x60;, - &#x60;userAgent&#x60;       
+Creates a Workspace-scoped regulation.    • When called, this endpoint may generate the &#x60;Workspace Regulation Created&#x60; event in the [audit trail](/tag/Audit-Trail).  Config API omitted fields: - &#x60;attributes&#x60;, - &#x60;userAgent&#x60;  Rate limit headers will be updated to reflect regulation-specific limits (tracked separately for Segment-only vs Segment &amp; Destination regulation types): - X-RateLimit-Remaining: Remaining requests for the regulation type category   - Segment-only Regulations: DELETE_INTERNAL, SUPPRESS_WITH_DELETE_INTERNAL, SUPPRESS_ONLY, UNSUPPRESS, DELETE_ARCHIVE_ONLY   - Segment &amp; Destination Regulations: DELETE_ONLY, SUPPRESS_WITH_DELETE - X-RateLimit-Reset: RFC 5322 timestamp for when the quota resets (for example, Tue, 31 Dec 2024 23:59:59 GMT)   
 
 ### Example
 
@@ -232,7 +232,7 @@ public class Example {
 ### HTTP response details
 | Status code | Description | Response headers |
 |-------------|-------------|------------------|
-| **200** | OK |  -  |
+| **200** | OK |  * X-RateLimit-Remaining - Remaining requests in the current period for the regulation type category. Tracked separately for Segment-only vs Segment &amp; Destination regulation types. <br>  * X-RateLimit-Consumed - Number of requests consumed in the current period for the regulation type category. Tracked separately for Segment-only vs Segment &amp; Destination regulation types. <br>  * X-RateLimit-Reset - RFC 5322 timestamp indicating when the regulation quota resets for the specific regulation type category. <br>  |
 | **404** | Resource not found |  -  |
 | **422** | Validation failure |  -  |
 | **429** | Too many requests |  -  |

pom.xml

@@ -5,7 +5,7 @@
     <artifactId>segment-publicapi</artifactId>
     <packaging>jar</packaging>
     <name>segment-publicapi</name>
-    <version>61.2.0</version>
+    <version>62.0.0</version>
     <url>https://segment.com/docs/api/public-api/</url>
     <description>Segment Public API</description>
     <scm>

src/main/java/com/segment/publicapi/ApiClient.java

@@ -123,7 +123,7 @@ private void init() {
         json = new JSON();
 
         // Set default User-Agent.
-        setUserAgent("Public API SDK 61.2.0 (Java)");
+        setUserAgent("Public API SDK 62.0.0 (Java)");
 
         authentications = new HashMap<String, Authentication>();
     }

src/main/java/com/segment/publicapi/Configuration.java

@@ -12,7 +12,7 @@
 package com.segment.publicapi;
 
 public class Configuration {
-    public static final String VERSION = "61.2.0";
+    public static final String VERSION = "62.0.0";
 
     private static ApiClient defaultApiClient = new ApiClient();