chore: update deps

Author: Nsttt

apps/ai/docs/index.mdx

@@ -5,4 +5,3 @@ sidebar: false
 outline: false
 lastUpdated: false
 ---
-

apps/ai/module-federation.config.ts

@@ -5,6 +5,6 @@ export default createModuleFederationConfig({
   name: 'ai_docs',
   exposes: {
     './intro': './docs/index.mdx',
-    './hello': './docs/hello.mdx'
+    './hello': './docs/hello.mdx',
   },
 });

apps/ai/package.json

@@ -11,7 +11,7 @@
   },
   "dependencies": {
     "@module-federation/rspress-plugin": "^0.18.3",
-    "@rspress/core": "2.0.0-beta.29",
+    "@rspress/core": "2.0.0-beta.31",
     "@zephyr-docs/shared": "workspace:*"
   },
   "devDependencies": {

apps/cloud/docs/cloud.mdx

@@ -5,7 +5,7 @@ description: With Zephyr's bring your own cloud feature, you can use Zephyr with
 
 import { Steps, Badge } from '@rspress/core/theme';
 import { Separator, Button, CardLayout } from '@zephyr-docs/shared';
-import { CloudProviderCards} from "../components/cloud-provider"
+import { CloudProviderCards } from '../components/cloud-provider';
 
 # Manage Cloud Providers on Zephyr
 
@@ -15,10 +15,10 @@ With BYOC, users are able to _manage configuration_, _understand the underlying
 
 Users belong to an organization can manage and configure cloud providers on Zephyr's [dashboard](https://app.zephyr-cloud.io), and user's organization gets connected with cloud provider account by creating an integration under **Deployment Integration** tab.
 
-## Choose your Cloud provider 
+## Choose your Cloud provider
 
 <CardLayout>
-<CloudProviderCards/>
+  <CloudProviderCards />
 </CardLayout>
 
 ## About Deployment Integrations
@@ -45,9 +45,9 @@ For detailed instructions on updating your deployment integrations, see our [Upd
 Zephyr regularly releases updates to deployment integrations that provide:
 
 - **New Features**: Access to the latest Zephyr capabilities and cloud provider features
-- **Performance Improvements**: Faster deployments and better resource utilization  
+- **Performance Improvements**: Faster deployments and better resource utilization
 - **Security Updates**: Latest security patches and compliance improvements
 - **Bug Fixes**: Resolution of known issues and edge cases
 - **Compatibility**: Support for new versions of bundlers and frameworks
 
-The beauty of Zephyr's integration system is that these updates happen at the infrastructure level, meaning your development team can benefit from improvements without modifying their build processes, deployment scripts, or workflows.
+The beauty of Zephyr's integration system is that these updates happen at the infrastructure level, meaning your development team can benefit from improvements without modifying their build processes, deployment scripts, or workflows.

apps/cloud/docs/cloud/akamai.mdx

@@ -51,11 +51,11 @@ Before proceeding, you will need some data from Akamai:
 
 | API                               | Access Level |
 | :-------------------------------- | :----------: |
-| CPcode and Reporting group (cprg) | READ-WRITE   |
-| Edge Hostnames API (hapi)         | READ-WRITE   |
-| EdgeKV                            | READ-WRITE   |
-| EdgeWorkers                       | READ-WRITE   |
-| Property Manager (PAPI)           | READ-WRITE   |
+| CPcode and Reporting group (cprg) |  READ-WRITE  |
+| Edge Hostnames API (hapi)         |  READ-WRITE  |
+| EdgeKV                            |  READ-WRITE  |
+| EdgeWorkers                       |  READ-WRITE  |
+| Property Manager (PAPI)           |  READ-WRITE  |
 
 - Copy or download token and add `[default]` as a header, so token will look like:
 
@@ -85,50 +85,48 @@ client_token = YOUR_CLIENT_TOKEN
 
 Find you product [here](https://techdocs.akamai.com/property-mgr/reference/id-prefixes#common-product-ids) and choose product id regarding contract - **prd_Fresca** or **prd_SPM**
 
-
 ### Configuration Inputs
 
 Details for each input after clicking **Add Integration** under **Akamai**:
 
 <dt>Integration Name</dt>
-<dd>
-  A unique name within your organization, used as a slug.
-</dd>
+<dd>A unique name within your organization, used as a slug.</dd>
 
 <dt>Integration Display Name</dt>
-<dd>
-  The name of the integration shown on the dashboard.
-</dd>
+<dd>The name of the integration shown on the dashboard.</dd>
 
 <dt>API Token</dt>
 <dd>
-  Obtainable from Akamai. [See instructions](#1-api-token) for creating your API token.
+  Obtainable from Akamai. [See instructions](#1-api-token) for creating your API
+  token.
 </dd>
 
 <dt>Domain</dt>
-<dd>
-  Your domain.
-</dd>
+<dd>Your domain.</dd>
 
 <dt>Akamai contract id</dt>
 <dd>
-  Obtainable from Akamai. [See instructions](#2-contract-id) for getting your contract id.
+  Obtainable from Akamai. [See instructions](#2-contract-id) for getting your
+  contract id.
 </dd>
 
 <dt>Akamai group id</dt>
 <dd>
-  Obtainable from Akamai. [See instructions](#3-group-id) for getting your group id.
+  Obtainable from Akamai. [See instructions](#3-group-id) for getting your group
+  id.
 </dd>
 
 <dt>Akamai product id</dt>
 <dd>
-  Obtainable from Akamai. [See instructions](#4-product-id) for getting your product id.
+  Obtainable from Akamai. [See instructions](#4-product-id) for getting your
+  product id.
 </dd>
 
 <dt>Set Integration as Default</dt>
 <dd>
   When set as default, all Zephyr deployments will use this integration until a
-  new one (default integration) is set. Deployment using integration won't work until Akamai worker and property become activated.
+  new one (default integration) is set. Deployment using integration won't work
+  until Akamai worker and property become activated.
 </dd>
 
 ### Validate domain and setup DNS
@@ -141,11 +139,11 @@ Details for each input after clicking **Add Integration** under **Akamai**:
 - Go to your domain provider (e.g., GoDaddy)
 - Add some CNAME records
 
-  | Subdomain                         | Type  | Value                                      |
-  |-----------------------------------|-------|--------------------------------------------|
-  | _acme-challenge.ze.yourdomain.com | CNAME | < value from verification record >         |
-  | ze.yourdomain.com                 | CNAME | ze.yourdomain.com.edgesuite.net.           |
-  | *.ze.yourdomain.com               | CNAME | ze.yourdomain.com.edgesuite.net.           |
+  | Subdomain                          | Type  | Value                              |
+  | ---------------------------------- | ----- | ---------------------------------- |
+  | \_acme-challenge.ze.yourdomain.com | CNAME | < value from verification record > |
+  | ze.yourdomain.com                  | CNAME | ze.yourdomain.com.edgesuite.net.   |
+  | \*.ze.yourdomain.com               | CNAME | ze.yourdomain.com.edgesuite.net.   |
 
 ### Wait until worker and property become activated
 
@@ -226,7 +224,7 @@ const { promisify } = require('node:util');
 const edgercPath = homedir() + '/.edgerc';
 const edgercSection = 'default';
 const eg = new EdgeGrid({
-path: edgercPath,
+  path: edgercPath,
   section: edgercSection,
 });
 
@@ -235,24 +233,23 @@ const network = process.env.NETWORK || 'production'; // staging or production
 
 eg.auth({
   path: `/edgekv/v1/networks/${network}/namespaces/${namespaceId}`,
-    method: 'DELETE',
-    headers: {
+  method: 'DELETE',
+  headers: {
     'Content-Type': 'application/json',
-      Accept: 'application/json',
+    Accept: 'application/json',
   },
   body: {},
 });
 
 const send = promisify(eg.send.bind(eg));
-  send()
+send()
   .then(({ data }) => {
     console.log('Namespace deleting result', data);
   })
   .catch((error) => {
     console.error('Namespace deleting error', error);
     process.exit(1);
   });
-
 ```
 
 ### Revoke EdgeKV access token
@@ -268,18 +265,18 @@ const { promisify } = require('node:util');
 const edgercPath = homedir() + '/.edgerc';
 const edgercSection = 'default';
 const eg = new EdgeGrid({
-path: edgercPath,
+  path: edgercPath,
   section: edgercSection,
 });
 
 const tokenName = process.env.TOKEN_NAME;
 
 eg.auth({
   path: `/edgekv/v1/tokens/${tokenName}`,
-    method: 'DELETE',
-    headers: {
+  method: 'DELETE',
+  headers: {
     'Content-Type': 'application/json',
-      Accept: 'application/json',
+    Accept: 'application/json',
   },
   body: {},
 });
@@ -293,5 +290,4 @@ send()
     console.error('Token revoking error', error);
     process.exit(1);
   });
-
 ```

apps/cloud/docs/cloud/aws.mdx

@@ -98,34 +98,28 @@ aws_secret_access_key = YOUR_ACCESS_KEY_SECRET
 Details for each input after clicking **Add Integration** under **AWS**:
 
 <dt>Integration Name</dt>
-<dd>
-  A unique name within your organization, used as a slug.
-</dd>
+<dd>A unique name within your organization, used as a slug.</dd>
 
 <dt>Integration Display Name</dt>
-<dd>
-  The name of the integration shown on the dashboard.
-</dd>
+<dd>The name of the integration shown on the dashboard.</dd>
 
 <dt>API Token</dt>
 <dd>
-  Obtainable from AWS. [See instructions](#1-api-token) for creating your API token.
+  Obtainable from AWS. [See instructions](#1-api-token) for creating your API
+  token.
 </dd>
 
 <dt>Domain</dt>
-<dd>
-  Your domain.
-</dd>
+<dd>Your domain.</dd>
 
 <dt>Certificate arn</dt>
-<dd>
-  Certificate arn for domain (ze.your.domain)
-</dd>
+<dd>Certificate arn for domain (ze.your.domain)</dd>
 
 <dt>Set Integration as Default</dt>
 <dd>
   When set as default, all Zephyr deployments will use this integration until a
-  new one (default integration) is set. Deployment using integration won't work until AWS worker and property become activated.
+  new one (default integration) is set. Deployment using integration won't work
+  until AWS worker and property become activated.
 </dd>
 
 ### Validate domain and setup DNS
@@ -134,10 +128,10 @@ Details for each input after clicking **Add Integration** under **AWS**:
 - Find you domain
 - Copy value from `Domain name (standard)` column and add DNS records described in the table below
 
-| Subdomain                         | Type  | Value                                      |
-|-----------------------------------|-------|--------------------------------------------|
-| ze.yourdomain.com                 | CNAME | < Domain name value >                      |
-| *.ze.yourdomain.com               | CNAME | < Domain name value >                      |
+| Subdomain            | Type  | Value                 |
+| -------------------- | ----- | --------------------- |
+| ze.yourdomain.com    | CNAME | < Domain name value > |
+| \*.ze.yourdomain.com | CNAME | < Domain name value > |
 
 </Steps>
 
@@ -679,7 +673,7 @@ log "==> PHASE 2 completed."
 #### Collect necessary data
 
 | Variable          | Where to find in the AWS dashboard | Description                                          |
-|-------------------|------------------------------------|------------------------------------------------------|
+| ----------------- | ---------------------------------- | ---------------------------------------------------- |
 | DDB_TABLES        | DynamoDB -> Tables                 | envs and snaphots table names                        |
 | LOG_GROUPS        | Cloudwatch -> Log groups           | Cloudwatch log groups of Lambda@Edge function        |
 | CF_DIST_ID        | Cloudfront -> Distributions        | Cloudfron distribution id                            |

apps/cloud/docs/cloud/cloudflare.mdx

@@ -8,7 +8,6 @@ import { Steps, Badge } from '@rspress/core/theme';
 import { Separator } from '@zephyr-docs/shared';
 import { CustomDomain } from '../../components/cloud-provider.tsx';
 
-
 # Configure Cloudflare on Zephyr
 
 Originally launched as an email spam tracker, Cloudflare today offers extensive capabilities for users to register, manage domains as a registrar, and monitor, secure, and configure an entire IT infrastructure.
@@ -102,13 +101,15 @@ Details for each input after clicking **Add Integration** under **Cloudflare**:
 <dd>The name of the integration shown on the dashboard.</dd>
 
 <dt>Delimiter</dt>
-<dd>Choose the delimiter for application subdomains: `-` (your deploy URL will be `*-ze.your.domain`) or `.` (your deploy URL will be `*.ze.your.domain`) </dd>
+<dd>
+  Choose the delimiter for application subdomains: `-` (your deploy URL will be
+  `*-ze.your.domain`) or `.` (your deploy URL will be `*.ze.your.domain`){' '}
+</dd>
 
 <dt>API Token</dt>
 <dd>
-  Obtainable from Cloudflare. [See
-  instructions](#2-api-token) for creating
-  your API token.
+  Obtainable from Cloudflare. [See instructions](#2-api-token) for creating your
+  API token.
 </dd>
 
 <dt>Zone ID</dt>
@@ -167,7 +168,7 @@ A CNAME record will be added to your domain with the following details:
 
 | Type  | Name |       Content        | Proxy Status | TTL  |
 | :---: | :--: | :------------------: | :----------: | :--: |
-| CNAME | `*`  | `ze.zephyrcloud.app` |  ✔ Proxied   | Auto |
+| CNAME | `*`  | `ze.zephyrcloud.app` |  ✔ Proxied  | Auto |
 
 ### Deployment and Inspecting Assets
 

apps/cloud/docs/cloud/fastly.mdx

@@ -26,7 +26,7 @@ Fastly's best-in-class edge cloud platform helps you modernize and automate to m
 
 ## Integration Setup
 
-:::info 
+:::info
 API Token Configuration
 
 - Create your API token [here](https://manage.fastly.com/account/personal/tokens). For detailed steps on creating an API token, refer to the [Fastly API token documentation](https://www.fastly.com/documentation/guides/account-info/account-management/using-api-tokens/).
@@ -43,10 +43,10 @@ API Token Configuration
 1. Navigate to the Organization Level in Zephyr
 2. Select **Settings** tab, choose **Deployment integration** and then click on **Available**
 3. On this page choose **Fastly Integration** and click on **Add integration**
-3. Complete the form with:
+4. Complete the form with:
    - API Token
    - Site ID
-4. Click **Add Integration**
+5. Click **Add Integration**
 
 ### Configure DNS Domain
 
@@ -55,7 +55,7 @@ API Token Configuration
 3. Add two domains:
    - `ze.yourdomain.com`
    - `*.ze.yourdomain.com`
-4. Click "Add" then "Submit" 
+4. Click "Add" then "Submit"
 5. You'll see a "Pending verification" status
 6. You will see CNAME records here that you'll need for the next step
 
@@ -67,18 +67,19 @@ API Token Configuration
 4. Click "View/Edit" once verified
 5. Create two CNAME records:
 
-| Subdomain | Type | Priority | Target |
-|-----------|------|----------|--------|
-| ze.yourdomain.com | CNAME | - | t.sni.global.fastly.net |
-| *.ze.yourdomain.com | CNAME | - | t.sni.global.fastly.net |
+| Subdomain            | Type  | Priority | Target                  |
+| -------------------- | ----- | -------- | ----------------------- |
+| ze.yourdomain.com    | CNAME | -        | t.sni.global.fastly.net |
+| \*.ze.yourdomain.com | CNAME | -        | t.sni.global.fastly.net |
 
-*Note: Actual target values will be shown in your Fastly dashboard*
+_Note: Actual target values will be shown in your Fastly dashboard_
 
 </Steps>
 
 ## System Components
 
 The integration creates:
+
 - Config store for jwt-secret
 - KV stores:
   - ze-snapshots
@@ -92,4 +93,4 @@ The integration creates:
 2. Build a new application with Zephyr
 3. During deployment:
    - System retrieves site information using provided parameters
-   - Zephyr Plugin uploads build assets to KV stores
+   - Zephyr Plugin uploads build assets to KV stores