Run daily builds of 8.18 and 9.0

Author: miguelgrinberg

.github/workflows/daily.yml

@@ -1,4 +1,4 @@
-name: Daily 8.17 branch integration testing
+name: Daily last two branches integration testing
 on:
   workflow_dispatch:
   schedule:
@@ -9,7 +9,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          ref: 8.17
+          ref: 8.18
       - name: Setup node.js
         uses: actions/setup-node@v4
       - name: Install
@@ -29,7 +29,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          ref: 8.17
+          ref: 8.18
       - name: Setup node.js
         uses: actions/setup-node@v4
       - name: Install
@@ -49,7 +49,67 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          ref: 8.17
+          ref: 8.18
+      - name: Setup node.js
+        uses: actions/setup-node@v4
+      - name: Install
+        run: |
+          npm install
+      - name: Build
+        run: |
+          npm run build
+      - name: Prepare for testing
+        run: |
+          npm run test:setup-javascript
+      - name: Integration tests
+        run: |
+          npm run test:integration-javascript
+  integration-tests-curl:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: 9.0
+      - name: Setup node.js
+        uses: actions/setup-node@v4
+      - name: Install
+        run: |
+          npm install
+      - name: Build
+        run: |
+          npm run build
+      - name: Prepare for testing
+        run: |
+          npm run test:setup-curl
+      - name: Integration tests
+        run: |
+          npm run test:integration-curl
+  integration-tests-python:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: 9.0
+      - name: Setup node.js
+        uses: actions/setup-node@v4
+      - name: Install
+        run: |
+          npm install
+      - name: Build
+        run: |
+          npm run build
+      - name: Prepare for testing
+        run: |
+          npm run test:setup-python
+      - name: Integration tests
+        run: |
+          npm run test:integration-python
+  integration-tests-javascript:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: 9.0
       - name: Setup node.js
         uses: actions/setup-node@v4
       - name: Install

CHANGES.md

@@ -1,5 +1,8 @@
 # request-converter change log
 
+## 9.0.0 (2025-02-24)
+* Update schema for 9.0
+
 ## 8.18.0 (2025-02-24)
 * Support for externally hosted exporters ([#69](https://github.com/elastic/request-converter/pull/69))
 * Update schema for 8.18

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elastic/request-converter",
-  "version": "9.0.0",
+  "version": "9.1.0",
   "description": "Elasticsearch request converter",
   "author": "Miguel Grinberg",
   "license": "Apache-2.0",

src/schema.json

@@ -11272,6 +11272,10 @@
           "stability": "stable"
         }
       },
+      "deprecation": {
+        "description": "Forcing any buffered data to be processed is deprecated, in a future major version a datafeed will be required.",
+        "version": "9.1.0"
+      },
       "description": "Force buffered data to be processed.\nThe flush jobs API is only applicable when sending data for analysis using\nthe post data API. Depending on the content of the buffer, then it might\nadditionally calculate new results. Both flush and close operations are\nsimilar, however the flush is more efficient if you are expecting to send\nmore data for analysis. When flushing, the job remains open and is available\nto continue analyzing data. A close operation additionally prunes and\npersists the model state to disk and the job must be opened again before\nanalyzing further data.",
       "docId": "ml-flush-job",
       "docTag": "ml anomaly",
@@ -122406,7 +122410,7 @@
           "description": "If true, returns partial results if there are shard failures. If false, returns an error with no partial results.",
           "name": "allow_partial_search_results",
           "required": false,
-          "serverDefault": false,
+          "serverDefault": true,
           "type": {
             "kind": "instance_of",
             "type": {
@@ -127451,9 +127455,22 @@
               "namespace": "_builtins"
             }
           }
+        },
+        {
+          "description": "The period to wait for a connection to the master node.\nIf no response is received before the timeout expires, the request fails and returns an error.\nIt can also be set to `-1` to indicate that the request should never timeout.",
+          "name": "master_timeout",
+          "required": false,
+          "serverDefault": "30s",
+          "type": {
+            "kind": "instance_of",
+            "type": {
+              "name": "Duration",
+              "namespace": "_types"
+            }
+          }
         }
       ],
-      "specLocation": "ilm/migrate_to_data_tiers/Request.ts#L22-L61"
+      "specLocation": "ilm/migrate_to_data_tiers/Request.ts#L23-L69"
     },
     {
       "kind": "response",
@@ -137692,22 +137709,9 @@
               "namespace": "_builtins"
             }
           }
-        },
-        {
-          "description": "If `true`, the request retrieves information from the local node only.",
-          "name": "local",
-          "required": false,
-          "serverDefault": false,
-          "type": {
-            "kind": "instance_of",
-            "type": {
-              "name": "boolean",
-              "namespace": "_builtins"
-            }
-          }
         }
       ],
-      "specLocation": "indices/get_field_mapping/IndicesGetFieldMappingRequest.ts#L23-L89"
+      "specLocation": "indices/get_field_mapping/IndicesGetFieldMappingRequest.ts#L23-L84"
     },
     {
       "kind": "response",
@@ -171564,6 +171568,10 @@
           }
         ]
       },
+      "deprecation": {
+        "description": "Forcing any buffered data to be processed is deprecated, in a future major version a datafeed will be required.",
+        "version": "9.1.0"
+      },
       "description": "Force buffered data to be processed.\nThe flush jobs API is only applicable when sending data for analysis using\nthe post data API. Depending on the content of the buffer, then it might\nadditionally calculate new results. Both flush and close operations are\nsimilar, however the flush is more efficient if you are expecting to send\nmore data for analysis. When flushing, the job remains open and is available\nto continue analyzing data. A close operation additionally prunes and\npersists the model state to disk and the job must be opened again before\nanalyzing further data.",
       "inherits": {
         "type": {
@@ -171651,7 +171659,7 @@
           }
         }
       ],
-      "specLocation": "ml/flush_job/MlFlushJobRequest.ts#L24-L107"
+      "specLocation": "ml/flush_job/MlFlushJobRequest.ts#L24-L108"
     },
     {
       "kind": "response",