Skip to content

Fix: update functions sunset date #3784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dev-dist merged 2 commits into from
May 15, 2026
Merged

Fix: update functions sunset date #3784

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7afb1b0
update functions sunset date
dev-dist May 15, 2026
0328d0e
update banner
dev-dist May 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/cre/llms-full-go.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16573,7 +16573,7 @@ Last Updated: 2026-05-11
sidebar to switch to the TypeScript version.
</Aside>

This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **August 12, 2026**.
This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **September 1, 2026**.

The majority of CLF use cases involve fetching off-chain data over HTTP and returning it to a consumer contract. That maps cleanly to a CRE workflow: a trigger (Cron, HTTP, or EVM Log) → an HTTP fetch → a signed report written on-chain to an `IReceiver` consumer.

Expand Down
2 changes: 1 addition & 1 deletion src/content/cre/llms-full-ts.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16500,7 +16500,7 @@ Last Updated: 2026-05-11
sidebar to switch to the Go version.
</Aside>

This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **August 12, 2026**.
This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **September 1, 2026**.

The majority of CLF use cases involve fetching off-chain data over HTTP and returning it to a consumer contract. That maps cleanly to a CRE workflow: a trigger (Cron, HTTP, or EVM Log) → an HTTP fetch → a signed report written on-chain to an `IReceiver` consumer.

Expand Down
2 changes: 1 addition & 1 deletion src/content/cre/reference/clf-migration-go.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ import { Aside } from "@components"
sidebar to switch to the TypeScript version.
</Aside>

This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **August 12, 2026**.
This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **September 1, 2026**.

The majority of CLF use cases involve fetching off-chain data over HTTP and returning it to a consumer contract. That maps cleanly to a CRE workflow: a trigger (Cron, HTTP, or EVM Log) → an HTTP fetch → a signed report written on-chain to an `IReceiver` consumer.

Expand Down
2 changes: 1 addition & 1 deletion src/content/cre/reference/clf-migration-ts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ import { Aside } from "@components"
sidebar to switch to the Go version.
</Aside>

This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **August 12, 2026**.
This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **September 1, 2026**.

The majority of CLF use cases involve fetching off-chain data over HTTP and returning it to a consumer contract. That maps cleanly to a CRE workflow: a trigger (Cron, HTTP, or EVM Log) → an HTTP fetch → a signed report written on-chain to an `IReceiver` consumer.

Expand Down
6 changes: 3 additions & 3 deletions src/features/chainlink-functions/common/cre-callout.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
import { Aside } from "@components"

<Aside type="caution" title="Chainlink Functions is shutting down on August 12, 2026">
Chainlink Functions will stop processing requests after **August 12, 2026**. Migrate your workflows to the
[Chainlink Runtime Environment (CRE)](/cre) before this date to avoid service interruption.
<Aside type="caution" title="Chainlink Functions sunsets Sept 1, 2026 (testnet: June 2, 2026)">
Migrate to the [Chainlink Runtime Environment (CRE)](/cre), which does everything Functions does and [more →](/cre).
Migrate your existing subscriptions before these dates to avoid service disruption.

See the [CLF to CRE migration guide](/cre/reference/clf-migration) for a full concept mapping and code examples.

Expand Down
Loading