Merge remote-tracking branch 'origin/main' into google-model-garden-integration

Author: pquentin

.backportrc.json

@@ -1,6 +1,6 @@
 {
   "repoOwner": "elastic",
   "repoName": "elasticsearch-specification",
-  "targetBranchChoices": ["9.1", "9.0", "8.19", "8.18"],
+  "targetBranchChoices": ["9.2", "9.1", "9.0", "8.19"],
   "fork": false
 }

.github/workflows/update-rest-api-json.yml

@@ -13,7 +13,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        branch: ['main', '9.1', '9.0', '8.19', '8.18']
+        branch: ['main', '9.2', '9.1', '9.0', '8.19']
 
     steps:
       - uses: actions/checkout@v5

.github/workflows/validate-apis.yml

@@ -41,14 +41,14 @@ jobs:
         with:
           node-version: 22
 
-      - name: Cache JSON report
-        id: cache-json-report
-        uses: actions/cache@v4
+      - name: Restore JSON report
+        if: github.event_name == 'pull_request'
+        uses: actions/cache/restore@v4
         with:
           path: ./clients-flight-recorder/recordings/types-validation/types-validation.json
-          key: types-validation-json-${{ github.event_name == 'pull_request' && format('{0}-{1}', github.base_ref, github.event.pull_request.base.sha) || format('{0}-{1}', github.ref_name, github.sha) }}
+          key: types-validation-json-${{ format('{0}-{1}', github.base_ref, github.event.pull_request.base.sha) }}
           restore-keys: |
-            types-validation-json-${{ github.event_name == 'pull_request' && github.base_ref || github.ref_name }}-
+            types-validation-json-${{ github.base_ref }}-
 
       - name: Install deps 1/2
         working-directory: ./clients-flight-recorder
@@ -87,11 +87,20 @@ jobs:
           BRANCH: ${{ github.ref_name }}
         run: node index.js --generate-report --ci --branch $BRANCH
 
+      - name: Save JSON report
+        if: github.event_name == 'push'
+        uses: actions/cache/save@v4
+        with:
+          path: ./clients-flight-recorder/recordings/types-validation/types-validation.json
+          key: types-validation-json-${{ format('{0}-{1}', github.ref_name, github.sha) }}
+          restore-keys: |
+            types-validation-json-${{ github.ref_name }}-
+
       - name: Run validation (PR)
         if: github.event_name == 'pull_request'
         id: validation
         working-directory: ./elasticsearch-specification
-        run: node .github/validate-pr --token ${{ secrets.GITHUB_TOKEN }}
+        run: node .github/validate-pr
 
       - name: Find existing comment
         if: github.event_name == 'pull_request'

compiler/src/model/build-model.ts

@@ -306,6 +306,7 @@ function compileClassOrInterfaceDeclaration (declaration: ClassDeclaration | Int
 
       // validate body
       if (bodyMember != null) {
+        mapping.requestBodyRequired = !(bodyMember as PropertySignature).hasQuestionToken()
         assert(
           bodyMember,
           methods.some(method => ['POST', 'PUT', 'DELETE'].includes(method)),

docs/overlays/elasticsearch-shared-overlays.yaml

@@ -129,6 +129,9 @@ actions:
             Inference APIs enable you to use certain services, such as built-in machine learning models (ELSER, E5), models uploaded through Eland, Cohere, OpenAI, Azure, Google AI Studio or Hugging Face.
             For built-in models and models uploaded through Eland, the inference APIs offer an alternative way to use and manage trained models.
             However, if you do not plan to use the inference APIs to use these models or if you want to use non-NLP models, use the machine learning trained model APIs.
+          externalDocs:
+            url: https://www.elastic.co/docs/explore-analyze/elastic-inference/inference-api
+            description: Learn about default inference endpoints, adaptive allocations, and chunking.
         - name: info
           x-displayName: Info
           description: >
@@ -187,6 +190,10 @@ actions:
           x-displayName: Node lifecycle
           description: >
             The node lifecycle APIs enable you to prepare nodes for temporary or permanent shutdown, monitor the shutdown status, and enable a previously shut-down node to resume normal operations.
+      # P
+        - name: project
+          x-displayName: Project
+          # description: 
       # Q
         - name: query_rules
           x-displayName: Query rules