update content up to 1.5.0, new features, small tickets, other feedback

Author: dev-dist

src/content/cre/capabilities/http.mdx

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

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

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

src/content/cre/guides/operations/deploying-workflows.mdx

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

src/content/cre/guides/workflow/using-evm-client/generating-bindings-go.mdx

@@ -7,7 +7,7 @@ date: Last Modified
 metadata:
   description: "Create type-safe contract interfaces: learn to generate Go bindings from smart contract ABIs for safer, cleaner workflow code."
   datePublished: "2025-11-04"
-  lastModified: "2026-03-05"
+  lastModified: "2026-03-17"
 ---
 
 import { Aside } from "@components"
@@ -38,7 +38,12 @@ cre generate-bindings evm --language go
 
 ### Step 1: Add your contract ABI
 
-Place your contract's ABI JSON file into the `contracts/evm/src/abi/` directory. For example, to generate bindings for a `PriceUpdater` contract, you would create `contracts/evm/src/abi/PriceUpdater.abi` with your ABI content.
+Place your contract ABI file into the `contracts/evm/src/abi/` directory. Two file formats are supported:
+
+- **`*.abi`** — A raw JSON array of ABI entries, as produced by `solc` or extracted from a compiled artifact
+- **`*.json`** — A compiled artifact file (Hardhat, Foundry, or similar) with a top-level `"abi"` field
+
+For example, to generate bindings for a `PriceUpdater` contract, create either `contracts/evm/src/abi/PriceUpdater.abi` or `contracts/evm/src/abi/PriceUpdater.json`. Both formats can coexist in the same directory.
 
 ### Step 2: Generate the bindings
 
@@ -48,7 +53,7 @@ From your **project root**, run the binding generator:
 cre generate-bindings evm
 ```
 
-This command scans all `.abi` files in `contracts/evm/src/abi/` and generates corresponding Go packages in `contracts/evm/src/generated/`. For each contract, two files are generated:
+This command scans all `.abi` and `.json` files in `contracts/evm/src/abi/` and generates corresponding Go packages in `contracts/evm/src/generated/`. For each contract, two files are generated:
 
 - `<ContractName>.go` — The main binding for interacting with the contract
 - `<ContractName>_mock.go` — A mock implementation for testing your workflows without deploying contracts

src/content/cre/guides/workflow/using-evm-client/generating-bindings-ts.mdx

@@ -7,7 +7,7 @@ date: Last Modified
 metadata:
   description: "Create type-safe contract interfaces: learn to generate TypeScript bindings from smart contract ABIs for safer, cleaner workflow code."
   datePublished: "2026-03-05"
-  lastModified: "2026-03-05"
+  lastModified: "2026-03-17"
 ---
 
 import { Aside } from "@components"
@@ -38,7 +38,12 @@ cre generate-bindings evm --language typescript
 
 ### Step 1: Add your contract ABI
 
-Place your contract's ABI JSON file into the `contracts/evm/src/abi/` directory. For example, to generate bindings for a `PriceUpdater` contract, create `contracts/evm/src/abi/PriceUpdater.abi` with your ABI content.
+Place your contract ABI file into the `contracts/evm/src/abi/` directory. Two file formats are supported:
+
+- **`*.abi`** — A raw JSON array of ABI entries, as produced by `solc` or extracted from a compiled artifact
+- **`*.json`** — A compiled artifact file (Hardhat, Foundry, or similar) with a top-level `"abi"` field
+
+For example, to generate bindings for a `PriceUpdater` contract, create either `contracts/evm/src/abi/PriceUpdater.abi` or `contracts/evm/src/abi/PriceUpdater.json`. Both formats can coexist in the same directory.
 
 ### Step 2: Generate the bindings
 
@@ -48,7 +53,7 @@ From your **project root**, run:
 cre generate-bindings evm
 ```
 
-This scans all `.abi` files in `contracts/evm/src/abi/` and generates corresponding TypeScript files in `contracts/evm/ts/generated/`. For each contract, three files are generated:
+This scans all `.abi` and `.json` files in `contracts/evm/src/abi/` and generates corresponding TypeScript files in `contracts/evm/ts/generated/`. For each contract, three files are generated:
 
 - `<ContractName>.ts` — The typed binding class with read, write, and event trigger methods.
 - `<ContractName>_mock.ts` — A mock implementation for testing your workflows without deploying contracts.

src/content/cre/guides/workflow/using-http-client/get-request-go.mdx

@@ -7,7 +7,7 @@ pageId: "guides-workflow-http-get-request"
 metadata:
   description: "Fetch data from APIs in Go: learn to make GET requests with consensus validation to bring offchain data into your workflow."
   datePublished: "2025-11-04"
-  lastModified: "2026-02-03"
+  lastModified: "2026-03-17"
 ---
 
 import { Aside } from "@components"
@@ -221,3 +221,54 @@ func onCronTrigger(config *Config, runtime cre.Runtime, trigger *cron.Payload) (
 ## Customizing your requests
 
 The `http.Request` struct provides several fields to customize your request. See the [HTTP Client SDK Reference](/cre/reference/sdk/http-client) for a full list of options.
+
+## Best practices
+
+### Parse inside the node function, not outside it
+
+When using a numeric aggregation method such as `ConsensusMedianAggregation` or a median field tag, the value returned from your node function must be a numeric type. If your node function returns a raw HTTP response body (a string), consensus will fail with an error like:
+
+```
+unsupported type for median aggregation: *pb.Value_StringValue
+```
+
+This commonly happens when an endpoint returns an error body — for example, `"error"` or a JSON error object — and the node function passes that string directly to the aggregation step instead of parsing it first.
+
+**Incorrect pattern** — returning a raw string that gets passed to median:
+
+```go
+func fetchData(config *Config, nodeRuntime cre.NodeRuntime) (string, error) {
+    // ...
+    return resp.Body, nil // ❌ raw string; will fail if aggregation is median
+}
+```
+
+**Correct pattern** — parse inside the node function and return a numeric value:
+
+```go
+func fetchData(config *Config, nodeRuntime cre.NodeRuntime) (float64, error) {
+    client := &http.Client{}
+    resp, err := client.SendRequest(nodeRuntime, &http.Request{
+        Url:    config.ApiUrl,
+        Method: "GET",
+    }).Await()
+    if err != nil {
+        return 0, fmt.Errorf("request failed: %w", err) // ✓ return error, not a string
+    }
+
+    var data struct {
+        Price float64 `json:"price"`
+    }
+    if err := json.Unmarshal([]byte(resp.Body), &data); err != nil {
+        return 0, fmt.Errorf("failed to parse response body %q: %w", resp.Body, err) // ✓ return error
+    }
+    return data.Price, nil // ✓ return the numeric value
+}
+```
+
+If the endpoint is down or returns an unexpected body, returning an error (rather than the raw string) causes the node to report a failure to the consensus mechanism, which handles node-level failures gracefully.
+
+{/* prettier-ignore */}
+<Aside type="note" title="Confidential HTTP">
+  This parsing requirement applies to standard HTTP requests. When using the [Confidential HTTP capability](/cre/capabilities/confidential-http), requests run in a Trusted Execution Environment and the response is not accessible for parsing in node mode.
+</Aside>