smartcontractkit · dev-dist · Apr 10, 2026 · Apr 10, 2026
@@ -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",

@@ -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) => {

@@ -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 }
@@ -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:**
 

@@ -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