Merge branch 'main' into feat/n8n-nodes-algolia-specs

Author: millotp

.github/actions/setup/action.yml

@@ -38,7 +38,7 @@ runs:
 
     # JavaScript for monorepo and tooling
     - name: Install Node
-      uses: actions/setup-node@v4
+      uses: actions/setup-node@v5
       with:
         node-version-file: .nvmrc
         cache: yarn
@@ -50,7 +50,7 @@ runs:
     # Csharp
     - name: Install dotnet
       if: ${{ inputs.language == 'csharp' }}
-      uses: actions/setup-dotnet@v4
+      uses: actions/setup-dotnet@v5
       with:
         dotnet-version: ${{ inputs.version }}
 
@@ -69,7 +69,7 @@ runs:
     # Golang
     - name: Install golang
       if: ${{ inputs.language == 'go' }}
-      uses: actions/setup-go@v5
+      uses: actions/setup-go@v6
       with:
         cache-dependency-path: clients/algoliasearch-client-go/go.sum
         go-version: ${{ inputs.version }}
@@ -144,7 +144,7 @@ runs:
       shell: bash
       run: pipx install poetry==2
 
-    - uses: actions/setup-python@v5
+    - uses: actions/setup-python@v6
       if: ${{ inputs.language == 'python' }}
       with:
         python-version: ${{ inputs.version }}

.github/workflows/issue.yml

@@ -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;

.github/workflows/pr-title.yml

@@ -14,6 +14,6 @@ jobs:
           fetch-depth: 0
 
       - name: Pull Request title rules
-        uses: Slashgear/action-check-pr-title@v4.3.0
+        uses: Slashgear/action-check-pr-title@v5.0.1
         with:
           regexp: '^(docs|chore|snippets|guides)|((?:feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)\((?:clients|generators|playground|csharp|dart|go|java|javascript|kotlin|php|python|ruby|scala|swift|cts|specs|scripts|ci|templates|deps)\)): .+'

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

@@ -14,7 +14,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Setup .NET
-        uses: actions/setup-dotnet@v4
+        uses: actions/setup-dotnet@v5
         with:
           global-json-file: global.json
 

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

@@ -1739,7 +1739,7 @@ WatchResponse Push(
   );
 
   /// <summary>
-  /// Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
+  /// Pushes records through the pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints or the debugger dashboard to see the status of your task. If you want to transform your data before indexing, this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
   /// </summary>
   ///
   /// Required API Key ACLs:
@@ -1764,7 +1764,7 @@ Task<WatchResponse> PushTaskAsync(
   );
 
   /// <summary>
-  /// Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.  (Synchronous version)
+  /// Pushes records through the pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints or the debugger dashboard to see the status of your task. If you want to transform your data before indexing, this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.  (Synchronous version)
   /// </summary>
   ///
   /// Required API Key ACLs:

clients/algoliasearch-client-go/algolia/ingestion/api_ingestion.go

@@ -3333,14 +3333,12 @@ public CompletableFuture<WatchResponse> pushAsync(@Nonnull String indexName, @No
   }
 
   /**
-   * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by
+   * Pushes records through the pipeline, directly to an index. You can make the call synchronous by
    * providing the `watch` parameter, for asynchronous calls, you can use the observability
-   * endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the
-   * [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * endpoints or the debugger dashboard to see the status of your task. If you want to transform
+   * your data before indexing, this is the recommended way of ingesting your records. This method
+   * is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when
+   * many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3360,14 +3358,12 @@ public WatchResponse pushTask(
   }
 
   /**
-   * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by
+   * Pushes records through the pipeline, directly to an index. You can make the call synchronous by
    * providing the `watch` parameter, for asynchronous calls, you can use the observability
-   * endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the
-   * [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * endpoints or the debugger dashboard to see the status of your task. If you want to transform
+   * your data before indexing, this is the recommended way of ingesting your records. This method
+   * is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when
+   * many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3381,14 +3377,12 @@ public WatchResponse pushTask(@Nonnull String taskID, @Nonnull PushTaskPayload p
   }
 
   /**
-   * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by
+   * Pushes records through the pipeline, directly to an index. You can make the call synchronous by
    * providing the `watch` parameter, for asynchronous calls, you can use the observability
-   * endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the
-   * [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * endpoints or the debugger dashboard to see the status of your task. If you want to transform
+   * your data before indexing, this is the recommended way of ingesting your records. This method
+   * is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when
+   * many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3402,14 +3396,12 @@ public WatchResponse pushTask(@Nonnull String taskID, @Nonnull PushTaskPayload p
   }
 
   /**
-   * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by
+   * Pushes records through the pipeline, directly to an index. You can make the call synchronous by
    * providing the `watch` parameter, for asynchronous calls, you can use the observability
-   * endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the
-   * [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * endpoints or the debugger dashboard to see the status of your task. If you want to transform
+   * your data before indexing, this is the recommended way of ingesting your records. This method
+   * is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when
+   * many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3420,14 +3412,12 @@ public WatchResponse pushTask(@Nonnull String taskID, @Nonnull PushTaskPayload p
   }
 
   /**
-   * (asynchronously) Pushes records through the Pipeline, directly to an index. You can make the
+   * (asynchronously) Pushes records through the pipeline, directly to an index. You can make the
    * call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the
-   * observability endpoints and/or debugger dashboard to see the status of your task. If you want
-   * to leverage the [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * observability endpoints or the debugger dashboard to see the status of your task. If you want
+   * to transform your data before indexing, this is the recommended way of ingesting your records.
+   * This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is
+   * useful when many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3465,14 +3455,12 @@ public CompletableFuture<WatchResponse> pushTaskAsync(
   }
 
   /**
-   * (asynchronously) Pushes records through the Pipeline, directly to an index. You can make the
+   * (asynchronously) Pushes records through the pipeline, directly to an index. You can make the
    * call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the
-   * observability endpoints and/or debugger dashboard to see the status of your task. If you want
-   * to leverage the [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * observability endpoints or the debugger dashboard to see the status of your task. If you want
+   * to transform your data before indexing, this is the recommended way of ingesting your records.
+   * This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is
+   * useful when many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3486,14 +3474,12 @@ public CompletableFuture<WatchResponse> pushTaskAsync(@Nonnull String taskID, @N
   }
 
   /**
-   * (asynchronously) Pushes records through the Pipeline, directly to an index. You can make the
+   * (asynchronously) Pushes records through the pipeline, directly to an index. You can make the
    * call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the
-   * observability endpoints and/or debugger dashboard to see the status of your task. If you want
-   * to leverage the [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * observability endpoints or the debugger dashboard to see the status of your task. If you want
+   * to transform your data before indexing, this is the recommended way of ingesting your records.
+   * This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is
+   * useful when many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3510,14 +3496,12 @@ public CompletableFuture<WatchResponse> pushTaskAsync(
   }
 
   /**
-   * (asynchronously) Pushes records through the Pipeline, directly to an index. You can make the
+   * (asynchronously) Pushes records through the pipeline, directly to an index. You can make the
    * call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the
-   * observability endpoints and/or debugger dashboard to see the status of your task. If you want
-   * to leverage the [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * observability endpoints or the debugger dashboard to see the status of your task. If you want
+   * to transform your data before indexing, this is the recommended way of ingesting your records.
+   * This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is
+   * useful when many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)

clients/algoliasearch-client-java/algoliasearch/src/main/java/com/algolia/api/IngestionClient.java

@@ -16,7 +16,7 @@ jobs:
           fetch-depth: 0
 
       - name: Install Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v5
         with:
           node-version-file: .nvmrc
           cache: yarn

clients/algoliasearch-client-javascript/.github/workflows/release.yml

@@ -15,7 +15,7 @@
     "test:bundle": "lerna run test:bundle --verbose --include-dependencies"
   },
   "devDependencies": {
-    "@types/node": "22.18.0",
+    "@types/node": "22.18.1",
     "bundlewatch": "0.4.1",
     "execa": "9.6.0",
     "lerna": "8.2.3",

clients/algoliasearch-client-javascript/package.json

@@ -56,7 +56,7 @@
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "0.18.2",
-    "@types/node": "22.18.0",
+    "@types/node": "22.18.1",
     "publint": "0.3.12",
     "rollup": "4.41.0",
     "tsup": "8.5.0",