Merge branch 'main' into nomad/1.11.1

Author: aimeeu

.github/workflows/algolia-prod.yml

@@ -22,7 +22,7 @@ jobs:
           cache: 'npm'
           node-version-file: 'package.json'
 
-      - run: npm i
+      - run: npm ci
       - run: npm run prebuild -- --get-real-file-changed-metadata --build-algolia-index
       - run: npm run algolia
         env:

.github/workflows/build-pr-preview.yml

@@ -2,6 +2,10 @@ name: Build Preview
 run-name: 'Build Preview for "${{ github.event.pull_request.title }}" (#${{ github.event.pull_request.number }})'
 
 on:
+  # 1: Change this to `pull_request` to see changes while testing this file in a PR.
+  # 2: This is because `pull_request_target` only works from the context of the base branch
+  #    https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request_target
+  # 3: Change this back to `pull_request_target` before merge for security reasons
   pull_request_target:
     types: [opened, synchronize]
   # Hello Security 👋, we are checking to make sure forked repo PR changed paths are only in content/** inside the job security-check.
@@ -105,20 +109,11 @@ jobs:
           cache: 'npm'
           node-version-file: 'package.json'
 
-      - name: Generate cache manifest
-        run: git ls-files -z -- '*.js' '*.mjs' '*.ts' '*.tsx' '*.mdx' '*.json' | xargs -0 git hash-object > cache-key.txt
-
-      - name: Use cache
+      - name: Cache Next.js build
         uses: actions/cache@d4323d4df104b026a6aa633fdb11d772146be0bf # v4.2.2
         with:
-          path: |
-            ~/.npm
-            ${{ github.workspace }}/.next/cache
-          # Generate a new cache whenever packages or source files change.
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-${{ hashFiles('cache-key.txt') }}
-          # If source files changed but packages didn't, rebuild from a prior cache.
-          restore-keys: |
-            ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-
+          path: ${{ github.workspace }}/.next/cache
+          key: ${{ runner.os }}-nextjs-build-${{ hashFiles('package-lock.json', 'next.config.js') }}
 
       - name: Install Vercel CLI
         run: npm i --global vercel@latest
@@ -187,17 +182,6 @@ jobs:
         with:
           repository: hashicorp/dev-portal
           path: ./unified-docs-frontend-preview
-      - name: Use cache
-        uses: actions/cache@d4323d4df104b026a6aa633fdb11d772146be0bf # v4.2.2
-        with:
-          path: |
-            ~/.npm
-            ${{ github.workspace }}/unified-docs-frontend-preview/.next/cache
-          # Generate a new cache whenever packages or source files change.
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-${{ hashFiles('**/*.js', '**/*.jsx', '**/*.ts', '**/*.tsx', '**/*.mdx') }}
-          # If source files changed but packages didn't, rebuild from a prior cache.
-          restore-keys: |
-            ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-
 
       - name: Setup Node.js
         uses: actions/setup-node@1d0ff469b7ec7b3cb9d8673fde0c81c44821de2a # v4.2.0
@@ -206,6 +190,12 @@ jobs:
           cache-dependency-path: 'unified-docs-frontend-preview/package-lock.json'
           node-version-file: 'unified-docs-frontend-preview/package.json'
 
+      - name: Cache Next.js build
+        uses: actions/cache@d4323d4df104b026a6aa633fdb11d772146be0bf # v4.2.2
+        with:
+          path: ${{ github.workspace }}/unified-docs-frontend-preview/.next/cache
+          key: ${{ runner.os }}-nextjs-build-devportal-${{ hashFiles('unified-docs-frontend-preview/package-lock.json', 'unified-docs-frontend-preview/next.config.js') }}
+
       - name: Setup Vercel CLI
         run: npm i --global vercel@latest
 

.github/workflows/copy-cloud-docs-for-tfe.yml

@@ -52,7 +52,7 @@ jobs:
       - name: Generate version-metadata for workflow
         working-directory: '${{github.workspace}}/new-docs-pr'
         run: |
-          npm i
+          npm ci
           npm run prebuild -- --only-build-version-metadata
 
       - name: Create the new TFE version folder for RELEASE PR

.github/workflows/deploy-udr.yml

@@ -27,17 +27,11 @@ jobs:
           cache: 'npm'
           node-version-file: 'package.json'
 
-      - name: Use cache
+      - name: Cache Next.js build
         uses: actions/cache@d4323d4df104b026a6aa633fdb11d772146be0bf # v4.2.2
         with:
-          path: |
-            ~/.npm
-            ${{ github.workspace }}/.next/cache
-          # Generate a new cache whenever packages or source files change.
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-${{ hashFiles('**/*.js', '**/*.mjs', '**/*.ts', '**/*.tsx', '**/*.mdx') }}
-          # If source files changed but packages didn't, rebuild from a prior cache.
-          restore-keys: |
-            ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-
+          path: ${{ github.workspace }}/.next/cache
+          key: ${{ runner.os }}-nextjs-build-${{ hashFiles('package-lock.json', 'next.config.js') }}
 
       - name: Install Vercel CLI
         run: npm install --global vercel@latest

.github/workflows/sync-docs-for-tfe.yml

@@ -83,7 +83,7 @@ jobs:
       - name: Generate version-metadata for workflow
         working-directory: '${{github.workspace}}/new-docs'
         run: |
-          npm i
+          npm ci
           npm run prebuild -- --only-build-version-metadata
 
       - name: Checkout HCPTF-diff for new docs version DIFF PR

.github/workflows/test-and-lint.yml

@@ -28,7 +28,7 @@ jobs:
           cache: 'npm'
           node-version-file: 'package.json'
 
-      - run: npm i
+      - run: npm ci
       - run: npm run test
 
   lint:
@@ -46,7 +46,7 @@ jobs:
           node-version-file: 'package.json'
 
       - name: Install Dependencies
-        run: npm i
+        run: npm ci
 
       - name: Run lint check
         run: npm run lint

content/boundary/v0.20.x/content/docs/client-agent/index.mdx

@@ -15,12 +15,6 @@ When the Boundary Client Agent runs alongside an authenticated Boundary client,
 If you enter a hostname that matches a Boundary alias that the client is authorized to establish a session to, Boundary automatically generates the session and transparently proxies the connection on your behalf.
 If the Boundary Client Agent cannot find an alias, or if there are any issues with authentication, network connectivity, or latency, the Client Agent defers DNS resolution to the previously configured DNS resolvers.
 
-<Note>
-
-You must enable both IPv4 and IPv6 protocols for your environment to ensure the Client Agent can start and perform DNS lookups.
-
-</Note>
-
 Currently HashiCorp tests the Client Agent on the following operating systems:
 
 - macOS 14

content/boundary/v0.20.x/content/docs/interoperability-matrix/index.mdx

@@ -52,10 +52,10 @@ Any patches or updates will be reflected in the minor number.
     <b>Windows version</b>: 2025.2.600.0
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4, 0.19.5, 0.19.6
+    0.19.6, 0.20.1
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4, 0.19.5, 0.19.6
+    0.19.6, 0.20.1
     </td>
     <td style={{verticalAlign: 'middle'}}>
     <b>MacOS</b>: 14.6, 15.3
@@ -76,10 +76,10 @@ Any patches or updates will be reflected in the minor number.
     <b>Windows version</b>: 0.14.14
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4
+    0.20.1
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4
+    0.20.1
     </td>
     <td style={{verticalAlign: 'middle'}}>
     <b>MacOS</b>: 14.6, 15.3
@@ -96,10 +96,10 @@ Any patches or updates will be reflected in the minor number.
     Microsoft Defender for Endpoint
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4, 0.19.5, 0.19.6
+    0.19.6
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4, 0.19.5, 0.19.6
+    0.19.6
     </td>
     <td style={{verticalAlign: 'middle'}}>
     <b>MacOS</b>: 14, 15
@@ -116,10 +116,10 @@ Any patches or updates will be reflected in the minor number.
     Palo Alto GlobalProtect
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.19.5, 0.19.6
+    0.19.6
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.19.5, 0.19.6
+    0.19.6
     </td>
     <td style={{verticalAlign: 'middle'}}>
     <b>MacOS</b>: 14, 15
@@ -136,10 +136,10 @@ Any patches or updates will be reflected in the minor number.
     SentinelOne Singularity
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4, 0.19.5, 0.19.6
+    0.19.6, 0.20.1
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4, 0.19.5, 0.19.6
+    0.19.6, 0.20.1
     </td>
     <td style={{verticalAlign: 'middle'}}>
     <b>MacOS</b>: 14, 15.2
@@ -156,10 +156,10 @@ Any patches or updates will be reflected in the minor number.
     Zscaler ZPA
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4, 0.19.5, 0.19.6
+    0.19.6, 0.20.1
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    0.1.4, 0.19.5, 0.19.6
+    0.19.6, 0.20.1
     </td>
     <td style={{verticalAlign: 'middle'}}>
     <b>MacOS</b>: 15

content/boundary/v0.20.x/content/docs/release-notes/v0_20_0.mdx

@@ -63,6 +63,18 @@ description: >-
     </td>
   </tr>
 
+  <tr>
+    <td style={{verticalAlign: 'middle'}}>
+    Client Agent no longer requires IPv6
+    </td>
+    <td style={{verticalAlign: 'middle'}}>
+    Previously, the Client Agent required you to enable both IPv4 and IPv6 protocols. Beginning with version 0.20.0, the Client Agent will no longer require IPv6.
+    <br /><br />
+    Learn more:&nbsp; <a href="/boundary/docs/client-agent">Boundary Client Agent</a>
+    </td>
+  </tr>
+
+
   </tbody>
 </table>
 

content/boundary/v0.20.x/content/docs/session-recording/index.mdx

@@ -77,7 +77,8 @@ When you estimate storage requirements for the external storage provider, you sh
 
 <Warning>
 
-Boundary supports recorded session files up to 5 GB in size.
+If you use Amazon S3 as your external storage provider, recorded session files cannot be over 5 GB in size due to Amazon's size limitations for PUT operations.
+
 If a recorded session file is over 5 GB, the session details show the recording state as `Failed` and you may not be able to play back the session.
 Be careful when you use Secure File Copy (SCP) to transfer large files during a recorded session because it can result in large recorded session files.