CRE no longer supports the T-REX Testnet. T-REX is shutting down its testnet, so the CRE integration has been turned off. Remove T-REX Testnet from your workflow configurations and deploy to a supported network instead. See Supported Networks for the current list.
The following Data Streams are scheduled for deprecation on October 18th, 2026. See Deprecating Data Streams for shutdown dates and the latest status:
The following Data Feeds are scheduled for deprecation. See Feeds Scheduled For Deprecation for shutdown dates and the latest status:
Overnight sessions for tokenized equities are now being smoothed with an exponential moving average. See the tokenized equities documentation to learn more.
CRE CLI version 1.38.0 is now available. This release adds a permanence warning to cre account link-key: once a workflow owner address is linked to an organization, it can never be transferred to or reused in another organization. For more information, see Linking Wallet Keys. It also refreshes your cached user context when it was written by a different CLI version or is older than 24 hours, so new environments and server-side configuration changes appear without a manual cre login.
Update your CLI by running cre update when prompted, or follow the CLI Installation guide for fresh installations.
CRE CLI version 1.37.0 is now available. When you request deploy access with cre account access, the CLI now asks you the purpose of your request.
Update your CLI by running cre update when prompted, or follow the CLI Installation guide for fresh installations.
CRE CLI version 1.36.0 is now available. This release adds detailed and classified execution statuses to cre execution status, cre execution list, and cre workflow get, so runs that finish with capability errors are labeled SUCCESS (completed with errors) and platform-caused failures are flagged with a hint. It also fixes telemetry for commands that don't require login, such as cre generate-bindings, cre workflow build, and cre workflow hash.
Update your CLI by running cre update when prompted, or follow the CLI Installation guide for fresh installations.
Ethereum is upgrading to Glamsterdam during Q4 2026, which changes the gas model of the chain. No action is required unless your workflow sets a gas limit.
Timelines:
Onchain writes to each network may fail for roughly 30 minutes before and after its upgrade. If your workflow sets a gas limit, start testing against Ethereum Sepolia from 6 October 2026 (add gas headroom or unset the gas limit), then update your workflows for Ethereum Mainnet once it is upgraded.
See Network Upgrades for details.
Scheduled (cron-based) updates for the Data Feeds listed below are being sunset. These updates were deprecated in August 2025 and will be fully shut down on or shortly after September 30, 2026.
These feeds are not being deprecated. Only the scheduled updates that request a new round at a fixed time are being removed. Each feed continues to update normally based on its heartbeat and deviation thresholds.
Affected feeds:
Ethereum
Avalanche
Polygon
Arbitrum
No action is required if your integration relies on heartbeat and deviation-threshold updates. If your integration depends on updates at a specific time, review your implementation before September 30, 2026.
Chainlink Data Feeds are now available on Stellar. Data Feeds on Stellar use a single proxy contract that serves every feed, and consumers select a feed by its 32-byte data_id rather than a per-feed contract address.
See Using Data Feeds on Stellar to get started, and Price Feed contract addresses for Stellar for feed IDs and onchain parameters.