CRE CLI version 1.15.0 is now available. This release upgrades cre workflow supported-chains to show tenant-specific chains and their mock forwarder addresses (requires cre login or CRE_API_KEY), adds ADI testnet and Celo Sepolia support, and introduces a global --allow-unknown-chains flag to skip chain validation for experimental networks during simulation and deploy. cre workflow hash now auto-derives the workflow owner based on your target registry — on-chain uses CRE_ETH_PRIVATE_KEY or workflow-owner-address, off-chain uses the owner from your login session. The release also includes private registry bug fixes.
Update your CLI by running cre update when prompted, or follow the CLI Installation guide for fresh installations.
CCIP is no longer supported on Mint Mainnet and Fraxtal Testnet.
Chainlink CCIP expands support to new networks:
Newly supported tokens: xSN4, xSN8, xSN9, xSN17, xSN23, xSN34, xSN35, xSN41, xSN44, xSN46, xSN50, xSN51, xSN56, xSN62, xSN64, xSN65, xSN71, xSN93, xSN98, xSN120
Chainlink is deprecating support for the legacy Flux Monitor, Direct Request, and Run Log job types.
After Chainlink Node version 2.47, these job types will no longer be supported. Node operators and developers that continue to rely on them can choose to remain on the last compatible release, but should not expect ongoing development support, including maintenance, bug fixes, security patches, or compatibility with future releases.
Teams using these legacy job types should begin planning to upgrade to the Chainlink Runtime Environment (CRE) as an alternative.
Newly supported tokens: BGBTC
CCIP is no longer supported on Berachain Bartio, Taiko Hekla, Kroma Sepolia, Memento Testnet, Treasure Topaz, and Etherlink Testnet.
Chainlink Data Feeds is available on Ink Mainnet and Ink Sepolia Testnet. View the available price feed information on the Price Feed Addresses page.
Chainlink Node v2.46.0 is now available. See the Release Notes for details.