omit cre.yaml from version control note

Author: dev-dist

src/content/cre/account/cli-login.mdx

@@ -5,7 +5,7 @@ title: "Logging in with the CLI"
 metadata:
   description: "Learn how to log in to the CRE CLI: authenticate through your browser, complete 2FA verification, and start using CLI commands."
   datePublished: "2025-11-04"
-  lastModified: "2026-03-26"
+  lastModified: "2026-05-22"
 ---
 
 import { Aside, ClickToZoom } from "@components"
@@ -81,4 +81,9 @@ Login completed successfully
 
 Your CLI session is authenticated and ready to use.
 
-In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`~/.cre/cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+
+{/* prettier-ignore */}
+<Aside type="caution" title="Do not commit cre.yaml">
+  **`~/.cre/cre.yaml`** contains your session credentials. Keep it in `~/.cre/` on your local machine only—never commit it to version control or copy it into a project repository.
+</Aside>

src/content/cre/account/managing-auth.mdx

@@ -5,7 +5,7 @@ title: "Managing Authentication"
 metadata:
   description: "Manage your CRE CLI sessions: check if you're logged in, handle expired sessions, and securely log out when needed."
   datePublished: "2025-11-04"
-  lastModified: "2026-03-26"
+  lastModified: "2026-05-22"
 ---
 
 import { Aside } from "@components"
@@ -18,7 +18,7 @@ To authenticate your CLI with your CRE account, use the `cre login` command. Thi
 
 For detailed login instructions, see the [Logging in with the CLI](/cre/account/cli-login) guide.
 
-Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. Do not commit **`~/.cre/cre.yaml`** to version control. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
 
 ## API key authentication
 

src/content/cre/llms-full-go.txt

@@ -7084,7 +7084,7 @@ Once your account is created:
 
 # Logging in with the CLI
 Source: https://docs.chain.link/cre/account/cli-login
-Last Updated: 2026-03-26
+Last Updated: 2026-05-22
 
 To deploy and manage workflows with the CRE CLI, you need to authenticate your CLI session with your CRE account. This guide walks you through the browser-based login process.
 
@@ -7145,13 +7145,18 @@ Login completed successfully
 
 Your CLI session is authenticated and ready to use.
 
-In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`~/.cre/cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+
+
+<Aside type="caution" title="Do not commit cre.yaml">
+  **`~/.cre/cre.yaml`** contains your session credentials. Keep it in `~/.cre/` on your local machine only—never commit it to version control or copy it into a project repository.
+</Aside>
 
 ---
 
 # Managing Authentication
 Source: https://docs.chain.link/cre/account/managing-auth
-Last Updated: 2026-03-26
+Last Updated: 2026-05-22
 
 This guide covers how to manage your CLI authentication, including browser-based login, API key authentication, checking your status, handling session expiration, and logging out.
 
@@ -7161,7 +7166,7 @@ To authenticate your CLI with your CRE account, use the `cre login` command. Thi
 
 For detailed login instructions, see the [Logging in with the CLI](/cre/account/cli-login) guide.
 
-Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. Do not commit **`~/.cre/cre.yaml`** to version control. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
 
 ## API key authentication
 
@@ -8387,7 +8392,7 @@ The typical workflow development process uses these commands in sequence:
 
 # Authentication Commands
 Source: https://docs.chain.link/cre/reference/cli/authentication
-Last Updated: 2026-05-08
+Last Updated: 2026-05-22
 
 The CRE CLI supports two authentication methods:
 
@@ -8483,8 +8488,8 @@ In a CI/CD pipeline, configure `CRE_API_KEY` as a secret environment variable in
 After a successful browser login — and when using an API key for commands that load credentials — the CLI stores **tenant context** at **`~/.cre/context.yaml`**. This file comes from the platform’s **`getTenantConfig`** data: a **registry manifest** for your organization so the CLI knows your CRE environment layout (for example vault gateway URL, registries, and allowed secrets auth flows per registry). Values are grouped under your CRE environment name (such as `PRODUCTION`).
 
 
-<Aside type="note" title="Credentials vs tenant context">
-  **`cre.yaml`** holds authentication tokens for your session. **`context.yaml`** holds **tenant configuration** returned by the platform, not secrets. **`cre logout`** removes both files from your machine.
+<Aside type="caution" title="Keep credential files out of version control">
+  **`~/.cre/cre.yaml`** holds authentication tokens for your session. Do not commit it to version control or copy it into your project repository—it belongs only in `~/.cre/` on your local machine. If you copy `cre.yaml` elsewhere, add it to `.gitignore` so it is not tracked. **`context.yaml`** holds **tenant configuration** returned by the platform, not secrets. **`cre logout`** removes both files from your machine.
 </Aside>
 
 The following example is **illustrative** only; your registries, addresses, and flow lists depend on your organization and environment.

src/content/cre/llms-full-ts.txt

@@ -6636,7 +6636,7 @@ Once your account is created:
 
 # Logging in with the CLI
 Source: https://docs.chain.link/cre/account/cli-login
-Last Updated: 2026-03-26
+Last Updated: 2026-05-22
 
 To deploy and manage workflows with the CRE CLI, you need to authenticate your CLI session with your CRE account. This guide walks you through the browser-based login process.
 
@@ -6697,13 +6697,18 @@ Login completed successfully
 
 Your CLI session is authenticated and ready to use.
 
-In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`~/.cre/cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+
+
+<Aside type="caution" title="Do not commit cre.yaml">
+  **`~/.cre/cre.yaml`** contains your session credentials. Keep it in `~/.cre/` on your local machine only—never commit it to version control or copy it into a project repository.
+</Aside>
 
 ---
 
 # Managing Authentication
 Source: https://docs.chain.link/cre/account/managing-auth
-Last Updated: 2026-03-26
+Last Updated: 2026-05-22
 
 This guide covers how to manage your CLI authentication, including browser-based login, API key authentication, checking your status, handling session expiration, and logging out.
 
@@ -6713,7 +6718,7 @@ To authenticate your CLI with your CRE account, use the `cre login` command. Thi
 
 For detailed login instructions, see the [Logging in with the CLI](/cre/account/cli-login) guide.
 
-Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
+Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. Do not commit **`~/.cre/cre.yaml`** to version control. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache).
 
 ## API key authentication
 
@@ -8000,7 +8005,7 @@ The typical workflow development process uses these commands in sequence:
 
 # Authentication Commands
 Source: https://docs.chain.link/cre/reference/cli/authentication
-Last Updated: 2026-05-08
+Last Updated: 2026-05-22
 
 The CRE CLI supports two authentication methods:
 
@@ -8096,8 +8101,8 @@ In a CI/CD pipeline, configure `CRE_API_KEY` as a secret environment variable in
 After a successful browser login — and when using an API key for commands that load credentials — the CLI stores **tenant context** at **`~/.cre/context.yaml`**. This file comes from the platform’s **`getTenantConfig`** data: a **registry manifest** for your organization so the CLI knows your CRE environment layout (for example vault gateway URL, registries, and allowed secrets auth flows per registry). Values are grouped under your CRE environment name (such as `PRODUCTION`).
 
 
-<Aside type="note" title="Credentials vs tenant context">
-  **`cre.yaml`** holds authentication tokens for your session. **`context.yaml`** holds **tenant configuration** returned by the platform, not secrets. **`cre logout`** removes both files from your machine.
+<Aside type="caution" title="Keep credential files out of version control">
+  **`~/.cre/cre.yaml`** holds authentication tokens for your session. Do not commit it to version control or copy it into your project repository—it belongs only in `~/.cre/` on your local machine. If you copy `cre.yaml` elsewhere, add it to `.gitignore` so it is not tracked. **`context.yaml`** holds **tenant configuration** returned by the platform, not secrets. **`cre logout`** removes both files from your machine.
 </Aside>
 
 The following example is **illustrative** only; your registries, addresses, and flow lists depend on your organization and environment.

src/content/cre/reference/cli/authentication.mdx

@@ -5,7 +5,7 @@ title: "Authentication Commands"
 metadata:
   description: "Manage your CLI authentication: browser-based login, API key authentication for CI/CD, and session management commands."
   datePublished: "2025-11-04"
-  lastModified: "2026-05-08"
+  lastModified: "2026-05-22"
 ---
 
 import { Aside } from "@components"
@@ -104,8 +104,8 @@ In a CI/CD pipeline, configure `CRE_API_KEY` as a secret environment variable in
 After a successful browser login — and when using an API key for commands that load credentials — the CLI stores **tenant context** at **`~/.cre/context.yaml`**. This file comes from the platform’s **`getTenantConfig`** data: a **registry manifest** for your organization so the CLI knows your CRE environment layout (for example vault gateway URL, registries, and allowed secrets auth flows per registry). Values are grouped under your CRE environment name (such as `PRODUCTION`).
 
 {/* prettier-ignore */}
-<Aside type="note" title="Credentials vs tenant context">
-  **`cre.yaml`** holds authentication tokens for your session. **`context.yaml`** holds **tenant configuration** returned by the platform, not secrets. **`cre logout`** removes both files from your machine.
+<Aside type="caution" title="Keep credential files out of version control">
+  **`~/.cre/cre.yaml`** holds authentication tokens for your session. Do not commit it to version control or copy it into your project repository—it belongs only in `~/.cre/` on your local machine. If you copy `cre.yaml` elsewhere, add it to `.gitignore` so it is not tracked. **`context.yaml`** holds **tenant configuration** returned by the platform, not secrets. **`cre logout`** removes both files from your machine.
 </Aside>
 
 The following example is **illustrative** only; your registries, addresses, and flow lists depend on your organization and environment.