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/account/cli-login.mdx b/src/content/cre/account/cli-login.mdx index 457d66b822f..54b980f1a33 100644 --- a/src/content/cre/account/cli-login.mdx +++ b/src/content/cre/account/cli-login.mdx @@ -5,7 +5,7 @@ title: "Logging in with the CLI" metadata: description: "Learn how to log in to the CRE CLI: authenticate through your browser, complete 2FA verification, and start using CLI commands." datePublished: "2025-11-04" - lastModified: "2026-03-26" + lastModified: "2026-05-22" --- import { Aside, ClickToZoom } from "@components" @@ -81,4 +81,9 @@ Login completed successfully Your CLI session is authenticated and ready to use. -In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache). +In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`~/.cre/cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache). + +{/* prettier-ignore */} + diff --git a/src/content/cre/account/managing-auth.mdx b/src/content/cre/account/managing-auth.mdx index a9b6a5e8a11..e97fa41f550 100644 --- a/src/content/cre/account/managing-auth.mdx +++ b/src/content/cre/account/managing-auth.mdx @@ -5,7 +5,7 @@ title: "Managing Authentication" metadata: description: "Manage your CRE CLI sessions: check if you're logged in, handle expired sessions, and securely log out when needed." datePublished: "2025-11-04" - lastModified: "2026-03-26" + lastModified: "2026-05-22" --- import { Aside } from "@components" @@ -18,7 +18,7 @@ To authenticate your CLI with your CRE account, use the `cre login` command. Thi For detailed login instructions, see the [Logging in with the CLI](/cre/account/cli-login) guide. -Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache). +Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. Do not commit **`~/.cre/cre.yaml`** to version control. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache). ## API key authentication diff --git a/src/content/cre/guides/workflow/using-confidential-http-client/making-requests-go.mdx b/src/content/cre/guides/workflow/using-confidential-http-client/making-requests-go.mdx index 3bc662f8ba8..7f32dd8357b 100644 --- a/src/content/cre/guides/workflow/using-confidential-http-client/making-requests-go.mdx +++ b/src/content/cre/guides/workflow/using-confidential-http-client/making-requests-go.mdx @@ -7,7 +7,7 @@ pageId: "guides-workflow-confidential-http-making-requests" metadata: description: "Make confidential HTTP requests in Go: learn to use enclave execution, secret injection, and optional response encryption in your workflows." datePublished: "2026-02-10" - lastModified: "2026-02-10" + lastModified: "2026-05-22" --- import { Aside } from "@components" @@ -170,6 +170,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. diff --git a/src/content/cre/guides/workflow/using-confidential-http-client/making-requests-ts.mdx b/src/content/cre/guides/workflow/using-confidential-http-client/making-requests-ts.mdx index dfc714bd00c..37ea3762fe5 100644 --- a/src/content/cre/guides/workflow/using-confidential-http-client/making-requests-ts.mdx +++ b/src/content/cre/guides/workflow/using-confidential-http-client/making-requests-ts.mdx @@ -7,7 +7,7 @@ pageId: "guides-workflow-confidential-http-making-requests" metadata: description: "Make confidential HTTP requests in TypeScript: learn to use enclave execution, secret injection, and optional response encryption in your workflows." datePublished: "2026-02-10" - lastModified: "2026-02-10" + lastModified: "2026-05-22" --- import { Aside } from "@components" @@ -136,6 +136,39 @@ 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 [Protocol Buffers `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. + +Import `Duration` from `@bufbuild/protobuf/wkt` and set `timeout` on the request: + +```typescript +import { Duration } from "@bufbuild/protobuf/wkt" + +const response = confHTTPClient + .sendRequest(runtime, { + request: { + url: runtime.config.url, + method: "GET", + multiHeaders: { + Authorization: { values: ["Basic {{.myApiKey}}"] }, + }, + timeout: { seconds: BigInt(10), nanos: 0 } satisfies Duration, + }, + vaultDonSecrets: [{ key: "myApiKey", owner: runtime.config.owner }], + }) + .result() +``` + +The JSON form is also accepted: `timeout: { seconds: "10", nanos: 0 }` (using `DurationJson`). + ## 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. 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..f30e993600d 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -272,7 +272,7 @@ The mechanism by which a DON comes to a single, reliable, and tamper-proof resul # Service Quotas Source: https://docs.chain.link/cre/service-quotas -Last Updated: 2025-12-18 +Last Updated: 2026-05-22 This page documents the service quotas for Chainlink Runtime Environment (CRE) workflows. @@ -284,6 +284,14 @@ This page documents the service quotas for Chainlink Runtime Environment (CRE) w These quotas apply at the organization level. +### Organization membership + +| Quota | Description | Value | +| ------------- | ------------------------------------------------ | ----- | +| Maximum users | Maximum number of user accounts per organization | 40 | + +This limit can be increased. [Contact us](/cre/support-feedback) to request a higher user cap for your organization. + ### Registry quotas | Registry | Quota | Value | @@ -489,10 +497,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.** @@ -7070,7 +7092,7 @@ Once your account is created: # Logging in with the CLI Source: https://docs.chain.link/cre/account/cli-login -Last Updated: 2026-03-26 +Last Updated: 2026-05-22 To deploy and manage workflows with the CRE CLI, you need to authenticate your CLI session with your CRE account. This guide walks you through the browser-based login process. @@ -7131,13 +7153,18 @@ Login completed successfully Your CLI session is authenticated and ready to use. -In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache). +In the terminal, the CLI may show **“Fetching user context…”** while it downloads your organization’s tenant configuration from the platform. It then writes **`~/.cre/context.yaml`** (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (`~/.cre/cre.yaml`). For details and a sanitized example, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache). + + + --- # Managing Authentication Source: https://docs.chain.link/cre/account/managing-auth -Last Updated: 2026-03-26 +Last Updated: 2026-05-22 This guide covers how to manage your CLI authentication, including browser-based login, API key authentication, checking your status, handling session expiration, and logging out. @@ -7147,7 +7174,7 @@ To authenticate your CLI with your CRE account, use the `cre login` command. Thi For detailed login instructions, see the [Logging in with the CLI](/cre/account/cli-login) guide. -Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache). +Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.yaml`** (cached **tenant context**: registry manifest from the platform, including vault gateway URL and related settings). **`cre logout`** removes both. Do not commit **`~/.cre/cre.yaml`** to version control. For a full description and a sample `context.yaml` shape, see [Tenant context cache](/cre/reference/cli/authentication#tenant-context-cache). ## API key authentication @@ -8373,7 +8400,7 @@ The typical workflow development process uses these commands in sequence: # Authentication Commands Source: https://docs.chain.link/cre/reference/cli/authentication -Last Updated: 2026-05-08 +Last Updated: 2026-05-22 The CRE CLI supports two authentication methods: @@ -8469,8 +8496,8 @@ In a CI/CD pipeline, configure `CRE_API_KEY` as a secret environment variable in After a successful browser login — and when using an API key for commands that load credentials — the CLI stores **tenant context** at **`~/.cre/context.yaml`**. This file comes from the platform’s **`getTenantConfig`** data: a **registry manifest** for your organization so the CLI knows your CRE environment layout (for example vault gateway URL, registries, and allowed secrets auth flows per registry). Values are grouped under your CRE environment name (such as `PRODUCTION`). -