diff --git a/public/changelog.json b/public/changelog.json
index 1d834a37b71..a1e81c604e2 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -398,6 +398,13 @@
     }
   },
   "data": [
+    {
+      "category": "release",
+      "date": "2026-04-10",
+      "description": "CRE CLI version 1.10.0 is now available. This release adds optional org ownership for secrets — set `CRE_CLI_SECRETS_ORG_OWNED: true` in your target configuration to use your org ID as the secret owner across `cre secrets create`, `cre secrets update`, `cre secrets delete`, and `cre secrets list`. This is useful for teams sharing secrets across multiple workflows. It also fixes a struct prefix bug in the EVM Bindings generator.\n\nUpdate your CLI by running `cre update` when prompted, or follow the [CLI Installation guide](https://docs.chain.link/cre/getting-started/cli-installation) for fresh installations.\n\n[See all changes on GitHub](https://github.com/smartcontractkit/cre-cli/compare/v1.9.0...v1.10.0)",
+      "title": "CRE CLI v1.10.0 — Org-Owned Secrets and EVM Bindings Fix",
+      "topic": "CRE"
+    },
     {
       "category": "integration",
       "date": "2025-04-10",
diff --git a/src/components/DownloadButton.tsx b/src/components/DownloadButton.tsx
index 64e8fc1e30c..42448a64c7a 100644
--- a/src/components/DownloadButton.tsx
+++ b/src/components/DownloadButton.tsx
@@ -1,5 +1,7 @@
 /** @jsxImportSource preact */
 
+import { VERSIONS } from "@config/versions/index.ts"
+
 export const DownloadButton = () => {
   const buttonStyle = {
     padding: "12px 24px",
@@ -15,7 +17,8 @@ export const DownloadButton = () => {
   }
 
   const handleClick = () => {
-    window.open("https://github.com/smartcontractkit/cre-cli/releases/tag/v1.2.0", "_blank", "noopener,noreferrer")
+    const version = VERSIONS["cre-cli"].LATEST
+    window.open(`https://github.com/smartcontractkit/cre-cli/releases/tag/${version}`, "_blank", "noopener,noreferrer")
   }
 
   const handleMouseOver = (e) => {
diff --git a/src/config/versions/index.ts b/src/config/versions/index.ts
index ea2e5677817..d6c0fdf4307 100644
--- a/src/config/versions/index.ts
+++ b/src/config/versions/index.ts
@@ -1,5 +1,3 @@
-import type { Collection } from "~/content.config.ts"
-
 // Base type for version configuration
 export interface VersionConfig {
   LATEST: string
@@ -77,6 +75,16 @@ export const VERSIONS = {
       "v0.2.3": "2024-11-30T00:00:00Z", // 30 November 2024
     },
   },
+  // CRE CLI Versions — update LATEST here for each new release
+  "cre-cli": {
+    LATEST: "v1.10.0",
+    ALL: ["v1.10.0", "v1.9.0", "v1.8.0"] as const,
+    RELEASE_DATES: {
+      "v1.10.0": "2026-04-10T00:00:00Z",
+      "v1.9.0": "2026-04-02T00:00:00Z",
+      "v1.8.0": "2026-03-26T00:00:00Z",
+    },
+  },
   // Add new products here following the same pattern
   // example: {
   //   LATEST: "v1.0.0",
@@ -90,8 +98,5 @@ export const VERSIONS = {
 
 // Type helpers
 export type ProductVersions = {
-  [K in Collection]?: VersionConfig | VMVersionConfig
+  [key: string]: VersionConfig | VMVersionConfig
 }
-
-// Re-export for convenience
-export type { Collection }
diff --git a/src/content/cre/getting-started/cli-installation/macos-linux.mdx b/src/content/cre/getting-started/cli-installation/macos-linux.mdx
index dd9c4f62b3c..62ed9590f43 100644
--- a/src/content/cre/getting-started/cli-installation/macos-linux.mdx
+++ b/src/content/cre/getting-started/cli-installation/macos-linux.mdx
@@ -5,13 +5,16 @@ title: "Installing the CRE CLI on macOS and Linux"
 metadata:
   description: "Install the CRE CLI on macOS or Linux: choose automatic script or manual setup, verify integrity, and get ready to build workflows."
   datePublished: "2025-11-04"
-  lastModified: "2026-03-17"
+  lastModified: "2026-04-10"
 ---
 
 import { Aside, CopyText, PageTabs } from "@components"
 import { DownloadButton } from "~/components/DownloadButton.tsx"
+import { VERSIONS } from "~/config/versions"
 
-This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is **v1.5.0**.
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
+
+This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is **{CRE_CLI_VERSION}**.
 
 <PageTabs
   pages={[
@@ -66,7 +69,7 @@ After the script completes, verify the installation:
 cre version
 ```
 
-**Expected output:** `CRE CLI version v1.5.0`
+**Expected output:** `CRE CLI version {CRE_CLI_VERSION}`
 
 <Aside type="note" title="macOS Gatekeeper">
   If you see warnings about "unrecognized developer/source" on macOS, run:{" "}
@@ -120,11 +123,11 @@ shasum -a 256 cre_darwin_arm64.zip
 Compare the output with the official checksum from the [CRE CLI releases page](https://github.com/smartcontractkit/cre-cli/releases):
 
 1. Go to https://github.com/smartcontractkit/cre-cli/releases
-1. Find the release version you downloaded (e.g., v1.5.0)
+1. Find the release version you downloaded (e.g., {CRE_CLI_VERSION})
 1. Under the **Assets** section, locate your downloaded file
 1. Compare the SHA-256 checksum shown next to the file with your command output
 
-**Example:** For `cre_darwin_arm64.zip` in release v1.5.0, you'll see something like:
+**Example:** For `cre_darwin_arm64.zip` in release {CRE_CLI_VERSION}, you'll see something like:
 
 ```
 cre_darwin_arm64.zip
@@ -154,7 +157,7 @@ If the checksums match, the file is authentic and safe to install. If they don't
 1. **Rename the extracted binary to `cre`**
 
    ```bash
-   mv cre_v1.5.0_darwin_arm64 cre
+   mv cre_{CRE_CLI_VERSION}_darwin_arm64 cre
    ```
 
 1. **Make it executable**:
@@ -227,7 +230,7 @@ cre version
 
 **Expected output:**
 
-You should see version information: `cre version v1.5.0`.
+You should see version information: `cre version {CRE_CLI_VERSION}`.
 
 **If it doesn't work:**
 
diff --git a/src/content/cre/getting-started/cli-installation/windows.mdx b/src/content/cre/getting-started/cli-installation/windows.mdx
index f47c16c3fbf..1cb39c24a37 100644
--- a/src/content/cre/getting-started/cli-installation/windows.mdx
+++ b/src/content/cre/getting-started/cli-installation/windows.mdx
@@ -5,13 +5,16 @@ title: "Installing the CRE CLI on Windows"
 metadata:
   description: "Install the CRE CLI on Windows: use PowerShell for quick setup or manual installation, verify integrity, and start building workflows."
   datePublished: "2025-11-04"
-  lastModified: "2026-03-17"
+  lastModified: "2026-04-10"
 ---
 
 import { Aside, CopyText, PageTabs } from "@components"
 import { DownloadButton } from "~/components/DownloadButton.tsx"
+import { VERSIONS } from "~/config/versions"
 
-This page explains how to install the Chainlink Developer Platform CLI (also referred to as the CRE CLI) on Windows. The recommended version at the time of writing is **v1.5.0**.
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
+
+This page explains how to install the Chainlink Developer Platform CLI (also referred to as the CRE CLI) on Windows. The recommended version at the time of writing is **{CRE_CLI_VERSION}**.
 
 <PageTabs
   pages={[
@@ -65,7 +68,7 @@ After the script completes, **open a new PowerShell window** and verify the inst
 cre version
 ```
 
-**Expected output:** `CRE CLI version v1.5.0`
+**Expected output:** `CRE CLI version {CRE_CLI_VERSION}`
 
 ### Manual installation
 
@@ -96,11 +99,11 @@ Get-FileHash cre_windows_amd64.zip -Algorithm SHA256
 Compare the `Hash` value in the output with the official checksum from the [CRE CLI releases page](https://github.com/smartcontractkit/cre-cli/releases):
 
 1. Go to https://github.com/smartcontractkit/cre-cli/releases
-2. Find the release version you downloaded (e.g., v1.5.0)
+2. Find the release version you downloaded (e.g., {CRE_CLI_VERSION})
 3. Under the **Assets** section, locate `cre_windows_amd64.zip`
 4. Compare the SHA-256 checksum shown next to the file with the `Hash` value from your PowerShell output
 
-**Example:** For `cre_windows_amd64.zip` in release v1.5.0, you'll see something like:
+**Example:** For `cre_windows_amd64.zip` in release {CRE_CLI_VERSION}, you'll see something like:
 
 ```
 cre_windows_amd64.zip
@@ -114,7 +117,7 @@ If the checksums match, the file is authentic and safe to install. If they don't
 1. Navigate to the directory where you downloaded the archive.
 1. Right-click the `.zip` file and select **Extract All...**.
 1. Choose a permanent location for the extracted folder (e.g., `C:\Program Files\cre-cli`).
-1. Inside the extracted folder, rename the file `cre_v1.5.0_windows_amd64.exe` to `cre.exe`.
+1. Inside the extracted folder, rename the file `cre_{CRE_CLI_VERSION}_windows_amd64.exe` to `cre.exe`.
 
 #### 3. Add the CLI to your PATH
 
@@ -139,7 +142,7 @@ Open a new **PowerShell** or **Command Prompt** window and run:
 cre version
 ```
 
-You should see version information: `cre version v1.5.0`.
+You should see version information: `cre version {CRE_CLI_VERSION}`.
 
 ## Next steps
 
diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt
index b426f7da5a0..ed568402480 100644
--- a/src/content/cre/llms-full-go.txt
+++ b/src/content/cre/llms-full-go.txt
@@ -448,10 +448,24 @@ To help us assist you faster, please include:
 
 # Release Notes
 Source: https://docs.chain.link/cre/release-notes
-Last Updated: 2026-04-02
+Last Updated: 2026-04-10
 
 This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations.
 
+## CLI v1.10.0 - April 10, 2026
+
+**<a href="https://github.com/smartcontractkit/cre-cli/releases/tag/v1.10.0" target="_blank">CRE CLI version 1.10.0</a> is now available.**
+
+- **Optional org ownership for secrets**: Secrets can now optionally be owned by your organization instead of your individual workflow owner address. Set `CRE_CLI_SECRETS_ORG_OWNED: true` in your target configuration to use your org ID as the secret owner across `cre secrets create`, `cre secrets update`, `cre secrets delete`, and `cre secrets list`. This is useful for teams sharing secrets across multiple workflows. When disabled (the default), behavior is unchanged. See [Secrets Management Commands](/cre/reference/cli/secrets#org-owned-secrets) for details.
+- **EVM Bindings generator fix**: Corrected a struct prefix bug in the EVM Bindings generator that could produce incorrect struct names under certain conditions.
+
+**How to update:**
+
+- **Automatic update**: When you run any CRE command, the CLI will automatically detect if a newer version is available and prompt you to update. Simply run `cre update` to install the latest version.
+- **Fresh installation**: If you're installing the CLI for the first time, follow the [CLI Installation guide](/cre/getting-started/cli-installation).
+
+[See all changes on GitHub](https://github.com/smartcontractkit/cre-cli/compare/v1.9.0...v1.10.0)
+
 ## CLI v1.9.0 - April 2, 2026
 
 **<a href="https://github.com/smartcontractkit/cre-cli/releases/tag/v1.9.0" target="_blank">CRE CLI version 1.9.0</a> is now available.**
@@ -953,9 +967,11 @@ These guides explain how to install the Chainlink Developer Platform CLI (also r
 
 # Installing the CRE CLI on macOS and Linux
 Source: https://docs.chain.link/cre/getting-started/cli-installation/macos-linux
-Last Updated: 2026-03-17
+Last Updated: 2026-04-10
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
-This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is **v1.5.0**.
+This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is **{CRE_CLI_VERSION}**.
 
 ## Installation
 
@@ -986,7 +1002,7 @@ After the script completes, verify the installation:
 cre version
 ```
 
-**Expected output:** `CRE CLI version v1.5.0`
+**Expected output:** `CRE CLI version {CRE_CLI_VERSION}`
 
 <Aside type="note" title="macOS Gatekeeper">
   If you see warnings about "unrecognized developer/source" on macOS, run:{" "}
@@ -1034,11 +1050,11 @@ shasum -a 256 cre_darwin_arm64.zip
 Compare the output with the official checksum from the [CRE CLI releases page](https://github.com/smartcontractkit/cre-cli/releases):
 
 1. Go to [https://github.com/smartcontractkit/cre-cli/releases](https://github.com/smartcontractkit/cre-cli/releases)
-2. Find the release version you downloaded (e.g., v1.5.0)
+2. Find the release version you downloaded (e.g., {CRE_CLI_VERSION})
 3. Under the **Assets** section, locate your downloaded file
 4. Compare the SHA-256 checksum shown next to the file with your command output
 
-**Example:** For `cre_darwin_arm64.zip` in release v1.5.0, you'll see something like:
+**Example:** For `cre_darwin_arm64.zip` in release {CRE_CLI_VERSION}, you'll see something like:
 
 ```
 cre_darwin_arm64.zip
@@ -1068,7 +1084,7 @@ If the checksums match, the file is authentic and safe to install. If they don't
 3. **Rename the extracted binary to `cre`**
 
    ```bash
-   mv cre_v1.5.0_darwin_arm64 cre
+   mv cre_{CRE_CLI_VERSION}_darwin_arm64 cre
    ```
 
 4. **Make it executable**:
@@ -1141,7 +1157,7 @@ cre version
 
 **Expected output:**
 
-You should see version information: `cre version v1.5.0`.
+You should see version information: `cre version {CRE_CLI_VERSION}`.
 
 **If it doesn't work:**
 
@@ -1178,9 +1194,11 @@ Once you're authenticated, you're ready to build your first workflow:
 
 # Installing the CRE CLI on Windows
 Source: https://docs.chain.link/cre/getting-started/cli-installation/windows
-Last Updated: 2026-03-17
+Last Updated: 2026-04-10
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
-This page explains how to install the Chainlink Developer Platform CLI (also referred to as the CRE CLI) on Windows. The recommended version at the time of writing is **v1.5.0**.
+This page explains how to install the Chainlink Developer Platform CLI (also referred to as the CRE CLI) on Windows. The recommended version at the time of writing is **{CRE_CLI_VERSION}**.
 
 ## Installation
 
@@ -1210,7 +1228,7 @@ After the script completes, **open a new PowerShell window** and verify the inst
 cre version
 ```
 
-**Expected output:** `CRE CLI version v1.5.0`
+**Expected output:** `CRE CLI version {CRE_CLI_VERSION}`
 
 ### Manual installation
 
@@ -1237,11 +1255,11 @@ Get-FileHash cre_windows_amd64.zip -Algorithm SHA256
 Compare the `Hash` value in the output with the official checksum from the [CRE CLI releases page](https://github.com/smartcontractkit/cre-cli/releases):
 
 1. Go to [https://github.com/smartcontractkit/cre-cli/releases](https://github.com/smartcontractkit/cre-cli/releases)
-2. Find the release version you downloaded (e.g., v1.5.0)
+2. Find the release version you downloaded (e.g., {CRE_CLI_VERSION})
 3. Under the **Assets** section, locate `cre_windows_amd64.zip`
 4. Compare the SHA-256 checksum shown next to the file with the `Hash` value from your PowerShell output
 
-**Example:** For `cre_windows_amd64.zip` in release v1.5.0, you'll see something like:
+**Example:** For `cre_windows_amd64.zip` in release {CRE_CLI_VERSION}, you'll see something like:
 
 ```
 cre_windows_amd64.zip
@@ -1255,7 +1273,7 @@ If the checksums match, the file is authentic and safe to install. If they don't
 1. Navigate to the directory where you downloaded the archive.
 2. Right-click the `.zip` file and select **Extract All...**.
 3. Choose a permanent location for the extracted folder (e.g., `C:\Program Files\cre-cli`).
-4. Inside the extracted folder, rename the file `cre_v1.5.0_windows_amd64.exe` to `cre.exe`.
+4. Inside the extracted folder, rename the file `cre_{CRE_CLI_VERSION}_windows_amd64.exe` to `cre.exe`.
 
 #### 3. Add the CLI to your PATH
 
@@ -1280,7 +1298,7 @@ Open a new **PowerShell** or **Command Prompt** window and run:
 cre version
 ```
 
-You should see version information: `cre version v1.5.0`.
+You should see version information: `cre version {CRE_CLI_VERSION}`.
 
 ## Next steps
 
@@ -8254,11 +8272,13 @@ See the [repository README](https://github.com/smartcontractkit/cre-gcp-predicti
 
 # CLI Reference
 Source: https://docs.chain.link/cre/reference/cli
-Last Updated: 2026-03-26
+Last Updated: 2026-04-10
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
-<Aside type="note" title="Required CLI Version: v1.5.0">
-  To ensure compatibility with the guides and examples in this documentation, please use version `v1.5.0` of the CRE
-  CLI. You can check your installed version by running `cre version`. Refer to the [CLI
+<Aside type="note" title={`Required CLI Version: ${CRE_CLI_VERSION}`}>
+  To ensure compatibility with the guides and examples in this documentation, please use version `{CRE_CLI_VERSION}` of
+  the CRE CLI. You can check your installed version by running `cre version`. Refer to the [CLI
   Installation](/cre/getting-started/cli-installation/macos-linux) guide for more information.
 </Aside>
 
@@ -9196,7 +9216,7 @@ The typical workflow lifecycle uses these commands in sequence:
 
 # Secrets Management Commands
 Source: https://docs.chain.link/cre/reference/cli/secrets
-Last Updated: 2026-04-02
+Last Updated: 2026-04-10
 
 <Aside type="note" title="Authentication required">
   Running the commands on this page requires you to be logged in with the CRE CLI. Run `cre whoami` in your terminal to
@@ -9217,6 +9237,27 @@ Starting with CLI v1.9.0, secrets operations use a **browser-based OAuth (PKCE)
 
 Your existing CLI login session (`~/.cre/cre.yaml`) is **not** affected — the vault authorization uses a separate short-lived token. **API key authentication is not supported** for this flow; you must be logged in with `cre login`.
 
+## Org-owned secrets
+
+Starting with CLI v1.10.0, secrets can optionally be owned by your **organization** instead of your individual workflow owner address. When the `CRE_CLI_SECRETS_ORG_OWNED` environment variable is set to `true` in your target configuration, all secrets operations use your org ID (from your authenticated session) as the owner identifier rather than your workflow owner address.
+
+This is useful for teams that share secrets across multiple workflows within an organization, as it decouples secret ownership from individual wallet addresses.
+
+**How it works:**
+
+- When `CRE_CLI_SECRETS_ORG_OWNED=true`, the CLI uses your org ID as the TDH2 encryption label and vault secret owner
+- When `CRE_CLI_SECRETS_ORG_OWNED=false` (the default), behavior is unchanged — the workflow owner address is used
+
+**Configuration:**
+
+Add `CRE_CLI_SECRETS_ORG_OWNED: true` to your target environment in your `.env.public` or configuration YAML:
+
+```yaml
+CRE_CLI_SECRETS_ORG_OWNED: true
+```
+
+You must be authenticated with `cre login` and your session must include a valid org ID for this to work.
+
 ## Namespaces
 
 Secrets are organized into **namespaces**, which act as logical groupings (e.g., `"main"`, `"staging"`, `"production"`). All secrets are stored in the `"main"` namespace by default. Currently, `create`, `update`, and `delete` commands only support the default namespace. Custom namespace support may be added in future CLI versions.
@@ -9224,7 +9265,7 @@ Secrets are organized into **namespaces**, which act as logical groupings (e.g.,
 
 <Aside type="note" title="Prerequisites">
   - You must be logged in with `cre login` (interactive login required; API keys are not supported for secrets operations)
-  - Your `workflow-owner-address` must be configured in your project
+  - Your `workflow-owner-address` must be configured in your project (not required when `CRE_CLI_SECRETS_ORG_OWNED=true`)
   - **Production CRE:** only **linked workflow owner** vault authorization is supported for these commands. See ([Using Secrets with Deployed Workflows](/cre/guides/workflow/secrets/using-secrets-deployed))
   - For comprehensive guides on using secrets, see [Managing Secrets](/cre/guides/workflow/secrets)
 </Aside>
@@ -9390,7 +9431,7 @@ cre secrets delete secrets-to-delete.yaml --target production-settings
 
 ## cre secrets list
 
-Lists all secret identifiers for your owner address in a specific namespace.
+Lists all secret identifiers for your owner address (or org ID, when `CRE_CLI_SECRETS_ORG_OWNED=true`) in a specific namespace.
 
 ### Usage
 
@@ -9583,7 +9624,9 @@ Remaining repositories:
 
 # Utility Commands
 Source: https://docs.chain.link/cre/reference/cli/utilities
-Last Updated: 2026-03-17
+Last Updated: 2026-04-10
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
 Utility commands provide helpful information and troubleshooting capabilities.
 
@@ -9633,12 +9676,12 @@ cre version
 **Example output:**
 
 ```bash
-CRE CLI version v1.5.0
+CRE CLI version {CRE_CLI_VERSION}
 ```
 
 
 <Aside type="note" title="Version compatibility">
-  Always check that your CLI version matches the version recommended in the documentation. The current recommended version is **v1.5.0**. See the [CLI Installation guide](/cre/getting-started/cli-installation) for more information.
+  Always check that your CLI version matches the version recommended in the documentation. The current recommended version is **{CRE_CLI_VERSION}**. See the [CLI Installation guide](/cre/getting-started/cli-installation) for more information.
 </Aside>
 
 ## Learn more
diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt
index 5ecc4acdf00..deba7efadb9 100644
--- a/src/content/cre/llms-full-ts.txt
+++ b/src/content/cre/llms-full-ts.txt
@@ -448,10 +448,24 @@ To help us assist you faster, please include:
 
 # Release Notes
 Source: https://docs.chain.link/cre/release-notes
-Last Updated: 2026-04-02
+Last Updated: 2026-04-10
 
 This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations.
 
+## CLI v1.10.0 - April 10, 2026
+
+**<a href="https://github.com/smartcontractkit/cre-cli/releases/tag/v1.10.0" target="_blank">CRE CLI version 1.10.0</a> is now available.**
+
+- **Optional org ownership for secrets**: Secrets can now optionally be owned by your organization instead of your individual workflow owner address. Set `CRE_CLI_SECRETS_ORG_OWNED: true` in your target configuration to use your org ID as the secret owner across `cre secrets create`, `cre secrets update`, `cre secrets delete`, and `cre secrets list`. This is useful for teams sharing secrets across multiple workflows. When disabled (the default), behavior is unchanged. See [Secrets Management Commands](/cre/reference/cli/secrets#org-owned-secrets) for details.
+- **EVM Bindings generator fix**: Corrected a struct prefix bug in the EVM Bindings generator that could produce incorrect struct names under certain conditions.
+
+**How to update:**
+
+- **Automatic update**: When you run any CRE command, the CLI will automatically detect if a newer version is available and prompt you to update. Simply run `cre update` to install the latest version.
+- **Fresh installation**: If you're installing the CLI for the first time, follow the [CLI Installation guide](/cre/getting-started/cli-installation).
+
+[See all changes on GitHub](https://github.com/smartcontractkit/cre-cli/compare/v1.9.0...v1.10.0)
+
 ## CLI v1.9.0 - April 2, 2026
 
 **<a href="https://github.com/smartcontractkit/cre-cli/releases/tag/v1.9.0" target="_blank">CRE CLI version 1.9.0</a> is now available.**
@@ -953,9 +967,11 @@ These guides explain how to install the Chainlink Developer Platform CLI (also r
 
 # Installing the CRE CLI on macOS and Linux
 Source: https://docs.chain.link/cre/getting-started/cli-installation/macos-linux
-Last Updated: 2026-03-17
+Last Updated: 2026-04-10
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
-This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is **v1.5.0**.
+This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is **{CRE_CLI_VERSION}**.
 
 ## Installation
 
@@ -986,7 +1002,7 @@ After the script completes, verify the installation:
 cre version
 ```
 
-**Expected output:** `CRE CLI version v1.5.0`
+**Expected output:** `CRE CLI version {CRE_CLI_VERSION}`
 
 <Aside type="note" title="macOS Gatekeeper">
   If you see warnings about "unrecognized developer/source" on macOS, run:{" "}
@@ -1034,11 +1050,11 @@ shasum -a 256 cre_darwin_arm64.zip
 Compare the output with the official checksum from the [CRE CLI releases page](https://github.com/smartcontractkit/cre-cli/releases):
 
 1. Go to [https://github.com/smartcontractkit/cre-cli/releases](https://github.com/smartcontractkit/cre-cli/releases)
-2. Find the release version you downloaded (e.g., v1.5.0)
+2. Find the release version you downloaded (e.g., {CRE_CLI_VERSION})
 3. Under the **Assets** section, locate your downloaded file
 4. Compare the SHA-256 checksum shown next to the file with your command output
 
-**Example:** For `cre_darwin_arm64.zip` in release v1.5.0, you'll see something like:
+**Example:** For `cre_darwin_arm64.zip` in release {CRE_CLI_VERSION}, you'll see something like:
 
 ```
 cre_darwin_arm64.zip
@@ -1068,7 +1084,7 @@ If the checksums match, the file is authentic and safe to install. If they don't
 3. **Rename the extracted binary to `cre`**
 
    ```bash
-   mv cre_v1.5.0_darwin_arm64 cre
+   mv cre_{CRE_CLI_VERSION}_darwin_arm64 cre
    ```
 
 4. **Make it executable**:
@@ -1141,7 +1157,7 @@ cre version
 
 **Expected output:**
 
-You should see version information: `cre version v1.5.0`.
+You should see version information: `cre version {CRE_CLI_VERSION}`.
 
 **If it doesn't work:**
 
@@ -1178,9 +1194,11 @@ Once you're authenticated, you're ready to build your first workflow:
 
 # Installing the CRE CLI on Windows
 Source: https://docs.chain.link/cre/getting-started/cli-installation/windows
-Last Updated: 2026-03-17
+Last Updated: 2026-04-10
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
-This page explains how to install the Chainlink Developer Platform CLI (also referred to as the CRE CLI) on Windows. The recommended version at the time of writing is **v1.5.0**.
+This page explains how to install the Chainlink Developer Platform CLI (also referred to as the CRE CLI) on Windows. The recommended version at the time of writing is **{CRE_CLI_VERSION}**.
 
 ## Installation
 
@@ -1210,7 +1228,7 @@ After the script completes, **open a new PowerShell window** and verify the inst
 cre version
 ```
 
-**Expected output:** `CRE CLI version v1.5.0`
+**Expected output:** `CRE CLI version {CRE_CLI_VERSION}`
 
 ### Manual installation
 
@@ -1237,11 +1255,11 @@ Get-FileHash cre_windows_amd64.zip -Algorithm SHA256
 Compare the `Hash` value in the output with the official checksum from the [CRE CLI releases page](https://github.com/smartcontractkit/cre-cli/releases):
 
 1. Go to [https://github.com/smartcontractkit/cre-cli/releases](https://github.com/smartcontractkit/cre-cli/releases)
-2. Find the release version you downloaded (e.g., v1.5.0)
+2. Find the release version you downloaded (e.g., {CRE_CLI_VERSION})
 3. Under the **Assets** section, locate `cre_windows_amd64.zip`
 4. Compare the SHA-256 checksum shown next to the file with the `Hash` value from your PowerShell output
 
-**Example:** For `cre_windows_amd64.zip` in release v1.5.0, you'll see something like:
+**Example:** For `cre_windows_amd64.zip` in release {CRE_CLI_VERSION}, you'll see something like:
 
 ```
 cre_windows_amd64.zip
@@ -1255,7 +1273,7 @@ If the checksums match, the file is authentic and safe to install. If they don't
 1. Navigate to the directory where you downloaded the archive.
 2. Right-click the `.zip` file and select **Extract All...**.
 3. Choose a permanent location for the extracted folder (e.g., `C:\Program Files\cre-cli`).
-4. Inside the extracted folder, rename the file `cre_v1.5.0_windows_amd64.exe` to `cre.exe`.
+4. Inside the extracted folder, rename the file `cre_{CRE_CLI_VERSION}_windows_amd64.exe` to `cre.exe`.
 
 #### 3. Add the CLI to your PATH
 
@@ -1280,7 +1298,7 @@ Open a new **PowerShell** or **Command Prompt** window and run:
 cre version
 ```
 
-You should see version information: `cre version v1.5.0`.
+You should see version information: `cre version {CRE_CLI_VERSION}`.
 
 ## Next steps
 
@@ -7408,11 +7426,13 @@ See the [repository README](https://github.com/smartcontractkit/cre-gcp-predicti
 
 # CLI Reference
 Source: https://docs.chain.link/cre/reference/cli
-Last Updated: 2026-03-26
+Last Updated: 2026-04-10
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
-<Aside type="note" title="Required CLI Version: v1.5.0">
-  To ensure compatibility with the guides and examples in this documentation, please use version `v1.5.0` of the CRE
-  CLI. You can check your installed version by running `cre version`. Refer to the [CLI
+<Aside type="note" title={`Required CLI Version: ${CRE_CLI_VERSION}`}>
+  To ensure compatibility with the guides and examples in this documentation, please use version `{CRE_CLI_VERSION}` of
+  the CRE CLI. You can check your installed version by running `cre version`. Refer to the [CLI
   Installation](/cre/getting-started/cli-installation/macos-linux) guide for more information.
 </Aside>
 
@@ -8350,7 +8370,7 @@ The typical workflow lifecycle uses these commands in sequence:
 
 # Secrets Management Commands
 Source: https://docs.chain.link/cre/reference/cli/secrets
-Last Updated: 2026-04-02
+Last Updated: 2026-04-10
 
 <Aside type="note" title="Authentication required">
   Running the commands on this page requires you to be logged in with the CRE CLI. Run `cre whoami` in your terminal to
@@ -8371,6 +8391,27 @@ Starting with CLI v1.9.0, secrets operations use a **browser-based OAuth (PKCE)
 
 Your existing CLI login session (`~/.cre/cre.yaml`) is **not** affected — the vault authorization uses a separate short-lived token. **API key authentication is not supported** for this flow; you must be logged in with `cre login`.
 
+## Org-owned secrets
+
+Starting with CLI v1.10.0, secrets can optionally be owned by your **organization** instead of your individual workflow owner address. When the `CRE_CLI_SECRETS_ORG_OWNED` environment variable is set to `true` in your target configuration, all secrets operations use your org ID (from your authenticated session) as the owner identifier rather than your workflow owner address.
+
+This is useful for teams that share secrets across multiple workflows within an organization, as it decouples secret ownership from individual wallet addresses.
+
+**How it works:**
+
+- When `CRE_CLI_SECRETS_ORG_OWNED=true`, the CLI uses your org ID as the TDH2 encryption label and vault secret owner
+- When `CRE_CLI_SECRETS_ORG_OWNED=false` (the default), behavior is unchanged — the workflow owner address is used
+
+**Configuration:**
+
+Add `CRE_CLI_SECRETS_ORG_OWNED: true` to your target environment in your `.env.public` or configuration YAML:
+
+```yaml
+CRE_CLI_SECRETS_ORG_OWNED: true
+```
+
+You must be authenticated with `cre login` and your session must include a valid org ID for this to work.
+
 ## Namespaces
 
 Secrets are organized into **namespaces**, which act as logical groupings (e.g., `"main"`, `"staging"`, `"production"`). All secrets are stored in the `"main"` namespace by default. Currently, `create`, `update`, and `delete` commands only support the default namespace. Custom namespace support may be added in future CLI versions.
@@ -8378,7 +8419,7 @@ Secrets are organized into **namespaces**, which act as logical groupings (e.g.,
 
 <Aside type="note" title="Prerequisites">
   - You must be logged in with `cre login` (interactive login required; API keys are not supported for secrets operations)
-  - Your `workflow-owner-address` must be configured in your project
+  - Your `workflow-owner-address` must be configured in your project (not required when `CRE_CLI_SECRETS_ORG_OWNED=true`)
   - **Production CRE:** only **linked workflow owner** vault authorization is supported for these commands. See ([Using Secrets with Deployed Workflows](/cre/guides/workflow/secrets/using-secrets-deployed))
   - For comprehensive guides on using secrets, see [Managing Secrets](/cre/guides/workflow/secrets)
 </Aside>
@@ -8544,7 +8585,7 @@ cre secrets delete secrets-to-delete.yaml --target production-settings
 
 ## cre secrets list
 
-Lists all secret identifiers for your owner address in a specific namespace.
+Lists all secret identifiers for your owner address (or org ID, when `CRE_CLI_SECRETS_ORG_OWNED=true`) in a specific namespace.
 
 ### Usage
 
@@ -8737,7 +8778,9 @@ Remaining repositories:
 
 # Utility Commands
 Source: https://docs.chain.link/cre/reference/cli/utilities
-Last Updated: 2026-03-17
+Last Updated: 2026-04-10
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
 Utility commands provide helpful information and troubleshooting capabilities.
 
@@ -8787,12 +8830,12 @@ cre version
 **Example output:**
 
 ```bash
-CRE CLI version v1.5.0
+CRE CLI version {CRE_CLI_VERSION}
 ```
 
 
 <Aside type="note" title="Version compatibility">
-  Always check that your CLI version matches the version recommended in the documentation. The current recommended version is **v1.5.0**. See the [CLI Installation guide](/cre/getting-started/cli-installation) for more information.
+  Always check that your CLI version matches the version recommended in the documentation. The current recommended version is **{CRE_CLI_VERSION}**. See the [CLI Installation guide](/cre/getting-started/cli-installation) for more information.
 </Aside>
 
 ## Learn more
diff --git a/src/content/cre/reference/cli/index.mdx b/src/content/cre/reference/cli/index.mdx
index 53928dd0fff..4c506088819 100644
--- a/src/content/cre/reference/cli/index.mdx
+++ b/src/content/cre/reference/cli/index.mdx
@@ -6,14 +6,17 @@ isIndex: true
 metadata:
   description: "Explore all CRE CLI commands: complete reference for project setup, workflow deployment, account management, and development tools."
   datePublished: "2025-11-04"
-  lastModified: "2026-03-26"
+  lastModified: "2026-04-10"
 ---
 
 import { Aside } from "@components"
+import { VERSIONS } from "~/config/versions"
 
-<Aside type="note" title="Required CLI Version: v1.5.0">
-  To ensure compatibility with the guides and examples in this documentation, please use version `v1.5.0` of the CRE
-  CLI. You can check your installed version by running `cre version`. Refer to the [CLI
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
+
+<Aside type="note" title={`Required CLI Version: ${CRE_CLI_VERSION}`}>
+  To ensure compatibility with the guides and examples in this documentation, please use version `{CRE_CLI_VERSION}` of
+  the CRE CLI. You can check your installed version by running `cre version`. Refer to the [CLI
   Installation](/cre/getting-started/cli-installation/macos-linux) guide for more information.
 </Aside>
 
diff --git a/src/content/cre/reference/cli/secrets.mdx b/src/content/cre/reference/cli/secrets.mdx
index cd5188cd866..1dc9db42f98 100644
--- a/src/content/cre/reference/cli/secrets.mdx
+++ b/src/content/cre/reference/cli/secrets.mdx
@@ -5,7 +5,7 @@ date: Last Modified
 metadata:
   description: "Manage production secrets with CLI: reference for creating, updating, and deleting secrets in the Vault DON."
   datePublished: "2025-11-04"
-  lastModified: "2026-04-02"
+  lastModified: "2026-04-10"
 ---
 
 import { Aside } from "@components"
@@ -29,6 +29,27 @@ Starting with CLI v1.9.0, secrets operations use a **browser-based OAuth (PKCE)
 
 Your existing CLI login session (`~/.cre/cre.yaml`) is **not** affected — the vault authorization uses a separate short-lived token. **API key authentication is not supported** for this flow; you must be logged in with `cre login`.
 
+## Org-owned secrets
+
+Starting with CLI v1.10.0, secrets can optionally be owned by your **organization** instead of your individual workflow owner address. When the `CRE_CLI_SECRETS_ORG_OWNED` environment variable is set to `true` in your target configuration, all secrets operations use your org ID (from your authenticated session) as the owner identifier rather than your workflow owner address.
+
+This is useful for teams that share secrets across multiple workflows within an organization, as it decouples secret ownership from individual wallet addresses.
+
+**How it works:**
+
+- When `CRE_CLI_SECRETS_ORG_OWNED=true`, the CLI uses your org ID as the TDH2 encryption label and vault secret owner
+- When `CRE_CLI_SECRETS_ORG_OWNED=false` (the default), behavior is unchanged — the workflow owner address is used
+
+**Configuration:**
+
+Add `CRE_CLI_SECRETS_ORG_OWNED: true` to your target environment in your `.env.public` or configuration YAML:
+
+```yaml
+CRE_CLI_SECRETS_ORG_OWNED: true
+```
+
+You must be authenticated with `cre login` and your session must include a valid org ID for this to work.
+
 ## Namespaces
 
 Secrets are organized into **namespaces**, which act as logical groupings (e.g., `"main"`, `"staging"`, `"production"`). All secrets are stored in the `"main"` namespace by default. Currently, `create`, `update`, and `delete` commands only support the default namespace. Custom namespace support may be added in future CLI versions.
@@ -36,7 +57,7 @@ Secrets are organized into **namespaces**, which act as logical groupings (e.g.,
 {/* prettier-ignore */}
 <Aside type="note" title="Prerequisites">
   - You must be logged in with `cre login` (interactive login required; API keys are not supported for secrets operations)
-  - Your `workflow-owner-address` must be configured in your project
+  - Your `workflow-owner-address` must be configured in your project (not required when `CRE_CLI_SECRETS_ORG_OWNED=true`)
   - **Production CRE:** only **linked workflow owner** vault authorization is supported for these commands. See ([Using Secrets with Deployed Workflows](/cre/guides/workflow/secrets/using-secrets-deployed))
   - For comprehensive guides on using secrets, see [Managing Secrets](/cre/guides/workflow/secrets)
 </Aside>
@@ -202,7 +223,7 @@ cre secrets delete secrets-to-delete.yaml --target production-settings
 
 ## cre secrets list
 
-Lists all secret identifiers for your owner address in a specific namespace.
+Lists all secret identifiers for your owner address (or org ID, when `CRE_CLI_SECRETS_ORG_OWNED=true`) in a specific namespace.
 
 ### Usage
 
diff --git a/src/content/cre/reference/cli/utilities.mdx b/src/content/cre/reference/cli/utilities.mdx
index 45b288f92a9..1d9413335ce 100644
--- a/src/content/cre/reference/cli/utilities.mdx
+++ b/src/content/cre/reference/cli/utilities.mdx
@@ -5,10 +5,13 @@ title: "Utility Commands"
 metadata:
   description: "Find CLI utility commands: reference for version checking, binding generation, and helpful development tools."
   datePublished: "2025-11-04"
-  lastModified: "2026-03-17"
+  lastModified: "2026-04-10"
 ---
 
 import { Aside } from "@components"
+import { VERSIONS } from "~/config/versions"
+
+export const CRE_CLI_VERSION = VERSIONS["cre-cli"].LATEST
 
 Utility commands provide helpful information and troubleshooting capabilities.
 
@@ -58,12 +61,12 @@ cre version
 **Example output:**
 
 ```bash
-CRE CLI version v1.5.0
+CRE CLI version {CRE_CLI_VERSION}
 ```
 
 {/* prettier-ignore */}
 <Aside type="note" title="Version compatibility">
-  Always check that your CLI version matches the version recommended in the documentation. The current recommended version is **v1.5.0**. See the [CLI Installation guide](/cre/getting-started/cli-installation) for more information.
+  Always check that your CLI version matches the version recommended in the documentation. The current recommended version is **{CRE_CLI_VERSION}**. See the [CLI Installation guide](/cre/getting-started/cli-installation) for more information.
 </Aside>
 
 ## Learn more
diff --git a/src/content/cre/release-notes.mdx b/src/content/cre/release-notes.mdx
index 2a14a850f6f..d7b648e00bd 100644
--- a/src/content/cre/release-notes.mdx
+++ b/src/content/cre/release-notes.mdx
@@ -5,13 +5,27 @@ date: Last Modified
 metadata:
   description: "Discover what's new in CRE: latest features, changes, and improvements in each release of the Chainlink Runtime Environment."
   datePublished: "2025-11-04"
-  lastModified: "2026-04-02"
+  lastModified: "2026-04-10"
 ---
 
 import { Aside } from "@components"
 
 This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations.
 
+## CLI v1.10.0 - April 10, 2026
+
+**<a href="https://github.com/smartcontractkit/cre-cli/releases/tag/v1.10.0" target="_blank">CRE CLI version 1.10.0</a> is now available.**
+
+- **Optional org ownership for secrets**: Secrets can now optionally be owned by your organization instead of your individual workflow owner address. Set `CRE_CLI_SECRETS_ORG_OWNED: true` in your target configuration to use your org ID as the secret owner across `cre secrets create`, `cre secrets update`, `cre secrets delete`, and `cre secrets list`. This is useful for teams sharing secrets across multiple workflows. When disabled (the default), behavior is unchanged. See [Secrets Management Commands](/cre/reference/cli/secrets#org-owned-secrets) for details.
+- **EVM Bindings generator fix**: Corrected a struct prefix bug in the EVM Bindings generator that could produce incorrect struct names under certain conditions.
+
+**How to update:**
+
+- **Automatic update**: When you run any CRE command, the CLI will automatically detect if a newer version is available and prompt you to update. Simply run `cre update` to install the latest version.
+- **Fresh installation**: If you're installing the CLI for the first time, follow the [CLI Installation guide](/cre/getting-started/cli-installation).
+
+[See all changes on GitHub](https://github.com/smartcontractkit/cre-cli/compare/v1.9.0...v1.10.0)
+
 ## CLI v1.9.0 - April 2, 2026
 
 **<a href="https://github.com/smartcontractkit/cre-cli/releases/tag/v1.9.0" target="_blank">CRE CLI version 1.9.0</a> is now available.**
diff --git a/src/pages/[product]/api-reference/[...id].astro b/src/pages/[product]/api-reference/[...id].astro
index 6badbd894c7..449e0c99f49 100644
--- a/src/pages/[product]/api-reference/[...id].astro
+++ b/src/pages/[product]/api-reference/[...id].astro
@@ -2,7 +2,8 @@
 import { getCollection, render } from "astro:content"
 import type { CollectionEntry } from "astro:content"
 import DocsLayout from "~/layouts/DocsLayout.astro"
-import { VERSIONS, type Collection, type VMVersionConfig } from "@config/versions"
+import { VERSIONS, type VMVersionConfig } from "@config/versions/index.ts"
+import type { Collection } from "~/content.config.ts"
 
 interface RouteParams {
   params: { product: Collection; id: string }