Merge branch 'main' into fix/ruby-browse-helpers

Author: Fluf22

.github/actions/setup/action.yml

@@ -26,7 +26,7 @@ runs:
 
     - name: Setup gradle
       if: inputs.type != 'minimal'
-      uses: gradle/actions/[email protected].1 # v4.4.2 fails because it uses Gradle 9.0 which is not compatible with Java < 17
+      uses: gradle/actions/[email protected].3
       with:
         validate-wrappers: true
         add-job-summary: 'on-failure'

.github/workflows/check.yml

@@ -316,6 +316,8 @@ jobs:
       ALGOLIA_APPLICATION_ID: ${{ secrets.ALGOLIA_APPLICATION_ID }}
       ALGOLIA_ADMIN_KEY: ${{ secrets.ALGOLIA_ADMIN_KEY }}
       MONITORING_API_KEY: ${{ secrets.MONITORING_API_KEY }}
+      METIS_APPLICATION_ID: ${{ secrets.METIS_APPLICATION_ID }}
+      METIS_API_KEY: ${{ secrets.METIS_API_KEY }}
     outputs:
       hasBreakingChanges: ${{ steps.breakingChanges.outputs.hasBreakingChanges }}
     name: client ${{ matrix.client.language }}@${{ matrix.client.version }}
@@ -586,7 +588,7 @@ jobs:
             echo 'BREAKING_CHANGES_SECTION<<EOF'
             echo "# 💥 Breaking changes detected !!"
             echo "Either this PR or a previous PR not released yet introduced breaking changes, be careful when merging."
-            echo "You can find the details in the 'client java@17' CI job."
+            echo "You can find the details in the 'client java@21' CI job."
             echo 'EOF'
           } >> "$GITHUB_OUTPUT"
 

.redocly.yaml

@@ -1,16 +1,20 @@
 apis:
   abtesting:
     root: specs/abtesting/spec.yml
+  abtesting-v3:
+    root: specs/abtesting-v3/spec.yml
+  advanced-personalization:
+    root: specs/advanced-personalization/spec.yml
   analytics:
     root: specs/analytics/spec.yml
+  composition:
+    root: specs/composition/spec.yml
   ingestion:
     root: specs/ingestion/spec.yml
   insights:
     root: specs/insights/spec.yml
   monitoring:
     root: specs/monitoring/spec.yml
-    rules:
-      security-defined: off
   personalization:
     root: specs/personalization/spec.yml
   query-suggestions:

.yarn/releases/yarn-4.9.4.cjs renamed to .yarn/releases/yarn-4.10.0.cjs

@@ -4,7 +4,7 @@ enableGlobalCache: false
 
 nodeLinker: node-modules
 
-yarnPath: .yarn/releases/yarn-4.9.4.cjs
+yarnPath: .yarn/releases/yarn-4.10.0.cjs
 
 # esbuild use native binaries, we need both to work locally and on the CI.
 supportedArchitectures:

.yarnrc.yml

@@ -5,7 +5,6 @@ specs/ @algolia/doc-approvers
 website/ @algolia/doc-approvers
 specs/advanced-personalization @algolia/predict-fe
 specs/composition @algolia/composition
-specs/composition-full @algolia/composition
 specs/abtesting-v3 @algolia/optimization
 specs/analytics @algolia/optimization
 

CODEOWNERS

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Create ticket
-        uses: actions/github-script@v7
+        uses: actions/github-script@v8
         with:
           script: |
             const action = context.payload.action;

clients/algoliasearch-client-csharp/.github/workflows/issue.yml

@@ -1,7 +1,7 @@
 /*
 * Composition API
 *
-* The Algolia Composition API lets you run composed search requests on your Compositions.  ## Client libraries  Use Algolia's API clients and libraries to reliably integrate Algolia's APIs with your apps.  See: [Algolia's ecosystem](https://www.algolia.com/doc/guides/getting-started/how-algolia-works/in-depth/ecosystem/)  ## Base URLs  The base URLs for requests to the Composition API are:  - `https://{APPLICATION_ID}.algolia.net` - `https://{APPLICATION_ID}-dsn.algolia.net`.   If your subscription includes a [Distributed Search Network](https://dashboard.algolia.com/infra),   this ensures that requests are sent to servers closest to users.  Both URLs provide high availability by distributing requests with load balancing.  **All requests must use HTTPS.**  ## Retry strategy  To guarantee high availability, implement a retry strategy for all API requests using the URLs of your servers as fallbacks:  - `https://{APPLICATION_ID}-1.algolianet.com` - `https://{APPLICATION_ID}-2.algolianet.com` - `https://{APPLICATION_ID}-3.algolianet.com`  These URLs use a different DNS provider than the primary URLs. You should randomize this list to ensure an even load across the three servers.  All Algolia API clients implement this retry strategy.  ## Authentication  To authenticate your API requests, add these headers:  - `x-algolia-application-id`. Your Algolia application ID. - `x-algolia-api-key`. An API key with the necessary permissions to make the request.   The required access control list (ACL) to make a request is listed in each endpoint's reference.  You can find your application ID and API key in the [Algolia dashboard](https://dashboard.algolia.com/account).  ## Request format  Depending on the endpoint, request bodies are either JSON objects or arrays of JSON objects,  ## Parameters  Parameters are passed as query parameters for GET and DELETE requests, and in the request body for POST and PUT requests.  Query parameters must be [URL-encoded](https://developer.mozilla.org/en-US/docs/Glossary/Percent-encoding). Non-ASCII characters must be UTF-8 encoded. Plus characters (`+`) are interpreted as spaces. Arrays as query parameters must be one of:  - A comma-separated string: `attributesToRetrieve=title,description` - A URL-encoded JSON array: `attributesToRetrieve=%5B%22title%22,%22description%22%D`  ## Response status and errors  The Composition API returns JSON responses. Since JSON doesn't guarantee any specific ordering, don't rely on the order of attributes in the API response.  Successful responses return a `2xx` status. Client errors return a `4xx` status. Server errors are indicated by a `5xx` status. Error responses have a `message` property with more information.  ## Version  The current version of the Composition API is version 1, as indicated by the `/1/` in each endpoint's URL.
+* The Algolia Composition API lets you run composed search requests on your Compositions.  ## Client libraries  Use Algolia's API clients and libraries to reliably integrate Algolia's APIs with your apps.  See: [Algolia's ecosystem](https://www.algolia.com/doc/guides/getting-started/how-algolia-works/in-depth/ecosystem/)  ## Base URLs  The base URLs for requests to the Composition API are:  - `https://{APPLICATION_ID}.algolia.net` - `https://{APPLICATION_ID}-dsn.algolia.net`.   If your subscription includes a [Distributed Search Network](https://dashboard.algolia.com/infra),   this ensures that requests are sent to servers closest to users.  Both URLs provide high availability by distributing requests with load balancing.  **All requests must use HTTPS.**  ## Retry strategy  To guarantee high availability, implement a retry strategy for all API requests using the URLs of your servers as fallbacks:  - `https://{APPLICATION_ID}-1.algolianet.com` - `https://{APPLICATION_ID}-2.algolianet.com` - `https://{APPLICATION_ID}-3.algolianet.com`  These URLs use a different DNS provider than the primary URLs. You should randomize this list to ensure an even load across the three servers.  All Algolia API clients implement this retry strategy.  ## Authentication  To authenticate your API requests, add these headers:  - `x-algolia-application-id`. Your Algolia application ID. - `x-algolia-api-key`. An API key with the necessary permissions to make the request.   The required access control list (ACL) to make a request is listed in each endpoint's reference.  You can find your application ID and API key in the [Algolia dashboard](https://dashboard.algolia.com/account).  ## Request format  Depending on the endpoint, request bodies are either JSON objects or arrays of JSON objects,  ## Parameters  Parameters are passed in the request body for POST and PUT requests. Query parameters must be [URL-encoded](https://developer.mozilla.org/en-US/docs/Glossary/Percent-encoding). Non-ASCII characters must be UTF-8 encoded. Plus characters (`+`) are interpreted as spaces.  ## Response status and errors  The Composition API returns JSON responses. Since JSON doesn't guarantee any specific ordering, don't rely on the order of attributes in the API response.  Successful responses return a `2xx` status. Client errors return a `4xx` status. Server errors are indicated by a `5xx` status. Error responses have a `message` property with more information.  ## Version  The current version of the Composition API is version 1, as indicated by the `/1/` in each endpoint's URL.
 *
 * The version of the OpenAPI document: 1.0.0
 * Generated by: https://github.com/openapitools/openapi-generator.git

clients/algoliasearch-client-csharp/algoliasearch/Clients/CompositionClient.cs

@@ -0,0 +1,32 @@
+//
+// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
+//
+using System;
+using System.Collections.Generic;
+using System.Linq;
+using System.Text;
+using System.Text.Json;
+using System.Text.Json.Serialization;
+using Algolia.Search.Serializer;
+
+namespace Algolia.Search.Models.Composition;
+
+/// <summary>
+/// Type of Composition Batch operation.
+/// </summary>
+/// <value>Type of Composition Batch operation.</value>
+[JsonConverter(typeof(Serializer.JsonStringEnumConverter<Action>))]
+public enum Action
+{
+  /// <summary>
+  /// Enum Upsert for value: upsert
+  /// </summary>
+  [JsonPropertyName("upsert")]
+  Upsert = 1,
+
+  /// <summary>
+  /// Enum Delete for value: delete
+  /// </summary>
+  [JsonPropertyName("delete")]
+  Delete = 2,
+}