From a7e810f7898a334e12d7df2dff0eaaf014fb79c2 Mon Sep 17 00:00:00 2001 From: devin distefano Date: Fri, 22 May 2026 13:26:24 -0500 Subject: [PATCH 1/4] version bump: cli 1.16.0 --- public/changelog.json | 7 ++ src/config/versions/index.ts | 6 +- .../forwarder-directory-go.mdx | 5 +- .../forwarder-directory-ts.mdx | 5 +- src/content/cre/llms-full-go.txt | 110 +++++++++++++----- src/content/cre/llms-full-ts.txt | 107 ++++++++++++----- src/content/cre/release-notes.mdx | 16 ++- src/content/cre/supported-networks-go.mdx | 51 ++++---- src/content/cre/supported-networks-ts.mdx | 51 ++++---- 9 files changed, 247 insertions(+), 111 deletions(-) diff --git a/public/changelog.json b/public/changelog.json index 47831e2fee5..b51e398876b 100644 --- a/public/changelog.json +++ b/public/changelog.json @@ -919,6 +919,13 @@ "title": "CCIP deprecated on Blast Mainnet", "topic": "CCIP" }, + { + "category": "release", + "date": "2026-05-22", + "description": "CRE CLI version 1.16.0 is now available. This release adds ADI mainnet (`adi-mainnet`) support for local simulation and production deployment. The release also includes bug fixes for workflow deploy checks, non-interactive cron trigger simulation, and platform API reliability.\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.15.0...v1.16.0)", + "title": "CRE CLI v1.16.0 — ADI Mainnet Support", + "topic": "CRE" + }, { "category": "release", "date": "2026-05-14", diff --git a/src/config/versions/index.ts b/src/config/versions/index.ts index 74d264fef65..a9beb29f7fa 100644 --- a/src/config/versions/index.ts +++ b/src/config/versions/index.ts @@ -77,9 +77,11 @@ export const VERSIONS = { }, // CRE CLI Versions — update LATEST here for each new release "cre-cli": { - LATEST: "v1.14.0", - ALL: ["v1.14.0", "v1.13.0", "v1.12.0", "v1.11.0", "v1.10.0", "v1.9.0", "v1.8.0"] as const, + LATEST: "v1.16.0", + ALL: ["v1.16.0", "v1.15.0", "v1.14.0", "v1.13.0", "v1.12.0", "v1.11.0", "v1.10.0", "v1.9.0", "v1.8.0"] as const, RELEASE_DATES: { + "v1.16.0": "2026-05-22T00:00:00Z", + "v1.15.0": "2026-05-14T00:00:00Z", "v1.14.0": "2026-05-08T00:00:00Z", "v1.13.0": "2026-04-30T00:00:00Z", "v1.12.0": "2026-04-23T00:00:00Z", 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 7c5e85a8635..89931e553bc 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 @@ -7,7 +7,7 @@ pageId: "evm-forwarder-directory" metadata: description: "Find forwarder contract addresses for CRE workflows on supported EVM networks." datePublished: "2025-11-04" - lastModified: "2026-05-14" + lastModified: "2026-05-22" --- import { Aside, CopyText } from "@components" @@ -53,6 +53,7 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Network | Chain Name | Mock Forwarder Address | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------ | +| ADI Mainnet | | | | Arbitrum One | | | | Avalanche | | | | Base | | | @@ -117,6 +118,7 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Network | Chain Name | Forwarder Address | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------ | +| ADI Mainnet | | | | Arbitrum One | | | | Avalanche | | | | Base | | | @@ -146,6 +148,7 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | ------------------------------------------------------------------ | | ADI Testnet | | | | Apechain Curtis | | | +| Arc Testnet | | | | Arbitrum Sepolia | | | | Avalanche Fuji | | | | Base 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 028581e6b02..bfcca90c269 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 @@ -7,7 +7,7 @@ pageId: "evm-forwarder-directory" metadata: description: "Find forwarder contract addresses for CRE workflows on supported EVM networks." datePublished: "2025-11-04" - lastModified: "2026-05-14" + lastModified: "2026-05-22" --- import { Aside, CopyText } from "@components" @@ -53,6 +53,7 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Network | Chain Name | Mock Forwarder Address | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------ | +| ADI Mainnet | | | | Arbitrum One | | | | Avalanche | | | | Base | | | @@ -117,6 +118,7 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Network | Chain Name | Forwarder Address | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------ | +| ADI Mainnet | | | | Arbitrum One | | | | Avalanche | | | | Base | | | @@ -146,6 +148,7 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | ------------------------------------------------------------------ | | ADI Testnet | | | | Apechain Curtis | | | +| Arc Testnet | | | | Arbitrum Sepolia | | | | Avalanche Fuji | | | | Base Sepolia | | | diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index 3f7fe33507c..baadc89d17d 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -489,10 +489,24 @@ To help us assist you faster, please include: # Release Notes Source: https://docs.chain.link/cre/release-notes -Last Updated: 2026-05-14 +Last Updated: 2026-05-22 This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations. +## CLI v1.16.0 - May 22, 2026 + +**CRE CLI version 1.16.0 is now available.** + +- **ADI Mainnet support**: ADI mainnet (`adi-mainnet`) is now supported for local simulation and production deployment. See [Supported Networks](/cre/supported-networks). +- **Bug fixes**: Improved workflow deploy checks, non-interactive simulation behavior for cron triggers, and platform API reliability. + +**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.15.0...v1.16.0) + ## CLI v1.15.0 - May 14, 2026 **CRE CLI version 1.15.0 is now available.** @@ -12838,7 +12852,7 @@ New DON timestamps are produced continuously (multiple per second). Treat it as # Making Confidential Requests Source: https://docs.chain.link/cre/guides/workflow/using-confidential-http-client/making-requests-go -Last Updated: 2026-02-10 +Last Updated: 2026-05-22 `confidentialhttp.Client` implements the [Confidential HTTP capability](/cre/capabilities/confidential-http-go). Use it when an outbound call should carry [sensitive credentials or request fields](/cre/capabilities/confidential-http-go#whats-kept-confidential) without assembling them as plain strings in workflow code on every node—see [when to use Confidential vs. regular HTTP](/cre/capabilities/confidential-http-go#when-to-use-confidential-http-vs-regular-http). For those values, use **`VaultDonSecrets`** with **`{{.key}}`** placeholders only; **`runtime.GetSecret()`** in headers or body follows a different trust boundary. @@ -12997,6 +13011,42 @@ Run the simulation: cre workflow simulate ``` +## Request timeout + +The `Timeout` field on the inner `Request` object controls how long the enclave waits for the external API to respond before cancelling the call. It uses the [`google.protobuf.Duration`](https://protobuf.dev/reference/protobuf/google.protobuf/#duration) type. + +**Default and limits:** + +- **Default**: If you omit `Timeout`, a default of **5 seconds** is applied. +- **Maximum**: **10 seconds**. Values above this limit will error. + +If your API routinely takes longer than 5 seconds, set an explicit timeout so the request does not fail unexpectedly. + +Use `durationpb.New()` with a `time.Duration` value on the `Request` field: + +```go +import ( + "time" + + confhttp "github.com/smartcontractkit/cre-sdk-go/capabilities/networking/confidentialhttp" + "google.golang.org/protobuf/types/known/durationpb" +) + +result, err := confHTTPClient.SendRequest(runtime, &confhttp.ConfidentialHTTPRequest{ + Request: &confhttp.HTTPRequest{ + Url: config.URL, + Method: "GET", + MultiHeaders: map[string]*confhttp.HeaderValues{ + "Authorization": {Values: []string{"Basic {{.myApiKey}}"}}, + }, + Timeout: durationpb.New(10 * time.Second), + }, + VaultDonSecrets: []*confhttp.SecretIdentifier{ + {Key: "myApiKey", Owner: config.Owner}, + }, +}).Await() +``` + ## Template syntax for secrets Secrets are injected into request bodies and headers using Go template syntax: `{{.secretName}}`. The placeholder name must match the `Key` in your `VaultDonSecrets` list. @@ -13226,7 +13276,7 @@ For the full list of types and methods available on the Confidential HTTP client # Forwarder Directory Source: https://docs.chain.link/cre/guides/workflow/using-evm-client/forwarder-directory-go -Last Updated: 2026-05-14 +Last Updated: 2026-05-22