From e83878483acae6438257367ec075c2394fd27242 Mon Sep 17 00:00:00 2001 From: devin distefano Date: Thu, 26 Feb 2026 12:44:22 -0600 Subject: [PATCH 1/7] changelog version bump --- src/components/DownloadButton.tsx | 2 +- .../cre/getting-started/cli-installation/macos-linux.mdx | 6 +++--- .../cre/getting-started/cli-installation/windows.mdx | 6 +++--- src/content/cre/reference/cli/index.mdx | 6 +++--- src/content/cre/reference/cli/utilities.mdx | 2 +- 5 files changed, 11 insertions(+), 11 deletions(-) diff --git a/src/components/DownloadButton.tsx b/src/components/DownloadButton.tsx index 7924e88ef4a..12b0c44f43e 100644 --- a/src/components/DownloadButton.tsx +++ b/src/components/DownloadButton.tsx @@ -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.1.0", "_blank", "noopener,noreferrer") } const handleMouseOver = (e) => { 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 b60b13375bb..0553ce5e04f 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,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-25" --- 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.1.0**. If you see warnings about "unrecognized developer/source" on macOS, run:{" "} diff --git a/src/content/cre/getting-started/cli-installation/windows.mdx b/src/content/cre/getting-started/cli-installation/windows.mdx index 7b31df1fd1a..ea3bfd023d0 100644 --- a/src/content/cre/getting-started/cli-installation/windows.mdx +++ b/src/content/cre/getting-started/cli-installation/windows.mdx @@ -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-25" --- 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.1.0**. - To ensure compatibility with the guides and examples in this documentation, please use version `v1.0.10` of the CRE + diff --git a/src/content/cre/reference/cli/utilities.mdx b/src/content/cre/reference/cli/utilities.mdx index 8d0bd99cea6..245db4a6bb1 100644 --- a/src/content/cre/reference/cli/utilities.mdx +++ b/src/content/cre/reference/cli/utilities.mdx @@ -58,7 +58,7 @@ cre version **Example output:** ```bash -cre version v1.0.11 +CRE CLI version v1.1.0 ``` {/* prettier-ignore */} From 41613a527e309004b89f1ddf388c7cb629bb9f5a Mon Sep 17 00:00:00 2001 From: devin distefano Date: Thu, 26 Feb 2026 16:24:02 -0600 Subject: [PATCH 2/7] bump version references --- src/components/DownloadButton.tsx | 2 +- .../cre/getting-started/cli-installation/macos-linux.mdx | 6 +++--- .../cre/getting-started/cli-installation/windows.mdx | 6 +++--- src/content/cre/reference/cli/index.mdx | 7 ++++--- src/content/cre/reference/cli/utilities.mdx | 2 +- 5 files changed, 12 insertions(+), 11 deletions(-) diff --git a/src/components/DownloadButton.tsx b/src/components/DownloadButton.tsx index 12b0c44f43e..64e8fc1e30c 100644 --- a/src/components/DownloadButton.tsx +++ b/src/components/DownloadButton.tsx @@ -15,7 +15,7 @@ export const DownloadButton = () => { } const handleClick = () => { - window.open("https://github.com/smartcontractkit/cre-cli/releases/tag/v1.1.0", "_blank", "noopener,noreferrer") + window.open("https://github.com/smartcontractkit/cre-cli/releases/tag/v1.2.0", "_blank", "noopener,noreferrer") } const handleMouseOver = (e) => { 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 0553ce5e04f..c401caf523d 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,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-25" + 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.1.0**. +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**. If you see warnings about "unrecognized developer/source" on macOS, run:{" "} diff --git a/src/content/cre/getting-started/cli-installation/windows.mdx b/src/content/cre/getting-started/cli-installation/windows.mdx index ea3bfd023d0..1a4785fb874 100644 --- a/src/content/cre/getting-started/cli-installation/windows.mdx +++ b/src/content/cre/getting-started/cli-installation/windows.mdx @@ -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-25" + 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.1.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 **v1.2.0**. - To ensure compatibility with the guides and examples in this documentation, please use version `v1.1.0` of the CRE + @@ -77,6 +77,7 @@ Manage workflows throughout their entire lifecycle. - **`cre workflow activate`** — Activate a workflow on the Workflow Registry contract - **`cre workflow pause`** — Pause a workflow on the Workflow Registry contract - **`cre workflow delete`** — Delete all versions of a workflow from the Workflow Registry +- **`cre workflow custom-build`** — Convert a workflow to use a custom self-compiled WASM build [View workflow commands →](/cre/reference/cli/workflow) diff --git a/src/content/cre/reference/cli/utilities.mdx b/src/content/cre/reference/cli/utilities.mdx index 245db4a6bb1..6162f5b2bd8 100644 --- a/src/content/cre/reference/cli/utilities.mdx +++ b/src/content/cre/reference/cli/utilities.mdx @@ -58,7 +58,7 @@ cre version **Example output:** ```bash -CRE CLI version v1.1.0 +CRE CLI version v1.2.0 ``` {/* prettier-ignore */} From 342ecce8706cab14a003e709c41466e2ef3cf83d Mon Sep 17 00:00:00 2001 From: devin distefano Date: Thu, 26 Feb 2026 17:38:48 -0600 Subject: [PATCH 3/7] bring your own wasm content + release notes/changelog --- src/config/sidebar.ts | 4 + .../cre/guides/operations/custom-build.mdx | 168 ++++++++++++++++++ .../snippets/custom-build-makefile-default.mk | 4 + .../snippets/custom-build-makefile.mk | 5 + src/content/cre/reference/cli/workflow.mdx | 44 ++++- src/content/cre/release-notes.mdx | 16 +- 6 files changed, 239 insertions(+), 2 deletions(-) create mode 100644 src/content/cre/guides/operations/custom-build.mdx create mode 100644 src/content/cre/guides/operations/snippets/custom-build-makefile-default.mk create mode 100644 src/content/cre/guides/operations/snippets/custom-build-makefile.mk diff --git a/src/config/sidebar.ts b/src/config/sidebar.ts index d0ae37ca3dd..e1301618975 100644 --- a/src/config/sidebar.ts +++ b/src/config/sidebar.ts @@ -374,6 +374,10 @@ export const SIDEBAR: Partial> = { title: "Monitoring & Debugging Workflows", url: "cre/guides/operations/monitoring-workflows", }, + { + title: "Custom WASM Builds", + url: "cre/guides/operations/custom-build", + }, ], }, { diff --git a/src/content/cre/guides/operations/custom-build.mdx b/src/content/cre/guides/operations/custom-build.mdx new file mode 100644 index 00000000000..11dbc0c0b73 --- /dev/null +++ b/src/content/cre/guides/operations/custom-build.mdx @@ -0,0 +1,168 @@ +--- +section: cre +date: Last Modified +title: "Custom WASM Builds" +metadata: + description: "Learn how to take ownership of the WASM build step in CRE workflows using cre workflow custom-build and a custom Makefile." + datePublished: "2026-02-26" + lastModified: "2026-02-26" +--- + +import { Aside } from "@components" +import { CodeHighlightBlock } from "@components" +import customBuildMakefileDefault from "./snippets/custom-build-makefile-default.mk?raw" +import customBuildMakefile from "./snippets/custom-build-makefile.mk?raw" + +By default, `cre workflow deploy` and `cre workflow simulate` compile your Go or TypeScript source to a WASM binary automatically — no build configuration required. This works for most workflows. + +`cre workflow custom-build` is an opt-in feature for advanced users who need to own the build step. Once converted, the CLI delegates compilation to a `Makefile` in your workflow directory instead of compiling your source itself. + +## When to use custom WASM builds + +{/* prettier-ignore */} + + +Generally, you should consider using custom WASM builds only when you have a specific reason to take control of the compilation step. Custom workflows are particularly useful for teams that need to use a custom compiler version or toolchain that differs from the CRE default compiler. + +Common reasons to use custom WASM builds: + +- **Custom compiler flags or build tags**: Add optimization flags, conditional compilation tags, or other build-time settings not exposed by the CLI's built-in compiler +- **CI/CD pipelines**: Build the WASM artifact once in your pipeline and promote it across environments without recompiling +- **Pre-build validation**: Add linting, type checking, formatting, or security scanning steps before compilation +- **Non-standard toolchains**: Use a custom compiler version or toolchain that differs from the CLI default +- **Language and SDK extensions**: Integrate code from other languages or custom SDKs into your build pipeline + +## Convert a workflow to custom build + +Run the following command from your project root: + +```bash +cre workflow custom-build ./my-workflow +``` + +You will be prompted to confirm before any changes are made. To skip the prompt, use `--force`. + +{/* prettier-ignore */} + + +The following changes are made to your workflow: + +- Updates `workflow-path` to `./wasm/workflow.wasm` in your `workflow.yaml` for all targets +- Creates a `Makefile` in your workflow directory with a `build` target +- Creates a `wasm/` output directory + +## Build and simulate + +After conversion, install dependencies (TypeScript only), then build and simulate: + +```bash +# TypeScript only +bun install + +make build +cre workflow simulate ./my-workflow --target staging-settings +``` + +The CLI picks up the compiled binary at `wasm/workflow.wasm` automatically. + +## Try it yourself + +Walk through the full custom build flow end to end using a hello-world project. + +**1. Convert your workflow to a custom build:** Run the following command from your project root: + +```bash +cre workflow custom-build ./my-workflow +``` + +**2. Open the generated `Makefile`:** In the `my-workflow` directory, you'll see a new `Makefile` with a `build` target. + + + +Install dependencies and run the initial build: + +```bash +# TypeScript only +bun install + +make build +cre workflow simulate ./my-workflow --target staging-settings +``` + +For a hello-world workflow you'll see output like `"Hello world!"`. + +**3. Add a custom step to your `Makefile`** (highlighted line shows what to add): + + + +**4. Rebuild and simulate again:** Run the following commands from your project root: + +```bash +make build +cre workflow simulate ./my-workflow --target staging-settings +``` + +When `make build` runs you'll see `Running my custom build step...` printed before compilation. + +Swap the `echo` for any real step: type checking, linting, code generation, or a custom compiler invocation. + +## Generated Makefile + +The generated `Makefile` is ready to use. The only requirement is that `make build` produces `wasm/workflow.wasm`. + +**Go:** + +```makefile +.PHONY: build + +build: + GOOS=wasip1 GOARCH=wasm CGO_ENABLED=0 go build -o wasm/workflow.wasm -trimpath -ldflags="-buildid= -w -s" . +``` + +**TypeScript:** + +```makefile +.PHONY: build + +build: + bun cre-compile main.ts wasm/workflow.wasm +``` + +## Customizing the Makefile + +Edit the generated `Makefile` to add any steps your build requires. + +**Example: Go with build tags:** + +```makefile +.PHONY: build + +build: + GOOS=wasip1 GOARCH=wasm CGO_ENABLED=0 go build -tags mytag -o wasm/workflow.wasm -trimpath -ldflags="-buildid= -w -s" . +``` + +**Example: TypeScript with type checking, linting, and formatting:** + +```makefile +.PHONY: build format lint typecheck + +format: + bun run format +lint: format + bun run lint +typecheck: lint + bun run typecheck + +build: typecheck + bun cre-compile main.ts wasm/workflow.wasm +``` + +## Learn more + +- [`cre workflow custom-build` reference](/cre/reference/cli/workflow#cre-workflow-custom-build): Command flags and usage +- [Simulating Workflows](/cre/guides/operations/simulating-workflows): Testing your workflow locally +- [Deploying Workflows](/cre/guides/operations/deploying-workflows): Deploying to the Workflow Registry diff --git a/src/content/cre/guides/operations/snippets/custom-build-makefile-default.mk b/src/content/cre/guides/operations/snippets/custom-build-makefile-default.mk new file mode 100644 index 00000000000..b3f1f10be55 --- /dev/null +++ b/src/content/cre/guides/operations/snippets/custom-build-makefile-default.mk @@ -0,0 +1,4 @@ +.PHONY: build + +build: + bun cre-compile main.ts wasm/workflow.wasm diff --git a/src/content/cre/guides/operations/snippets/custom-build-makefile.mk b/src/content/cre/guides/operations/snippets/custom-build-makefile.mk new file mode 100644 index 00000000000..2b1fe155142 --- /dev/null +++ b/src/content/cre/guides/operations/snippets/custom-build-makefile.mk @@ -0,0 +1,5 @@ +.PHONY: build + +build: + echo "Running my custom build step..." # highlight-line + bun cre-compile main.ts wasm/workflow.wasm diff --git a/src/content/cre/reference/cli/workflow.mdx b/src/content/cre/reference/cli/workflow.mdx index 94fa9ce86ab..249d8be1212 100644 --- a/src/content/cre/reference/cli/workflow.mdx +++ b/src/content/cre/reference/cli/workflow.mdx @@ -5,7 +5,7 @@ title: "Workflow Commands" metadata: description: "Manage workflows with CLI: complete command reference for simulating, deploying, activating, pausing, and deleting workflows." datePublished: "2025-11-04" - lastModified: "2025-11-04" + lastModified: "2026-02-26" --- import { Aside } from "@components" @@ -244,6 +244,48 @@ cre workflow delete ./my-workflow --target production-settings For more details, see [Deleting Workflows](/cre/guides/operations/deleting-workflows). +## `cre workflow custom-build` + +{/* prettier-ignore */} + + +Converts a workflow to use a custom self-compiled WASM build. Instead of the CLI compiling your source automatically, a generated `Makefile` owns the build step. Use this when you need custom compiler flags, CI/CD artifact promotion, pre-build validation, or non-standard toolchains. + +**Usage:** + +```bash +cre workflow custom-build [flags] +``` + +**Arguments:** + +- `` — (Required) Path to the workflow folder (e.g., `./my-workflow`) + +**Flags:** + +|
Flag
| Description | +| ------------------------------------------ | ------------------------------------------------ | +| `-f, --force` | Skip confirmation prompt and convert immediately | + +**Example:** + +```bash +cre workflow custom-build ./my-workflow +``` + +**Expected output:** + +```bash +✓ Workflow converted to custom build. workflow-path is now ./wasm/workflow.wasm + The Makefile is configured to output the WASM to this path. Run: make build +``` + +For a full guide including Makefile examples and customization, see [Custom WASM Builds](/cre/guides/operations/custom-build). + +--- + ## Workflow lifecycle The typical workflow lifecycle uses these commands in sequence: diff --git a/src/content/cre/release-notes.mdx b/src/content/cre/release-notes.mdx index f3eb188177a..50986cd95eb 100644 --- a/src/content/cre/release-notes.mdx +++ b/src/content/cre/release-notes.mdx @@ -5,7 +5,7 @@ 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-02-16" + lastModified: "2026-02-26" --- import { Aside } from "@components" @@ -16,6 +16,20 @@ This page provides detailed release notes for CRE. It includes information on ne CRE now supports the [Confidential HTTP](/cre/capabilities/confidential-http) capability for production workflows, allowing you to make privacy-preserving API calls with enclave execution. See the [Making Confidential Requests](/cre/guides/workflow/using-confidential-http-client/making-requests-ts) guide to learn more. +## CLI v1.1.0 - February 19th, 2026 + +**CRE CLI version 1.1.0 is now available.** + +- **Custom WASM builds**: New `cre workflow custom-build` command converts a workflow to use a custom Makefile-based build process. Use this when you need custom compiler flags, build tags, CI/CD artifact promotion, or non-standard toolchains. See the [Custom WASM Builds](/cre/guides/operations/custom-build) guide for details. +- **Improved CLI interface**: The CLI has a refreshed visual output across all commands — styled errors, progress indicators, and spinners during long-running operations make it easier to follow what's happening. + +**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.0.11...v1.1.0) + ## CLI v1.0.11 - February 13, 2026 **CRE CLI version 1.0.11 is now available.** From 569f03f30bded6126aab3d3b7aa9ea0f72e4367d Mon Sep 17 00:00:00 2001 From: devin distefano Date: Thu, 26 Feb 2026 17:55:29 -0600 Subject: [PATCH 4/7] changelog update --- public/changelog.json | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/public/changelog.json b/public/changelog.json index 37600585eb6..8eab331b566 100644 --- a/public/changelog.json +++ b/public/changelog.json @@ -488,6 +488,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", From 59d36f7286b00624f87170da6334e753ea08459e Mon Sep 17 00:00:00 2001 From: devin distefano Date: Thu, 26 Feb 2026 17:57:57 -0600 Subject: [PATCH 5/7] deploy access cli --- src/config/sidebar.ts | 4 + src/content/cre/account/deploy-access.mdx | 87 +++++++++++++++++++ src/content/cre/account/index.mdx | 1 + src/content/cre/account/managing-auth.mdx | 3 + .../getting-started/before-you-build-go.mdx | 2 +- .../getting-started/before-you-build-ts.mdx | 2 +- .../guides/operations/deploying-workflows.mdx | 9 +- src/content/cre/index.mdx | 2 +- src/content/cre/reference/cli/account.mdx | 47 +++++++++- .../cre/reference/cli/authentication.mdx | 4 +- src/content/cre/reference/cli/workflow.mdx | 7 +- 11 files changed, 155 insertions(+), 13 deletions(-) create mode 100644 src/content/cre/account/deploy-access.mdx diff --git a/src/config/sidebar.ts b/src/config/sidebar.ts index e1301618975..cfe554c17da 100644 --- a/src/config/sidebar.ts +++ b/src/config/sidebar.ts @@ -399,6 +399,10 @@ export const SIDEBAR: Partial> = { title: "Managing Authentication", url: "cre/account/managing-auth", }, + { + title: "Requesting Deploy Access", + url: "cre/account/deploy-access", + }, ], }, { diff --git a/src/content/cre/account/deploy-access.mdx b/src/content/cre/account/deploy-access.mdx new file mode 100644 index 00000000000..faa151500ed --- /dev/null +++ b/src/content/cre/account/deploy-access.mdx @@ -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 cre.chain.link/request-access 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 */} + + +## 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 diff --git a/src/content/cre/account/index.mdx b/src/content/cre/account/index.mdx index 53a47993344..0b7530a492c 100644 --- a/src/content/cre/account/index.mdx +++ b/src/content/cre/account/index.mdx @@ -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 diff --git a/src/content/cre/account/managing-auth.mdx b/src/content/cre/account/managing-auth.mdx index b0f6eac7b15..79bd13aafe6 100644 --- a/src/content/cre/account/managing-auth.mdx +++ b/src/content/cre/account/managing-auth.mdx @@ -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: diff --git a/src/content/cre/getting-started/before-you-build-go.mdx b/src/content/cre/getting-started/before-you-build-go.mdx index 861d35457d9..d1aa8b0e96c 100644 --- a/src/content/cre/getting-started/before-you-build-go.mdx +++ b/src/content/cre/getting-started/before-you-build-go.mdx @@ -53,7 +53,7 @@ Here are resources to help you go from simulation to production. {/* prettier-ignore */} 1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Connect your wallet to your organization diff --git a/src/content/cre/getting-started/before-you-build-ts.mdx b/src/content/cre/getting-started/before-you-build-ts.mdx index e00d7583c2a..9a055ca1a6b 100644 --- a/src/content/cre/getting-started/before-you-build-ts.mdx +++ b/src/content/cre/getting-started/before-you-build-ts.mdx @@ -119,7 +119,7 @@ Here are resources to help you go from simulation to production. {/* prettier-ignore */} 1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Connect your wallet to your organization diff --git a/src/content/cre/guides/operations/deploying-workflows.mdx b/src/content/cre/guides/operations/deploying-workflows.mdx index 710a4fb2ead..a00ee37fa46 100644 --- a/src/content/cre/guides/operations/deploying-workflows.mdx +++ b/src/content/cre/guides/operations/deploying-workflows.mdx @@ -12,9 +12,10 @@ import { Aside } from "@components" {/* prettier-ignore */} When you deploy a workflow, you take your locally tested code and register it with the onchain Workflow Registry contract. This makes your workflow "live" so it can activate and respond to triggers across a [Decentralized Oracle Network (DON)](/cre/key-terms#decentralized-oracle-network-don). @@ -23,7 +24,7 @@ When you deploy a workflow, you take your locally tested code and register it wi Before you can deploy a workflow, you must have: -- **Early Access approval**: Workflow deployment is currently in Early Access. Request access here if you haven't already. +- **Early Access approval**: Workflow deployment is currently in Early Access. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). - **[Authenticated](/cre/reference/cli/authentication)**: Logged in via `cre login` or using an [API key](/cre/reference/cli/authentication#api-key-authentication) (`CRE_API_KEY`). To verify, run `cre whoami`. - **[Linked your key](/cre/reference/cli/account#cre-account-link-key)**: Linked your EOA or multi-sig wallet to your account by running `cre account link-key`. - **A funded wallet**: The account you are deploying from must be funded with ETH on Ethereum Mainnet to pay the gas fees for the onchain registration transaction to the Workflow Registry contract. diff --git a/src/content/cre/index.mdx b/src/content/cre/index.mdx index 69165c62c54..bc9d3501cae 100644 --- a/src/content/cre/index.mdx +++ b/src/content/cre/index.mdx @@ -49,7 +49,7 @@ Early Access to workflow deployment includes: - **Workflow lifecycle management**: Deploy, activate, pause, update, and delete workflows through the CLI - **Monitoring and debugging**: Access detailed logs, events, and performance metrics in the CRE UI -To request Early Access, please share details about your project and use case—this helps us provide better support as you build with CRE. +To request Early Access, run `cre account access` from the CLI or visit cre.chain.link/request-access. See [Requesting Deploy Access](/cre/account/deploy-access) for details. ## How CRE runs your workflows diff --git a/src/content/cre/reference/cli/account.mdx b/src/content/cre/reference/cli/account.mdx index cc810b66e6f..7a78a044449 100644 --- a/src/content/cre/reference/cli/account.mdx +++ b/src/content/cre/reference/cli/account.mdx @@ -5,7 +5,7 @@ title: "Account Management" metadata: description: "Manage wallet addresses with CLI: link, unlink, and list keys for deploying workflows to the Workflow Registry." datePublished: "2025-11-04" - lastModified: "2025-11-04" + lastModified: "2026-02-26" --- import { Aside } from "@components" @@ -17,6 +17,51 @@ The `cre account` commands manage your linked public key addresses for workflow All `cre` commands support [global flags](/cre/reference/cli#global-flags) like `--env`, `--target`, `--project-root`, and `--verbose`. +## `cre account access` + + + +Checks your organization's deployment access status and lets you submit a request for Early Access directly from the CLI. + +For a full walkthrough including the interactive flow and web UI option, see [Requesting Deploy Access](/cre/account/deploy-access). + +**Usage:** + +```bash +cre account access +``` + +**Interactive flow:** + +When you run this command, the CLI will: + +1. Check whether your organization has deployment access enabled +1. If not, prompt you to submit a request +1. Ask you to briefly describe your use case +1. Confirm the request was submitted — the Chainlink team will follow up via email + +**Example output (access not yet enabled):** + +``` +! Deployment access is not yet enabled for your organization. + + Request deployment access? Yes + + Briefly describe your use case + What are you building with CRE? + > I'm working on a prediction market and I need to deploy my workflow! (or whatever you're building) + +✓ Access request submitted successfully! + +Our team will review your request and get back to you via email shortly. +``` + +--- + ## `cre account link-key`