smartcontractkit · dev-dist · Feb 26, 2026 · Feb 26, 2026 · Feb 26, 2026 · Feb 26, 2026
@@ -389,6 +389,13 @@
       "title": "Deprecating Data Feeds",
       "topic": "Data Feeds"
     },
+    {
+      "category": "release",
+      "date": "2026-02-26",
+      "description": "CRE CLI version 1.2.0 is now available. This release adds dynamic template fetching, new `cre templates` commands for managing template sources, and a new `cre account access` command for checking and requesting deployment access.\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.1.0...v1.2.0)",
+      "title": "CRE CLI v1.2.0 — Dynamic Templates and Deploy Access Management",
+      "topic": "CRE"
+    },
     {
       "category": "release",
       "date": "2026-02-25",
@@ -495,6 +502,13 @@
       "title": "Cross-chain token (CCT) standard: Added support for new tokens",
       "topic": "CCIP"
     },
+    {
+      "category": "release",
+      "date": "2026-02-19",
+      "description": "CRE CLI version 1.1.0 is now available. This release adds support for custom WASM builds and an improved CLI interface.\n\n**Required versions:** CLI v1.1.0+, Go SDK v1.2.0+, TS SDK v1.0.9+\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.0.11...v1.1.0)",
+      "title": "CRE CLI v1.1.0 — Custom WASM Builds and Improved CLI Interface",
+      "topic": "CRE"
+    },
     {
       "category": "integration",
       "date": "2026-02-15",

@@ -15,7 +15,7 @@ export const DownloadButton = () => {
   }
 
   const handleClick = () => {
-    window.open("https://github.com/smartcontractkit/cre-cli/releases/tag/v1.0.11", "_blank", "noopener,noreferrer")
+    window.open("https://github.com/smartcontractkit/cre-cli/releases/tag/v1.2.0", "_blank", "noopener,noreferrer")
   }
 
   const handleMouseOver = (e) => {

@@ -374,6 +374,10 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Monitoring & Debugging Workflows",
           url: "cre/guides/operations/monitoring-workflows",
         },
+        {
+          title: "Custom WASM Builds",
+          url: "cre/guides/operations/custom-build",
+        },
       ],
     },
     {
@@ -395,6 +399,10 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
               title: "Managing Authentication",
               url: "cre/account/managing-auth",
             },
+            {
+              title: "Requesting Deploy Access",
+              url: "cre/account/deploy-access",
+            },
           ],
         },
         {
@@ -498,6 +506,7 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
             { title: "Account Management", url: "cre/reference/cli/account" },
             { title: "Workflow Commands", url: "cre/reference/cli/workflow" },
             { title: "Secrets Management", url: "cre/reference/cli/secrets" },
+            { title: "Template Sources", url: "cre/reference/cli/templates" },
             { title: "Utilities", url: "cre/reference/cli/utilities" },
           ],
         },

@@ -0,0 +1,87 @@
+---
+section: cre
+date: Last Modified
+title: "Requesting Deploy Access"
+metadata:
+  description: "Learn how to check your deployment access status and request Early Access to deploy CRE workflows using the CLI or web UI."
+  datePublished: "2026-02-26"
+  lastModified: "2026-02-26"
+---
+
+import { Aside } from "@components"
+
+Deploying workflows to a Chainlink DON requires Early Access approval. You can request access in two ways:
+
+- **From the CLI** — Run `cre account access` to check your status or submit a request directly from your terminal
+- **From the web** — Visit <a href="https://cre.chain.link/request-access" target="_blank" rel="noopener noreferrer">cre.chain.link/request-access</a> to fill out the request form
+
+## Check your access status
+
+Run the following command to see your current deployment access status:
+
+```bash
+cre account access
+```
+
+Your access status is also shown when you run `cre whoami`:
+
+```bash
+cre whoami
+```
+
+```
+Account details retrieved:
+
+Email:           email@domain.com
+Organization ID: org_mEMRknbVURM9DWsB
+Deploy Access:   Not enabled (run 'cre account access' to request)
+```
+
+## Request deploy access
+
+If your organization does not have deploy access, `cre account access` will prompt you to submit a request:
+
+```
+! Deployment access is not yet enabled for your organization.
+
+  Request deployment access? Yes
+```
+
+After confirming, you'll be asked to briefly describe what you're building:
+
+```
+  Briefly describe your use case
+  What are you building with CRE?
+```
+
+Once submitted, you'll see:
+
+```
+✓ Access request submitted successfully!
+
+Our team will review your request and get back to you via email shortly.
+```
+
+You'll receive a confirmation email, and the Chainlink team will follow up once your request has been reviewed.
+
+{/* prettier-ignore */}
+<Aside type="note" title="You can keep building while you wait">
+  Deploy access is only required for `cre workflow deploy`. You can continue developing and simulating workflows locally with `cre workflow simulate` while your request is under review.
+</Aside>
+
+## What happens after approval
+
+Once your organization is granted deploy access, `cre whoami` will show:
+
+```
+Deploy Access:   Enabled
+```
+
+You can then use `cre workflow deploy` to deploy workflows to the Workflow Registry. See [Deploying Workflows](/cre/guides/operations/deploying-workflows) for next steps.
+
+## Prompted automatically
+
+You don't need to run `cre account access` proactively. The CLI will prompt you to request access automatically in two situations:
+
+- When you run `cre workflow deploy` without access
+- After a successful `cre workflow simulate`, as a reminder that deployment is available once access is granted
@@ -28,6 +28,7 @@ To use CRE, you need:
 - **[Creating Your Account](/cre/account/creating-account)** - Step-by-step guide to creating a new CRE account through the CRE UI
 - **[Logging in with the CLI](/cre/account/cli-login)** - Authenticate your CLI with your CRE account to run commands
 - **[Managing Authentication](/cre/account/managing-auth)** - Check your login status, handle session expiration, and log out
+- **[Requesting Deploy Access](/cre/account/deploy-access)** - Check your deployment access status or submit a request for Early Access
 
 ## Security features
 

@@ -61,10 +61,13 @@ Account details retrieved:
 
 Email:           email@domain.com
 Organization ID: org_mEMRknbVURM9DWsB
+Deploy Access:   Not enabled (run 'cre account access' to request)
 ```
 
 If you're not logged in, you'll receive an error message prompting you to run `cre login`.
 
+To check your deploy access status or submit a request, see [Requesting Deploy Access](/cre/account/deploy-access).
+
 ## Logging out
 
 To explicitly end your CLI session and remove your stored credentials, use the `cre logout` command:

@@ -53,7 +53,7 @@ Here are resources to help you go from simulation to production.
 
 {/* prettier-ignore */}
 <Aside type="note" title="Deployment access required">
-  Deploying requires Early Access approval. <a href="https://cre.chain.link/request-access" target="_blank" rel="noopener noreferrer">Request access here</a>. While you wait, continue building and simulating workflows.
+  Deploying requires Early Access approval. Run `cre account access` or visit <a href="https://cre.chain.link/request-access" target="_blank">cre.chain.link/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
 </Aside>
 
 1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Connect your wallet to your organization

@@ -119,7 +119,7 @@ Here are resources to help you go from simulation to production.
 
 {/* prettier-ignore */}
 <Aside type="note" title="Deployment access required">
-  Deploying requires Early Access approval. <a href="https://cre.chain.link/request-access" target="_blank" rel="noopener noreferrer">Request access here</a>. While you wait, continue building and simulating workflows.
+  Deploying requires Early Access approval. Run `cre account access` or visit <a href="https://cre.chain.link/request-access" target="_blank">cre.chain.link/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
 </Aside>
 
 1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Connect your wallet to your organization

@@ -5,13 +5,13 @@ 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-02-16"
+  lastModified: "2026-02-26"
 ---
 
 import { Aside, CopyText, PageTabs } from "@components"
 import { DownloadButton } from "~/components/DownloadButton.tsx"
 
-This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is **v1.0.11**.
+This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is **v1.2.0**.
 
 <PageTabs
   pages={[
@@ -66,7 +66,7 @@ After the script completes, verify the installation:
 cre version
 ```
 
-**Expected output:** `cre version v1.0.11`
+**Expected output:** `CRE CLI version v1.2.0`
 
 <Aside type="note" title="macOS Gatekeeper">
   If you see warnings about "unrecognized developer/source" on macOS, run:{" "}

@@ -5,13 +5,13 @@ 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-02-16"
+  lastModified: "2026-02-26"
 ---
 
 import { Aside, CopyText, PageTabs } from "@components"
 import { DownloadButton } from "~/components/DownloadButton.tsx"
 
-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.0.11**.
+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.2.0**.
 
 <PageTabs
   pages={[
@@ -65,7 +65,7 @@ After the script completes, **open a new PowerShell window** and verify the inst
 cre version
 ```
 
-**Expected output:** `cre version v1.0.11`
+**Expected output:** `CRE CLI version v1.2.0`
 
 ### Manual installation