smartcontractkit · dev-dist · Mar 17, 2026 · Mar 17, 2026 · Mar 17, 2026
@@ -398,6 +398,63 @@
     }
   },
   "data": [
+    {
+      "category": "release",
+      "date": "2026-03-17",
+      "description": "CRE CLI version 1.5.0 is now available. This release adds support for 9 new mainnets (Celo, Gnosis Chain, Ink, Linea, Mantle, MegaETH, Plasma, Scroll, and Sonic) and 8 new testnets (Cronos, Mantle Sepolia, MegaETH Testnet 2, Scroll Sepolia, Sonic Testnet, TAC Testnet, Unichain Sepolia, and XLayer Testnet), introduces the `cre hash` command to display content hashes for workflow artifacts, adds `${VAR}` environment variable resolution in RPC URLs, JSON ABI support in `cre generate-bindings`, and `.env` file support across all commands.\n\n**Required versions for new networks:** CLI v1.5.0+, Go SDK v1.6.0+, TS SDK v1.3.0+\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.4.0...v1.5.0)",
+      "title": "CRE CLI v1.5.0 — New Networks, Hash Command, and Developer Tools",
+      "topic": "CRE"
+    },
+    {
+      "category": "integration",
+      "date": "2026-03-17",
+      "description": "CRE now supports 9 new mainnets and 8 new testnets for workflow simulation and production deployment.\n\nNew mainnets: Celo, Gnosis Chain, Ink, Linea, Mantle, MegaETH, Plasma, Scroll, and Sonic.\n\nNew testnets: Cronos, Mantle Sepolia, MegaETH Testnet 2, Scroll Sepolia, Sonic Testnet, TAC Testnet, Unichain Sepolia, and XLayer Testnet.\n\n**Required versions:** CLI v1.5.0+, Go SDK v1.6.0+, TS SDK v1.3.0+\n\nSee the [Supported Networks](https://docs.chain.link/cre/supported-networks) page for chain names and version requirements.",
+      "relatedNetworks": [
+        "celo",
+        "gnosis-chain",
+        "ink",
+        "linea",
+        "mantle",
+        "megaeth",
+        "plasma",
+        "scroll",
+        "sonic",
+        "cronos",
+        "tac",
+        "unichain",
+        "xlayer"
+      ],
+      "title": "CRE Expands to New Mainnets and Testnets",
+      "topic": "CRE"
+    },
+    {
+      "category": "release",
+      "date": "2026-03-16",
+      "description": "Go SDK version 1.6.0 updates EVM capabilities to support the new networks added in CLI v1.5.0.\n\n[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-go/compare/v1.5.0...v1.6.0)",
+      "title": "CRE Go SDK v1.6.0 — New Network Support",
+      "topic": "CRE"
+    },
+    {
+      "category": "release",
+      "date": "2026-03-16",
+      "description": "TypeScript SDK version 1.3.0 updates EVM capabilities to support the new networks added in CLI v1.5.0.\n\n[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-typescript/compare/v1.2.0...v1.3.0)",
+      "title": "CRE TS SDK v1.3.0 — New Network Support",
+      "topic": "CRE"
+    },
+    {
+      "category": "release",
+      "date": "2026-03-12",
+      "description": "CRE CLI version 1.4.0 is now available. This release enables `cre workflow build`, `cre workflow upload`, and `cre workflow deploy` to run as independent steps for better CI/CD pipeline integration. The HTTP capability now supports sending multiple headers per request.\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.3.0...v1.4.0)",
+      "title": "CRE CLI v1.4.0 — CI/CD Pipeline Support and MultiHeaders",
+      "topic": "CRE"
+    },
+    {
+      "category": "release",
+      "date": "2026-03-12",
+      "description": "TypeScript SDK version 1.2.0 adds a `logTriggerConfig` helper for configuring EVM log triggers in workflows and improves error messages with field-level context in `encodeCallMsg`.\n\n[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-typescript/compare/v1.1.0...v1.2.0)",
+      "title": "CRE TS SDK v1.2.0 — logTriggerConfig Helper and Improved Errors",
+      "topic": "CRE"
+    },
     {
       "category": "integration",
       "date": "2026-03-15",

@@ -5,7 +5,7 @@ date: Last Modified
 metadata:
   description: "CRE HTTP capability: fetch offchain data with consensus validation for secure results in your workflows."
   datePublished: "2025-11-04"
-  lastModified: "2025-11-04"
+  lastModified: "2026-03-17"
 ---
 
 import { Aside } from "@components"
@@ -27,6 +27,10 @@ This provides cryptographically verified, tamper-proof execution for your offcha
 
 </Aside>
 
+## Features
+
+- **Multiple headers per request**: Use the `MultiHeaders` field to send multiple headers in a single HTTP request. This is useful for APIs that require multiple authentication or content negotiation headers simultaneously.
+
 ## Learn more
 
 - **[API Interactions Guide](/cre/guides/workflow/using-http-client)**: Learn how to use the SDK to invoke the HTTP capability.

@@ -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-26"
+  lastModified: "2026-03-17"
 ---
 
 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.2.0**.
+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**.
 
 <PageTabs
   pages={[
@@ -66,7 +66,7 @@ After the script completes, verify the installation:
 cre version
 ```
 
-**Expected output:** `CRE CLI version v1.2.0`
+**Expected output:** `CRE CLI version v1.5.0`
 
 <Aside type="note" title="macOS Gatekeeper">
   If you see warnings about "unrecognized developer/source" on macOS, run:{" "}
@@ -120,11 +120,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.0.11)
+1. Find the release version you downloaded (e.g., v1.5.0)
 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.0.11, you'll see something like:
+**Example:** For `cre_darwin_arm64.zip` in release v1.5.0, you'll see something like:
 
 ```
 cre_darwin_arm64.zip
@@ -154,7 +154,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.0.11_darwin_arm64 cre
+   mv cre_v1.5.0_darwin_arm64 cre
    ```
 
 1. **Make it executable**:
@@ -227,7 +227,7 @@ cre version
 
 **Expected output:**
 
-You should see version information: `cre version v1.0.11`.
+You should see version information: `cre version v1.5.0`.
 
 **If it doesn't work:**
 

@@ -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-26"
+  lastModified: "2026-03-17"
 ---
 
 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.2.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.5.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 CLI version v1.2.0`
+**Expected output:** `CRE CLI version v1.5.0`
 
 ### Manual installation
 
@@ -96,11 +96,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.0.11)
+2. Find the release version you downloaded (e.g., v1.5.0)
 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.0.11, you'll see something like:
+**Example:** For `cre_windows_amd64.zip` in release v1.5.0, you'll see something like:
 
 ```
 cre_windows_amd64.zip
@@ -114,7 +114,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.0.11_windows_amd64.exe` to `cre.exe`.
+1. Inside the extracted folder, rename the file `cre_v1.5.0_windows_amd64.exe` to `cre.exe`.
 
 #### 3. Add the CLI to your PATH
 
@@ -139,7 +139,7 @@ Open a new **PowerShell** or **Command Prompt** window and run:
 cre version
 ```
 
-You should see version information: `cre version v1.0.11`.
+You should see version information: `cre version v1.5.0`.
 
 ## Next steps
 

@@ -5,7 +5,7 @@ title: "Deploying Workflows"
 metadata:
   description: "Deploy your workflow: learn how to register your workflow and start running it across a Decentralized Oracle Network (DON)."
   datePublished: "2025-11-04"
-  lastModified: "2026-02-12"
+  lastModified: "2026-03-17"
 ---
 
 import { Aside } from "@components"
@@ -70,6 +70,9 @@ cre workflow deploy my-workflow --target production-settings
 | ---------------- | --------------------------------------------------------------------------------------- |
 | `--target`       | Sets the target environment from your configuration files (e.g., `production-settings`) |
 | `--output`       | The output file for the compiled WASM binary (default: `"./binary.wasm.br.b64"`)        |
+| `--wasm`         | Path to a pre-built WASM binary (skips compilation). Useful in CI/CD pipelines          |
+| `--config`       | Override the config file path from `workflow.yaml`                                      |
+| `--no-config`    | Deploy without a config file                                                            |
 | `--unsigned`     | Return the raw transaction instead of broadcasting it to the network                    |
 | `--yes`          | Skip confirmation prompts and proceed with the operation                                |
 | `--project-root` | Path to the project root directory                                                      |
@@ -146,6 +149,86 @@ After a successful deployment, you can verify that your workflow was registered
 
 1. **Block Explorer**: Check the Workflow Registry contract on a block explorer. The CLI output will provide the transaction hash for the registration. The `WorkflowRegistry` contract is deployed on **Ethereum Mainnet** at the address <a href="https://etherscan.io/address/0x4ac54353fa4fa961afcc5ec4b118596d3305e7e5#code" target="_blank" rel="noopener noreferrer">`0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5`</a>.
 
+## CI/CD pipeline integration
+
+The `cre workflow build` and `cre workflow deploy` commands can be run as independent steps, making it straightforward to integrate CRE deployments into CI/CD pipelines.
+
+The separation gives you two key benefits:
+
+- **Build once, deploy many times** — Compile your workflow to a WASM binary in a build step, then promote that exact binary to staging and production without recompiling. This ensures the artifact you tested is the artifact you deploy.
+- **Verify before deploying** — Use `cre workflow hash` after building to record and verify content hashes before submitting a deployment transaction.
+
+### Example: GitHub Actions
+
+The following example shows a two-job pipeline: a `build` job that compiles and uploads the WASM artifact, and a `deploy` job that downloads and deploys that exact binary.
+
+```yaml
+# .github/workflows/deploy.yml
+name: Deploy Workflow
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install CRE CLI
+        run: curl -sSL https://github.com/smartcontractkit/cre-cli/releases/latest/download/install.sh | sh
+
+      - name: Build workflow
+        run: cre workflow build ./my-workflow --output ./my-workflow/binary.wasm
+        env:
+          CRE_API_KEY: ${{ secrets.CRE_API_KEY }}
+
+      - name: Display content hashes
+        run: cre workflow hash ./my-workflow --wasm ./my-workflow/binary.wasm --target production-settings
+        env:
+          CRE_API_KEY: ${{ secrets.CRE_API_KEY }}
+          CRE_ETH_PRIVATE_KEY: ${{ secrets.CRE_ETH_PRIVATE_KEY }}
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: workflow-binary
+          path: ./my-workflow/binary.wasm
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install CRE CLI
+        run: curl -sSL https://github.com/smartcontractkit/cre-cli/releases/latest/download/install.sh | sh
+
+      - name: Download artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: workflow-binary
+          path: ./my-workflow
+
+      - name: Deploy workflow
+        run: cre workflow deploy ./my-workflow --wasm ./my-workflow/binary.wasm --target production-settings --yes
+        env:
+          CRE_API_KEY: ${{ secrets.CRE_API_KEY }}
+          CRE_ETH_PRIVATE_KEY: ${{ secrets.CRE_ETH_PRIVATE_KEY }}
+          INFURA_API_KEY: ${{ secrets.INFURA_API_KEY }}
+```
+
+{/* prettier-ignore */}
+<Aside type="note" title="API key authentication">
+  Use `CRE_API_KEY` for non-interactive authentication in CI/CD pipelines instead of `cre login`. Create an API key from the CRE platform under **Organization → APIs**. See [Authentication](/cre/reference/cli/authentication#api-key-authentication) for setup instructions.
+</Aside>
+
+{/* prettier-ignore */}
+<Aside type="note" title="RPC URLs in CI/CD">
+  Use `${VAR_NAME}` syntax in your `project.yaml` RPC URLs to inject secrets from your CI/CD environment. See [Environment variable interpolation in RPC URLs](/cre/reference/project-configuration#environment-variable-interpolation-in-rpc-urls) for details.
+</Aside>
+
 ## Using multi-sig wallets
 
 The `deploy` command supports multi-sig wallets through the `--unsigned` flag. When using this flag, the CLI generates raw transaction data that you can submit through your multi-sig wallet interface instead of sending the transaction directly.