From 028facb70743f72431270d108cf1a24cb2bea7fe Mon Sep 17 00:00:00 2001 From: devin distefano Date: Tue, 17 Mar 2026 15:18:35 -0500 Subject: [PATCH 1/2] supported networks update --- public/changelog.json | 57 +++++++++ .../forwarder-directory-go.mdx | 33 +++++ .../forwarder-directory-ts.mdx | 33 +++++ src/content/cre/llms-full-go.txt | 118 +++++++++++++++++- src/content/cre/llms-full-ts.txt | 118 +++++++++++++++++- src/content/cre/release-notes.mdx | 66 +++++++++- src/content/cre/supported-networks-go.mdx | 19 ++- src/content/cre/supported-networks-ts.mdx | 19 ++- 8 files changed, 456 insertions(+), 7 deletions(-) diff --git a/public/changelog.json b/public/changelog.json index c923d6a0467..5da8a17ac14 100644 --- a/public/changelog.json +++ b/public/changelog.json @@ -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", diff --git a/src/content/cre/guides/workflow/using-evm-client/forwarder-directory-go.mdx b/src/content/cre/guides/workflow/using-evm-client/forwarder-directory-go.mdx index 5777e6cbdcb..2bd5a06bfe1 100644 --- a/src/content/cre/guides/workflow/using-evm-client/forwarder-directory-go.mdx +++ b/src/content/cre/guides/workflow/using-evm-client/forwarder-directory-go.mdx @@ -57,11 +57,20 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Avalanche | | | | Base | | | | BNB Chain | | | +| Celo | | | | Ethereum Mainnet | | | +| Gnosis Chain | | | +| Ink | | | | Jovay Mainnet | | | +| Linea | | | +| Mantle | | | +| MegaETH | | | | OP Mainnet | | | | Pharos Mainnet | | | +| Plasma | | | | Polygon | | | +| Scroll | | | +| Sonic | | | | World Chain | | | | XLayer Mainnet | | | | ZKSync Era | | | @@ -76,15 +85,22 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Avalanche Fuji | | | | Base Sepolia | | | | BNB Chain Testnet | | | +| Cronos Testnet | | | | Ethereum Sepolia | | | | Hyperliquid Testnet | | | | Ink Sepolia | | | | Jovay Testnet | | | | Linea Sepolia | | | +| Mantle Sepolia | | | +| MegaETH Testnet 2 | | | | OP Sepolia | | | | Pharos Atlantic Testnet | | | | Plasma Testnet | | | | Polygon Amoy | | | +| Scroll Sepolia | | | +| Sonic Testnet | | | +| TAC Testnet | | | +| Unichain Sepolia | | | | World Chain Sepolia | | | | XLayer Testnet | | | | ZKSync Era Sepolia | | | @@ -101,11 +117,20 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Avalanche | | | | Base | | | | BNB Chain | | | +| Celo | | | | Ethereum Mainnet | | | +| Gnosis Chain | | | +| Ink | | | | Jovay Mainnet | | | +| Linea | | | +| Mantle | | | +| MegaETH | | | | OP Mainnet | | | | Pharos Mainnet | | | +| Plasma | | | | Polygon | | | +| Scroll | | | +| Sonic | | | | World Chain | | | | XLayer Mainnet | | | | ZKSync Era | | | @@ -119,14 +144,22 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Avalanche Fuji | | | | Base Sepolia | | | | BNB Chain Testnet | | | +| Cronos Testnet | | | | Ethereum Sepolia | | | | Hyperliquid Testnet | | | | Ink Sepolia | | | | Jovay Testnet | | | | Linea Sepolia | | | +| Mantle Sepolia | | | +| MegaETH Testnet 2 | | | | OP Sepolia | | | | Pharos Atlantic Testnet | | | | Plasma Testnet | | | | Polygon Amoy | | | +| Scroll Sepolia | | | +| Sonic Testnet | | | +| TAC Testnet | | | +| Unichain Sepolia | | | | World Chain Sepolia | | | +| XLayer Testnet | | | | ZKSync Era Sepolia | | | diff --git a/src/content/cre/guides/workflow/using-evm-client/forwarder-directory-ts.mdx b/src/content/cre/guides/workflow/using-evm-client/forwarder-directory-ts.mdx index cf9c6990f09..04d8da0a54b 100644 --- a/src/content/cre/guides/workflow/using-evm-client/forwarder-directory-ts.mdx +++ b/src/content/cre/guides/workflow/using-evm-client/forwarder-directory-ts.mdx @@ -57,11 +57,20 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Avalanche | | | | Base | | | | BNB Smart Chain | | | +| Celo | | | | Ethereum Mainnet | | | +| Gnosis Chain | | | +| Ink | | | | Jovay Mainnet | | | +| Linea | | | +| Mantle | | | +| MegaETH | | | | OP Mainnet | | | | Pharos Mainnet | | | +| Plasma | | | | Polygon | | | +| Scroll | | | +| Sonic | | | | World Chain | | | | XLayer Mainnet | | | | ZKSync Era | | | @@ -76,15 +85,22 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Avalanche Fuji | | | | Base Sepolia | | | | BSC Testnet | | | +| Cronos Testnet | | | | Ethereum Sepolia | | | | Hyperliquid Testnet | | | | Ink Sepolia | | | | Jovay Testnet | | | | Linea Sepolia | | | +| Mantle Sepolia | | | +| MegaETH Testnet 2 | | | | OP Sepolia | | | | Pharos Atlantic Testnet | | | | Plasma Testnet | | | | Polygon Amoy | | | +| Scroll Sepolia | | | +| Sonic Testnet | | | +| TAC Testnet | | | +| Unichain Sepolia | | | | World Chain Sepolia | | | | XLayer Testnet | | | | ZKSync Era Sepolia | | | @@ -101,11 +117,20 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Avalanche | | | | Base | | | | BNB Smart Chain | | | +| Celo | | | | Ethereum Mainnet | | | +| Gnosis Chain | | | +| Ink | | | | Jovay Mainnet | | | +| Linea | | | +| Mantle | | | +| MegaETH | | | | OP Mainnet | | | | Pharos Mainnet | | | +| Plasma | | | | Polygon | | | +| Scroll | | | +| Sonic | | | | World Chain | | | | XLayer Mainnet | | | | ZKSync Era | | | @@ -119,14 +144,22 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Avalanche Fuji | | | | Base Sepolia | | | | BSC Testnet | | | +| Cronos Testnet | | | | Ethereum Sepolia | | | | Hyperliquid Testnet | | | | Ink Sepolia | | | | Jovay Testnet | | | | Linea Sepolia | | | +| Mantle Sepolia | | | +| MegaETH Testnet 2 | | | | OP Sepolia | | | | Pharos Atlantic Testnet | | | | Plasma Testnet | | | | Polygon Amoy | | | +| Scroll Sepolia | | | +| Sonic Testnet | | | +| TAC Testnet | | | +| Unichain Sepolia | | | | World Chain Sepolia | | | +| XLayer Testnet | | | | ZKSync Era Sepolia | | | diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index a93ddd0c0c3..16be8f793d9 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -442,10 +442,74 @@ To help us assist you faster, please include: # Release Notes Source: https://docs.chain.link/cre/release-notes -Last Updated: 2026-03-05 +Last Updated: 2026-03-17 This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations. +## CLI v1.5.0 - March 17, 2026 + +**CRE CLI version 1.5.0 is now available.** + +- **New Mainnets**: Added Celo, Gnosis Chain, Ink, Linea, Mantle, MegaETH, Plasma, Scroll, and Sonic mainnet support for simulation and production deployment. +- **New Testnets**: Added Cronos, Mantle Sepolia, MegaETH Testnet 2, Scroll Sepolia, Sonic Testnet, TAC Testnet, and Unichain Sepolia testnet support. +- **`cre hash` command**: New command to display content hashes for workflow artifacts. Hashes are also displayed automatically during `cre workflow build` and `cre workflow deploy`. +- **Environment variable resolution in RPC URLs**: Use `${VAR}` syntax in your `project.yaml` RPC URLs to inject values from environment variables. +- **JSON ABI support in `cre generate-bindings`**: The `cre generate-bindings evm` command now accepts raw JSON ABI files in addition to compiled Hardhat and Foundry artifacts. +- **`.env` support across all commands**: The `.env` file is now respected across all CRE commands, with `.env` values taking precedence over other settings. +- **Bug Fix**: Fixed an issue where `cre workflow build` could fail in configurations where `cre workflow simulate` succeeded. + +**Required versions for new networks:** + +- All new mainnets and testnets: CLI v1.5.0+, Go SDK v1.6.0+, TS SDK v1.3.0+ + +**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.4.0...v1.5.0) + +## Go SDK v1.6.0 - March 16, 2026 + +**Go SDK version 1.6.0** updates EVM capabilities to support the new networks added in CLI v1.5.0. + +- **New Networks**: Updated EVM client capabilities to support Celo, Gnosis Chain, Ink, Linea, Mantle, MegaETH, Plasma, Scroll, Sonic, and their associated testnets + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-go/compare/v1.5.0...v1.6.0) + +## TS SDK v1.3.0 - March 16, 2026 + +**TypeScript SDK version 1.3.0** updates EVM capabilities to support the new networks added in CLI v1.5.0. + +- **New Networks**: Updated EVM client capabilities to support new networks added in CLI v1.5.0 + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-typescript/compare/v1.2.0...v1.3.0) + +## CLI v1.4.0 - March 12, 2026 + +**CRE CLI version 1.4.0 is now available.** + +- **CI/CD pipeline support**: `cre workflow build`, `cre workflow upload`, and `cre workflow deploy` can now be run as independent steps for better integration with CI/CD pipelines. +- **MultiHeaders support**: The HTTP capability now supports sending multiple headers per request. + +This release also includes various internal improvements and security fixes. + +**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.3.0...v1.4.0) + +## TS SDK v1.2.0 - March 12, 2026 + +**TypeScript SDK version 1.2.0** includes improvements to the EVM client and developer experience. + +- **`logTriggerConfig` helper**: New helper for configuring EVM log triggers in your workflow +- **Improved error messages**: Added field-level context to `encodeCallMsg` errors for easier debugging + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-typescript/compare/v1.1.0...v1.2.0) + ## CLI v1.3.0 - March 5, 2026 **CRE CLI version 1.3.0 is now available.** @@ -11310,11 +11374,20 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Avalanche | avalanche-mainnet | 0xdc21e279934ff6721cadfdd112dafb3261f09a2c | | Base | ethereum-mainnet-base-1 | 0x5e342a8438b4f5d39e72875fcee6f76b39cce548 | | BNB Chain | binance_smart_chain-mainnet | 0x6f3239bbb26e98961e1115aba83f8a282e5508c8 | +| Celo | celo-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Ethereum Mainnet | ethereum-mainnet | 0xa3d1ad4ac559a6575a114998affb2fb2ec97a7d9 | +| Gnosis Chain | gnosis-chain-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Ink | ethereum-mainnet-ink-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Jovay Mainnet | jovay-mainnet | 0x2B3068C4B288A2CD1f8B3613b8f33ef7cEecadC4 | +| Linea | ethereum-mainnet-linea-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Mantle | ethereum-mainnet-mantle-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| MegaETH | megaeth-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | OP Mainnet | ethereum-mainnet-optimism-1 | 0x9119a1501550ed94a3f2794038ed9258337afa18 | | Pharos Mainnet | pharos-mainnet | 0x2B3068C4B288A2CD1f8B3613b8f33ef7cEecadC4 | +| Plasma | plasma-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Polygon | polygon-mainnet | 0xf458d621885e29a5003ea9bbba5280d54e19b1ce | +| Scroll | ethereum-mainnet-scroll-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Sonic | sonic-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | World Chain | ethereum-mainnet-worldchain-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | XLayer Mainnet | ethereum-mainnet-xlayer-1 | 0x2B3068C4B288A2CD1f8B3613b8f33ef7cEecadC4 | | ZKSync Era | ethereum-mainnet-zksync-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | @@ -11329,15 +11402,22 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Avalanche Fuji | avalanche-testnet-fuji | 0x2e7371a5d032489e4f60216d8d898a4c10805963 | | Base Sepolia | ethereum-testnet-sepolia-base-1 | 0x82300bd7c3958625581cc2f77bc6464dcecdf3e5 | | BNB Chain Testnet | binance_smart_chain-testnet | 0xa238e42cb8782808dbb2f37e19859244ec4779b0 | +| Cronos Testnet | cronos-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Ethereum Sepolia | ethereum-testnet-sepolia | 0x15fC6ae953E024d975e77382eEeC56A9101f9F88 | | Hyperliquid Testnet | hyperliquid-testnet | 0xB27fA1c28288c50542527F64BCda22C9FbAc24CB | | Ink Sepolia | ink-testnet-sepolia | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Jovay Testnet | jovay-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Linea Sepolia | ethereum-testnet-sepolia-linea-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Mantle Sepolia | ethereum-testnet-sepolia-mantle-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| MegaETH Testnet 2 | megaeth-testnet-2 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0xa2888380dff3704a8ab6d1cd1a8f69c15fea5ee3 | | Pharos Atlantic Testnet | pharos-atlantic-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Plasma Testnet | plasma-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Polygon Amoy | polygon-testnet-amoy | 0x3675a5eb2286a3f87e8278fc66edf458a2e3bb74 | +| Scroll Sepolia | ethereum-testnet-sepolia-scroll-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Sonic Testnet | sonic-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| TAC Testnet | tac-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Unichain Sepolia | ethereum-testnet-sepolia-unichain-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | World Chain Sepolia | ethereum-testnet-sepolia-worldchain-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | XLayer Testnet | xlayer-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | ZKSync Era Sepolia | ethereum-testnet-sepolia-zksync-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | @@ -11354,11 +11434,20 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Avalanche | avalanche-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Base | ethereum-mainnet-base-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | BNB Chain | binance_smart_chain-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Celo | celo-mainnet | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | | Ethereum Mainnet | ethereum-mainnet | 0x0b93082D9b3C7C97fAcd250082899BAcf3af3885 | +| Gnosis Chain | gnosis-chain-mainnet | 0x9eF6468C5f37b976E57d52054c693269479A784d | +| Ink | ethereum-mainnet-ink-1 | 0x9eF6468C5f37b976E57d52054c693269479A784d | | Jovay Mainnet | jovay-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Linea | ethereum-mainnet-linea-1 | 0x9eF6468C5f37b976E57d52054c693269479A784d | +| Mantle | ethereum-mainnet-mantle-1 | 0xB9F79d863261869B234c481D1f9A7af84AeAd192 | +| MegaETH | megaeth-mainnet | 0x7BCcaFBD064cB3658476066Cc33ceE3F3414c04c | | OP Mainnet | ethereum-mainnet-optimism-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | Pharos Mainnet | pharos-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Plasma | plasma-mainnet | 0x7BCcaFBD064cB3658476066Cc33ceE3F3414c04c | | Polygon | polygon-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Scroll | ethereum-mainnet-scroll-1 | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | +| Sonic | sonic-mainnet | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | | World Chain | ethereum-mainnet-worldchain-1 | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | | XLayer Mainnet | ethereum-mainnet-xlayer-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | ZKSync Era | ethereum-mainnet-zksync-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | @@ -11372,16 +11461,24 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Avalanche Fuji | avalanche-testnet-fuji | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Base Sepolia | ethereum-testnet-sepolia-base-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | BNB Chain Testnet | binance_smart_chain-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Cronos Testnet | cronos-testnet | 0x9eF6468C5f37b976E57d52054c693269479A784d | | Ethereum Sepolia | ethereum-testnet-sepolia | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | Hyperliquid Testnet | hyperliquid-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Ink Sepolia | ink-testnet-sepolia | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Jovay Testnet | jovay-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Linea Sepolia | ethereum-testnet-sepolia-linea-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Mantle Sepolia | ethereum-testnet-sepolia-mantle-1 | 0xB9F79d863261869B234c481D1f9A7af84AeAd192 | +| MegaETH Testnet 2 | megaeth-testnet-2 | 0x9eF6468C5f37b976E57d52054c693269479A784d | | OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Pharos Atlantic Testnet | pharos-atlantic-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Plasma Testnet | plasma-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Polygon Amoy | polygon-testnet-amoy | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Scroll Sepolia | ethereum-testnet-sepolia-scroll-1 | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | +| Sonic Testnet | sonic-testnet | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | +| TAC Testnet | tac-testnet | 0x7BCcaFBD064cB3658476066Cc33ceE3F3414c04c | +| Unichain Sepolia | ethereum-testnet-sepolia-unichain-1 | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | | World Chain Sepolia | ethereum-testnet-sepolia-worldchain-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| XLayer Testnet | xlayer-testnet | 0x9eF6468C5f37b976E57d52054c693269479A784d | | ZKSync Era Sepolia | ethereum-testnet-sepolia-zksync-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | --- @@ -16772,7 +16869,7 @@ This section provides a reference for the built-in trigger capabilities of the C # Supported Networks Source: https://docs.chain.link/cre/supported-networks-go -Last Updated: 2026-03-05 +Last Updated: 2026-03-17 This page lists all EVM-compatible networks supported by CRE workflows, along with the minimum CLI and SDK versions required for each network. @@ -16791,11 +16888,20 @@ Network support depends on your CLI and SDK versions. The tables below show the | Avalanche | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Base | v1.0.0+ | v1.0.0+ | v1.0.1+ | | BNB Chain | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Celo | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Ethereum | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Gnosis Chain | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Ink | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Jovay | v1.3.0+ | v1.4.0+ | v1.1.3+ | +| Linea | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Mantle | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| MegaETH | v1.5.0+ | v1.6.0+ | v1.3.0+ | | OP Mainnet | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Pharos | v1.3.0+ | v1.4.0+ | v1.1.3+ | +| Plasma | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Polygon | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Scroll | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Sonic | v1.5.0+ | v1.6.0+ | v1.3.0+ | | World Chain | v1.0.11+ | v1.2.0+ | v1.0.9+ | | XLayer | v1.3.0+ | v1.4.0+ | v1.1.3+ | | ZKSync Era | v1.0.6+ | v1.1.3+ | v1.0.7+ | @@ -16810,16 +16916,24 @@ Network support depends on your CLI and SDK versions. The tables below show the | Avalanche Fuji | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Base Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | BNB Chain Testnet | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Cronos Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Ethereum Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Hyperliquid Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Ink Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Jovay Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Linea Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | +| Mantle Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| MegaETH Testnet 2 | v1.5.0+ | v1.6.0+ | v1.3.0+ | | OP Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Pharos Atlantic Testnet | v1.3.0+ | v1.5.0+ | v1.1.4+ | | Plasma Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Polygon Amoy | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Scroll Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Sonic Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| TAC Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Unichain Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | | World Chain Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | +| XLayer Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | | ZKSync Era Sepolia | v1.0.6+ | v1.1.2+ | v1.0.7+ | ## Forwarder Addresses diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index fed3e34a447..f3557721c16 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -442,10 +442,74 @@ To help us assist you faster, please include: # Release Notes Source: https://docs.chain.link/cre/release-notes -Last Updated: 2026-03-05 +Last Updated: 2026-03-17 This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations. +## CLI v1.5.0 - March 17, 2026 + +**CRE CLI version 1.5.0 is now available.** + +- **New Mainnets**: Added Celo, Gnosis Chain, Ink, Linea, Mantle, MegaETH, Plasma, Scroll, and Sonic mainnet support for simulation and production deployment. +- **New Testnets**: Added Cronos, Mantle Sepolia, MegaETH Testnet 2, Scroll Sepolia, Sonic Testnet, TAC Testnet, and Unichain Sepolia testnet support. +- **`cre hash` command**: New command to display content hashes for workflow artifacts. Hashes are also displayed automatically during `cre workflow build` and `cre workflow deploy`. +- **Environment variable resolution in RPC URLs**: Use `${VAR}` syntax in your `project.yaml` RPC URLs to inject values from environment variables. +- **JSON ABI support in `cre generate-bindings`**: The `cre generate-bindings evm` command now accepts raw JSON ABI files in addition to compiled Hardhat and Foundry artifacts. +- **`.env` support across all commands**: The `.env` file is now respected across all CRE commands, with `.env` values taking precedence over other settings. +- **Bug Fix**: Fixed an issue where `cre workflow build` could fail in configurations where `cre workflow simulate` succeeded. + +**Required versions for new networks:** + +- All new mainnets and testnets: CLI v1.5.0+, Go SDK v1.6.0+, TS SDK v1.3.0+ + +**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.4.0...v1.5.0) + +## Go SDK v1.6.0 - March 16, 2026 + +**Go SDK version 1.6.0** updates EVM capabilities to support the new networks added in CLI v1.5.0. + +- **New Networks**: Updated EVM client capabilities to support Celo, Gnosis Chain, Ink, Linea, Mantle, MegaETH, Plasma, Scroll, Sonic, and their associated testnets + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-go/compare/v1.5.0...v1.6.0) + +## TS SDK v1.3.0 - March 16, 2026 + +**TypeScript SDK version 1.3.0** updates EVM capabilities to support the new networks added in CLI v1.5.0. + +- **New Networks**: Updated EVM client capabilities to support new networks added in CLI v1.5.0 + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-typescript/compare/v1.2.0...v1.3.0) + +## CLI v1.4.0 - March 12, 2026 + +**CRE CLI version 1.4.0 is now available.** + +- **CI/CD pipeline support**: `cre workflow build`, `cre workflow upload`, and `cre workflow deploy` can now be run as independent steps for better integration with CI/CD pipelines. +- **MultiHeaders support**: The HTTP capability now supports sending multiple headers per request. + +This release also includes various internal improvements and security fixes. + +**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.3.0...v1.4.0) + +## TS SDK v1.2.0 - March 12, 2026 + +**TypeScript SDK version 1.2.0** includes improvements to the EVM client and developer experience. + +- **`logTriggerConfig` helper**: New helper for configuring EVM log triggers in your workflow +- **Improved error messages**: Added field-level context to `encodeCallMsg` errors for easier debugging + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-typescript/compare/v1.1.0...v1.2.0) + ## CLI v1.3.0 - March 5, 2026 **CRE CLI version 1.3.0 is now available.** @@ -10699,11 +10763,20 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Avalanche | avalanche-mainnet | 0xdc21e279934ff6721cadfdd112dafb3261f09a2c | | Base | ethereum-mainnet-base-1 | 0x5e342a8438b4f5d39e72875fcee6f76b39cce548 | | BNB Smart Chain | binance_smart_chain-mainnet | 0x6f3239bbb26e98961e1115aba83f8a282e5508c8 | +| Celo | celo-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Ethereum Mainnet | ethereum-mainnet | 0xa3d1ad4ac559a6575a114998affb2fb2ec97a7d9 | +| Gnosis Chain | gnosis-chain-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Ink | ethereum-mainnet-ink-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Jovay Mainnet | jovay-mainnet | 0x2B3068C4B288A2CD1f8B3613b8f33ef7cEecadC4 | +| Linea | ethereum-mainnet-linea-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Mantle | ethereum-mainnet-mantle-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| MegaETH | megaeth-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | OP Mainnet | ethereum-mainnet-optimism-1 | 0x9119a1501550ed94a3f2794038ed9258337afa18 | | Pharos Mainnet | pharos-mainnet | 0x2B3068C4B288A2CD1f8B3613b8f33ef7cEecadC4 | +| Plasma | plasma-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Polygon | polygon-mainnet | 0xf458d621885e29a5003ea9bbba5280d54e19b1ce | +| Scroll | ethereum-mainnet-scroll-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Sonic | sonic-mainnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | World Chain | ethereum-mainnet-worldchain-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | XLayer Mainnet | ethereum-mainnet-xlayer-1 | 0x2B3068C4B288A2CD1f8B3613b8f33ef7cEecadC4 | | ZKSync Era | ethereum-mainnet-zksync-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | @@ -10718,15 +10791,22 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Avalanche Fuji | avalanche-testnet-fuji | 0x2e7371a5d032489e4f60216d8d898a4c10805963 | | Base Sepolia | ethereum-testnet-sepolia-base-1 | 0x82300bd7c3958625581cc2f77bc6464dcecdf3e5 | | BSC Testnet | binance_smart_chain-testnet | 0xa238e42cb8782808dbb2f37e19859244ec4779b0 | +| Cronos Testnet | cronos-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Ethereum Sepolia | ethereum-testnet-sepolia | 0x15fC6ae953E024d975e77382eEeC56A9101f9F88 | | Hyperliquid Testnet | hyperliquid-testnet | 0xB27fA1c28288c50542527F64BCda22C9FbAc24CB | | Ink Sepolia | ink-testnet-sepolia | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Jovay Testnet | jovay-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Linea Sepolia | ethereum-testnet-sepolia-linea-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Mantle Sepolia | ethereum-testnet-sepolia-mantle-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| MegaETH Testnet 2 | megaeth-testnet-2 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0xa2888380dff3704a8ab6d1cd1a8f69c15fea5ee3 | | Pharos Atlantic Testnet | pharos-atlantic-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Plasma Testnet | plasma-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | Polygon Amoy | polygon-testnet-amoy | 0x3675a5eb2286a3f87e8278fc66edf458a2e3bb74 | +| Scroll Sepolia | ethereum-testnet-sepolia-scroll-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Sonic Testnet | sonic-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| TAC Testnet | tac-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | +| Unichain Sepolia | ethereum-testnet-sepolia-unichain-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | World Chain Sepolia | ethereum-testnet-sepolia-worldchain-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | XLayer Testnet | xlayer-testnet | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | | ZKSync Era Sepolia | ethereum-testnet-sepolia-zksync-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | @@ -10743,11 +10823,20 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Avalanche | avalanche-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Base | ethereum-mainnet-base-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | BNB Smart Chain | binance_smart_chain-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Celo | celo-mainnet | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | | Ethereum Mainnet | ethereum-mainnet | 0x0b93082D9b3C7C97fAcd250082899BAcf3af3885 | +| Gnosis Chain | gnosis-chain-mainnet | 0x9eF6468C5f37b976E57d52054c693269479A784d | +| Ink | ethereum-mainnet-ink-1 | 0x9eF6468C5f37b976E57d52054c693269479A784d | | Jovay Mainnet | jovay-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Linea | ethereum-mainnet-linea-1 | 0x9eF6468C5f37b976E57d52054c693269479A784d | +| Mantle | ethereum-mainnet-mantle-1 | 0xB9F79d863261869B234c481D1f9A7af84AeAd192 | +| MegaETH | megaeth-mainnet | 0x7BCcaFBD064cB3658476066Cc33ceE3F3414c04c | | OP Mainnet | ethereum-mainnet-optimism-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | Pharos Mainnet | pharos-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Plasma | plasma-mainnet | 0x7BCcaFBD064cB3658476066Cc33ceE3F3414c04c | | Polygon | polygon-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Scroll | ethereum-mainnet-scroll-1 | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | +| Sonic | sonic-mainnet | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | | World Chain | ethereum-mainnet-worldchain-1 | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | | XLayer Mainnet | ethereum-mainnet-xlayer-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | ZKSync Era | ethereum-mainnet-zksync-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | @@ -10761,16 +10850,24 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Avalanche Fuji | avalanche-testnet-fuji | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Base Sepolia | ethereum-testnet-sepolia-base-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | BSC Testnet | binance_smart_chain-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Cronos Testnet | cronos-testnet | 0x9eF6468C5f37b976E57d52054c693269479A784d | | Ethereum Sepolia | ethereum-testnet-sepolia | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | Hyperliquid Testnet | hyperliquid-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Ink Sepolia | ink-testnet-sepolia | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Jovay Testnet | jovay-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Linea Sepolia | ethereum-testnet-sepolia-linea-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Mantle Sepolia | ethereum-testnet-sepolia-mantle-1 | 0xB9F79d863261869B234c481D1f9A7af84AeAd192 | +| MegaETH Testnet 2 | megaeth-testnet-2 | 0x9eF6468C5f37b976E57d52054c693269479A784d | | OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Pharos Atlantic Testnet | pharos-atlantic-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Plasma Testnet | plasma-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | | Polygon Amoy | polygon-testnet-amoy | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Scroll Sepolia | ethereum-testnet-sepolia-scroll-1 | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | +| Sonic Testnet | sonic-testnet | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | +| TAC Testnet | tac-testnet | 0x7BCcaFBD064cB3658476066Cc33ceE3F3414c04c | +| Unichain Sepolia | ethereum-testnet-sepolia-unichain-1 | 0x98B8335d29Aca40840Ed8426dA1A0aAa8677d8D1 | | World Chain Sepolia | ethereum-testnet-sepolia-worldchain-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| XLayer Testnet | xlayer-testnet | 0x9eF6468C5f37b976E57d52054c693269479A784d | | ZKSync Era Sepolia | ethereum-testnet-sepolia-zksync-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | --- @@ -17957,7 +18054,7 @@ This section provides a reference for the built-in trigger capabilities of the C # Supported Networks Source: https://docs.chain.link/cre/supported-networks-ts -Last Updated: 2026-03-05 +Last Updated: 2026-03-17 This page lists all EVM-compatible networks supported by CRE workflows, along with the minimum CLI and SDK versions required for each network. @@ -17976,11 +18073,20 @@ Network support depends on your CLI and SDK versions. The tables below show the | Avalanche | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Base | v1.0.0+ | v1.0.0+ | v1.0.1+ | | BNB Chain | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Celo | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Ethereum | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Gnosis Chain | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Ink | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Jovay | v1.3.0+ | v1.4.0+ | v1.1.3+ | +| Linea | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Mantle | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| MegaETH | v1.5.0+ | v1.6.0+ | v1.3.0+ | | OP Mainnet | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Pharos | v1.3.0+ | v1.4.0+ | v1.1.3+ | +| Plasma | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Polygon | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Scroll | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Sonic | v1.5.0+ | v1.6.0+ | v1.3.0+ | | World Chain | v1.0.11+ | v1.2.0+ | v1.0.9+ | | XLayer | v1.3.0+ | v1.4.0+ | v1.1.3+ | | ZKSync Era | v1.0.6+ | v1.1.3+ | v1.0.7+ | @@ -17995,16 +18101,24 @@ Network support depends on your CLI and SDK versions. The tables below show the | Avalanche Fuji | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Base Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | BNB Chain Testnet | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Cronos Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Ethereum Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Hyperliquid Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Ink Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Jovay Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Linea Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | +| Mantle Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| MegaETH Testnet 2 | v1.5.0+ | v1.6.0+ | v1.3.0+ | | OP Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Pharos Atlantic Testnet | v1.3.0+ | v1.5.0+ | v1.1.4+ | | Plasma Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Polygon Amoy | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Scroll Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Sonic Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| TAC Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Unichain Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | | World Chain Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | +| XLayer Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | | ZKSync Era Sepolia | v1.0.6+ | v1.1.2+ | v1.0.7+ | ## Forwarder Addresses diff --git a/src/content/cre/release-notes.mdx b/src/content/cre/release-notes.mdx index f19f5001783..2d0760a9b8b 100644 --- a/src/content/cre/release-notes.mdx +++ b/src/content/cre/release-notes.mdx @@ -5,13 +5,77 @@ 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-03-05" + lastModified: "2026-03-17" --- import { Aside } from "@components" This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations. +## CLI v1.5.0 - March 17, 2026 + +**CRE CLI version 1.5.0 is now available.** + +- **New Mainnets**: Added Celo, Gnosis Chain, Ink, Linea, Mantle, MegaETH, Plasma, Scroll, and Sonic mainnet support for simulation and production deployment. +- **New Testnets**: Added Cronos, Mantle Sepolia, MegaETH Testnet 2, Scroll Sepolia, Sonic Testnet, TAC Testnet, and Unichain Sepolia testnet support. +- **`cre hash` command**: New command to display content hashes for workflow artifacts. Hashes are also displayed automatically during `cre workflow build` and `cre workflow deploy`. +- **Environment variable resolution in RPC URLs**: Use `${VAR}` syntax in your `project.yaml` RPC URLs to inject values from environment variables. +- **JSON ABI support in `cre generate-bindings`**: The `cre generate-bindings evm` command now accepts raw JSON ABI files in addition to compiled Hardhat and Foundry artifacts. +- **`.env` support across all commands**: The `.env` file is now respected across all CRE commands, with `.env` values taking precedence over other settings. +- **Bug Fix**: Fixed an issue where `cre workflow build` could fail in configurations where `cre workflow simulate` succeeded. + +**Required versions for new networks:** + +- All new mainnets and testnets: CLI v1.5.0+, Go SDK v1.6.0+, TS SDK v1.3.0+ + +**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.4.0...v1.5.0) + +## Go SDK v1.6.0 - March 16, 2026 + +**Go SDK version 1.6.0** updates EVM capabilities to support the new networks added in CLI v1.5.0. + +- **New Networks**: Updated EVM client capabilities to support Celo, Gnosis Chain, Ink, Linea, Mantle, MegaETH, Plasma, Scroll, Sonic, and their associated testnets + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-go/compare/v1.5.0...v1.6.0) + +## TS SDK v1.3.0 - March 16, 2026 + +**TypeScript SDK version 1.3.0** updates EVM capabilities to support the new networks added in CLI v1.5.0. + +- **New Networks**: Updated EVM client capabilities to support new networks added in CLI v1.5.0 + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-typescript/compare/v1.2.0...v1.3.0) + +## CLI v1.4.0 - March 12, 2026 + +**CRE CLI version 1.4.0 is now available.** + +- **CI/CD pipeline support**: `cre workflow build`, `cre workflow upload`, and `cre workflow deploy` can now be run as independent steps for better integration with CI/CD pipelines. +- **MultiHeaders support**: The HTTP capability now supports sending multiple headers per request. + +This release also includes various internal improvements and security fixes. + +**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.3.0...v1.4.0) + +## TS SDK v1.2.0 - March 12, 2026 + +**TypeScript SDK version 1.2.0** includes improvements to the EVM client and developer experience. + +- **`logTriggerConfig` helper**: New helper for configuring EVM log triggers in your workflow +- **Improved error messages**: Added field-level context to `encodeCallMsg` errors for easier debugging + +[See all changes on GitHub](https://github.com/smartcontractkit/cre-sdk-typescript/compare/v1.1.0...v1.2.0) + ## CLI v1.3.0 - March 5, 2026 **CRE CLI version 1.3.0 is now available.** diff --git a/src/content/cre/supported-networks-go.mdx b/src/content/cre/supported-networks-go.mdx index d71b2fde2d8..f51e709373c 100644 --- a/src/content/cre/supported-networks-go.mdx +++ b/src/content/cre/supported-networks-go.mdx @@ -7,7 +7,7 @@ pageId: "supported-networks" metadata: description: "View all EVM networks supported by CRE workflows, including required CLI and SDK versions for each network." datePublished: "2026-02-03" - lastModified: "2026-03-05" + lastModified: "2026-03-17" --- This page lists all EVM-compatible networks supported by CRE workflows, along with the minimum CLI and SDK versions required for each network. @@ -27,11 +27,20 @@ Network support depends on your CLI and SDK versions. The tables below show the | Avalanche | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Base | v1.0.0+ | v1.0.0+ | v1.0.1+ | | BNB Chain | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Celo | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Ethereum | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Gnosis Chain | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Ink | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Jovay | v1.3.0+ | v1.4.0+ | v1.1.3+ | +| Linea | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Mantle | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| MegaETH | v1.5.0+ | v1.6.0+ | v1.3.0+ | | OP Mainnet | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Pharos | v1.3.0+ | v1.4.0+ | v1.1.3+ | +| Plasma | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Polygon | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Scroll | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Sonic | v1.5.0+ | v1.6.0+ | v1.3.0+ | | World Chain | v1.0.11+ | v1.2.0+ | v1.0.9+ | | XLayer | v1.3.0+ | v1.4.0+ | v1.1.3+ | | ZKSync Era | v1.0.6+ | v1.1.3+ | v1.0.7+ | @@ -46,16 +55,24 @@ Network support depends on your CLI and SDK versions. The tables below show the | Avalanche Fuji | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Base Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | BNB Chain Testnet | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Cronos Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Ethereum Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Hyperliquid Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Ink Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Jovay Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Linea Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | +| Mantle Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| MegaETH Testnet 2 | v1.5.0+ | v1.6.0+ | v1.3.0+ | | OP Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Pharos Atlantic Testnet | v1.3.0+ | v1.5.0+ | v1.1.4+ | | Plasma Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Polygon Amoy | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Scroll Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Sonic Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| TAC Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Unichain Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | | World Chain Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | +| XLayer Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | | ZKSync Era Sepolia | v1.0.6+ | v1.1.2+ | v1.0.7+ | ## Forwarder Addresses diff --git a/src/content/cre/supported-networks-ts.mdx b/src/content/cre/supported-networks-ts.mdx index dd0030bb19b..a8e3f7884ec 100644 --- a/src/content/cre/supported-networks-ts.mdx +++ b/src/content/cre/supported-networks-ts.mdx @@ -7,7 +7,7 @@ pageId: "supported-networks" metadata: description: "View all EVM networks supported by CRE workflows, including required CLI and SDK versions for each network." datePublished: "2026-02-03" - lastModified: "2026-03-05" + lastModified: "2026-03-17" --- This page lists all EVM-compatible networks supported by CRE workflows, along with the minimum CLI and SDK versions required for each network. @@ -27,11 +27,20 @@ Network support depends on your CLI and SDK versions. The tables below show the | Avalanche | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Base | v1.0.0+ | v1.0.0+ | v1.0.1+ | | BNB Chain | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Celo | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Ethereum | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Gnosis Chain | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Ink | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Jovay | v1.3.0+ | v1.4.0+ | v1.1.3+ | +| Linea | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Mantle | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| MegaETH | v1.5.0+ | v1.6.0+ | v1.3.0+ | | OP Mainnet | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Pharos | v1.3.0+ | v1.4.0+ | v1.1.3+ | +| Plasma | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Polygon | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Scroll | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Sonic | v1.5.0+ | v1.6.0+ | v1.3.0+ | | World Chain | v1.0.11+ | v1.2.0+ | v1.0.9+ | | XLayer | v1.3.0+ | v1.4.0+ | v1.1.3+ | | ZKSync Era | v1.0.6+ | v1.1.3+ | v1.0.7+ | @@ -46,16 +55,24 @@ Network support depends on your CLI and SDK versions. The tables below show the | Avalanche Fuji | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Base Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | BNB Chain Testnet | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Cronos Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | | Ethereum Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Hyperliquid Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Ink Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Jovay Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Linea Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | +| Mantle Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| MegaETH Testnet 2 | v1.5.0+ | v1.6.0+ | v1.3.0+ | | OP Sepolia | v1.0.0+ | v1.0.0+ | v1.0.1+ | | Pharos Atlantic Testnet | v1.3.0+ | v1.5.0+ | v1.1.4+ | | Plasma Testnet | v1.0.7+ | v1.1.4+ | v1.0.7+ | | Polygon Amoy | v1.0.0+ | v1.0.0+ | v1.0.1+ | +| Scroll Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Sonic Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| TAC Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | +| Unichain Sepolia | v1.5.0+ | v1.6.0+ | v1.3.0+ | | World Chain Sepolia | v1.0.7+ | v1.1.4+ | v1.0.7+ | +| XLayer Testnet | v1.5.0+ | v1.6.0+ | v1.3.0+ | | ZKSync Era Sepolia | v1.0.6+ | v1.1.2+ | v1.0.7+ | ## Forwarder Addresses From bd60e8d8a9aff24842f72feef9c093fa5e23cc22 Mon Sep 17 00:00:00 2001 From: devin distefano Date: Tue, 17 Mar 2026 16:20:58 -0500 Subject: [PATCH 2/2] update content up to 1.5.0, new features, small tickets, other feedback --- src/content/cre/capabilities/http.mdx | 6 +- .../cli-installation/macos-linux.mdx | 14 +- .../cli-installation/windows.mdx | 14 +- .../guides/operations/deploying-workflows.mdx | 85 +++- .../generating-bindings-go.mdx | 11 +- .../generating-bindings-ts.mdx | 11 +- .../using-http-client/get-request-go.mdx | 53 ++- .../using-http-client/get-request-ts.mdx | 44 +- .../workflow/using-http-client/index.mdx | 7 +- .../cre/guides/workflow/using-randomness.mdx | 9 +- src/content/cre/llms-full-go.txt | 403 ++++++++++++++++-- src/content/cre/llms-full-ts.txt | 364 ++++++++++++++-- src/content/cre/reference/cli/index.mdx | 10 +- .../cre/reference/cli/project-setup-go.mdx | 21 +- src/content/cre/reference/cli/utilities.mdx | 6 +- src/content/cre/reference/cli/workflow.mdx | 136 +++++- .../reference/project-configuration-go.mdx | 18 +- .../reference/project-configuration-ts.mdx | 18 +- src/content/cre/release-notes.mdx | 1 + 19 files changed, 1099 insertions(+), 132 deletions(-) diff --git a/src/content/cre/capabilities/http.mdx b/src/content/cre/capabilities/http.mdx index 8cce404cffb..f2eb14c2bd3 100644 --- a/src/content/cre/capabilities/http.mdx +++ b/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 +## 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. 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 c401caf523d..e34ce84948a 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-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**. 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:** diff --git a/src/content/cre/getting-started/cli-installation/windows.mdx b/src/content/cre/getting-started/cli-installation/windows.mdx index 1a4785fb874..9dcf4878296 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-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**. `0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5`. +## 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 */} + + +{/* prettier-ignore */} + + ## 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. diff --git a/src/content/cre/guides/workflow/using-evm-client/generating-bindings-go.mdx b/src/content/cre/guides/workflow/using-evm-client/generating-bindings-go.mdx index 68980c43d64..c43889b5ad2 100644 --- a/src/content/cre/guides/workflow/using-evm-client/generating-bindings-go.mdx +++ b/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: - `.go` — The main binding for interacting with the contract - `_mock.go` — A mock implementation for testing your workflows without deploying contracts diff --git a/src/content/cre/guides/workflow/using-evm-client/generating-bindings-ts.mdx b/src/content/cre/guides/workflow/using-evm-client/generating-bindings-ts.mdx index c62058a4007..e777fad477a 100644 --- a/src/content/cre/guides/workflow/using-evm-client/generating-bindings-ts.mdx +++ b/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: - `.ts` — The typed binding class with read, write, and event trigger methods. - `_mock.ts` — A mock implementation for testing your workflows without deploying contracts. diff --git a/src/content/cre/guides/workflow/using-http-client/get-request-go.mdx b/src/content/cre/guides/workflow/using-http-client/get-request-go.mdx index 0af264b455c..df049b97177 100644 --- a/src/content/cre/guides/workflow/using-http-client/get-request-go.mdx +++ b/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 */} + diff --git a/src/content/cre/guides/workflow/using-http-client/get-request-ts.mdx b/src/content/cre/guides/workflow/using-http-client/get-request-ts.mdx index c7efc0e4eae..7d95eda861f 100644 --- a/src/content/cre/guides/workflow/using-http-client/get-request-ts.mdx +++ b/src/content/cre/guides/workflow/using-http-client/get-request-ts.mdx @@ -7,7 +7,7 @@ pageId: "guides-workflow-http-get-request" metadata: description: "Fetch data from APIs in TypeScript: 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" @@ -385,3 +385,45 @@ The request object provides several fields to customize your HTTP call. See the - **Body**: Request payload (for POST, PUT, etc.) - **Timeout**: Request timeout as a duration string in seconds (e.g., `"5s"`, `"8s"`) - **Cache settings**: Control response caching behavior + +## Best practices + +### Parse inside the node function, not outside it + +When using a numeric aggregation method such as `median()`, 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: + +```typescript +const fetchData = (nodeRuntime: NodeRuntime): string => { + const response = nodeRuntime.httpClient.sendRequest({ url: config.apiUrl, method: "GET" }).result() + return response.body // ❌ raw string; will fail if aggregation is median +} +``` + +**Correct pattern** — parse inside the node function and return a numeric value: + +```typescript +const fetchData = (nodeRuntime: NodeRuntime): number => { + const response = nodeRuntime.httpClient.sendRequest({ url: config.apiUrl, method: "GET" }).result() + + const data = JSON.parse(response.body) + if (typeof data.price !== "number") { + throw new Error(`Unexpected response body: ${response.body}`) // ✓ throw on bad data + } + return data.price // ✓ return the numeric value +} +``` + +If the endpoint is down or returns an unexpected body, throwing an error (rather than returning the raw string) causes the node to report a failure to the consensus mechanism, which handles node-level failures gracefully. + +{/* prettier-ignore */} + diff --git a/src/content/cre/guides/workflow/using-http-client/index.mdx b/src/content/cre/guides/workflow/using-http-client/index.mdx index 903b8a1a7ff..1d107714a27 100644 --- a/src/content/cre/guides/workflow/using-http-client/index.mdx +++ b/src/content/cre/guides/workflow/using-http-client/index.mdx @@ -6,7 +6,7 @@ isIndex: true metadata: description: "Connect your workflow to external APIs: learn to make GET and POST requests with built-in consensus for secure offchain data." datePublished: "2025-11-04" - lastModified: "2026-02-03" + lastModified: "2026-03-17" --- import { Aside } from "@components" @@ -18,6 +18,11 @@ The CRE SDK provides an HTTP client that allows your workflows to interact with If your HTTP request includes timestamps (e.g., for authentication headers or time-based queries), use `runtime.now()` instead of `Date.now()`. This ensures all nodes use the same timestamp and reach consensus. See [Using Time in Workflows](/cre/guides/workflow/time-in-workflows) for details. +{/* prettier-ignore */} + + These guides will walk you through the common use cases for the HTTP client. ## Guides diff --git a/src/content/cre/guides/workflow/using-randomness.mdx b/src/content/cre/guides/workflow/using-randomness.mdx index 6e378ea4064..613855636d4 100644 --- a/src/content/cre/guides/workflow/using-randomness.mdx +++ b/src/content/cre/guides/workflow/using-randomness.mdx @@ -6,14 +6,15 @@ date: Last Modified metadata: description: "Generate random numbers safely in CRE: use runtime.Rand() to ensure all nodes get the same values and maintain consensus." datePublished: "2025-11-04" - lastModified: "2026-02-05" + lastModified: "2026-03-17" --- import { Aside } from "@components" ## The problem: Why randomness needs special handling @@ -215,7 +216,7 @@ Random generators are tied to the mode they were created in. **Do not** attempt **Is the randomness cryptographically secure?** -The randomness is sourced from the host environment's secure random generator, but the standard Go `*rand.Rand` object is **not** intended for cryptographic purposes. For cryptographic operations, use dedicated crypto libraries. +No. `runtime.Rand()` returns a seeded pseudo-random number generator (Go's `math/rand`). The seed is coordinated by the CRE platform so that all nodes in the DON produce the same sequence — that is what makes consensus possible — but it is not cryptographically secure. Do not use it for key generation, signature nonces, or any security-sensitive purpose. For cryptographic randomness, use Go's `crypto/rand` package. **What happens if I try to use randomness in the wrong mode?** diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index 16be8f793d9..979e92331b4 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -457,6 +457,7 @@ This page provides detailed release notes for CRE. It includes information on ne - **JSON ABI support in `cre generate-bindings`**: The `cre generate-bindings evm` command now accepts raw JSON ABI files in addition to compiled Hardhat and Foundry artifacts. - **`.env` support across all commands**: The `.env` file is now respected across all CRE commands, with `.env` values taking precedence over other settings. - **Bug Fix**: Fixed an issue where `cre workflow build` could fail in configurations where `cre workflow simulate` succeeded. +- **Known issue**: Environment variables passed without a `.env` file present (for example, via a secrets manager like `op run`) may not be bound correctly. Creating an empty `.env` file in your project root (`touch .env`) resolves this. A fix is coming in CLI v1.5.1. **Required versions for new networks:** @@ -858,9 +859,9 @@ These guides explain how to install the Chainlink Developer Platform CLI (also r # Installing the CRE CLI on macOS and Linux Source: https://docs.chain.link/cre/getting-started/cli-installation/macos-linux -Last Updated: 2026-02-26 +Last Updated: 2026-03-17 -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**. ## Installation @@ -891,7 +892,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` + + + These guides will walk you through the common use cases for the HTTP client. ## Guides @@ -4707,11 +4713,12 @@ By following this pattern, you can manage your secrets securely without ever exp # Using Randomness in Workflows Source: https://docs.chain.link/cre/guides/workflow/using-randomness -Last Updated: 2026-02-05 +Last Updated: 2026-03-17 ## The problem: Why randomness needs special handling @@ -4913,7 +4920,7 @@ Random generators are tied to the mode they were created in. **Do not** attempt **Is the randomness cryptographically secure?** -The randomness is sourced from the host environment's secure random generator, but the standard Go `*rand.Rand` object is **not** intended for cryptographic purposes. For cryptographic operations, use dedicated crypto libraries. +No. `runtime.Rand()` returns a seeded pseudo-random number generator (Go's `math/rand`). The seed is coordinated by the CRE platform so that all nodes in the DON produce the same sequence — that is what makes consensus possible — but it is not cryptographically secure. Do not use it for key generation, signature nonces, or any security-sensitive purpose. For cryptographic randomness, use Go's `crypto/rand` package. **What happens if I try to use randomness in the wrong mode?** @@ -5265,7 +5272,7 @@ Despite these limitations, simulation is an essential tool for catching bugs, va # Deploying Workflows Source: https://docs.chain.link/cre/guides/operations/deploying-workflows -Last Updated: 2026-02-12 +Last Updated: 2026-03-17 +## 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. @@ -7640,10 +7734,10 @@ See the [repository README](https://github.com/smartcontractkit/cre-gcp-predicti # CLI Reference Source: https://docs.chain.link/cre/reference/cli -Last Updated: 2026-02-26 +Last Updated: 2026-03-17 -