You can find a list of release notes for Chainlink nodes in the smartcontractkit GitHub repository. Docker images are available in the Chainlink Docker hub.

Changes to v1.4.1

v1.4.1 release notes

• Added a fix to ensure that a failed EthSubscribe does not register (*rpc.ClientSubscription)(nil), which leads to a panic when unsubscribing.
• Fix parsing of float values on job specs.

Changes to v1.4.0

v1.4.0 release notes

• JSON parse tasks in TOML now support a custom separator parameter to substitute for the default ,.
• Slow SQL queries are now logged.
• Updated the block explorer URLs to include FTMScan and SnowTrace.
• Keeper upkeep order can now be shuffled. See KEEPER_TURN_FLAG_ENABLED for details.
• Several fixes. See the release notes for a full list of changes.

Changes to v1.3.0 nodes

v1.3.0 release notes

• Added disk rotating logs. See the Node Logging and LOG_FILE_MAX_SIZE documentation for details.
• Added support for the force flag on the chainlink blocks replay CLI command. If set to true, already consumed logs that would otherwise be skipped will be rebroadcasted.
• Added a version compatibility check when using the CLI to login to a remote node. The bypass-version-check flag skips this check.
• Changed default locking mode to "dual". See the DATABASE_LOCKING_MODE documentation for details.
• Specifying multiple EVM RPC nodes with the same URL is no longer supported. If you see ERROR 0106_evm_node_uniqueness.sql: failed to run SQL migration, you have multiple nodes specified with the same URL and you must fix this before proceeding with the upgrade.
• EIP-1559 is now enabled by default on the Ethereum Mainnet. See the EVM_EIP1559_DYNAMIC_FEES documentation for details.
• Added new Keepers feature that includes gas price in calls to checkUpkeep(). To enable the feature, set KEEPER_CHECK_UPKEEP_GAS_PRICE_FEATURE_ENABLED to true. Use this setting only on Polygon networks.

Changes to v1.2.0 nodes

v1.2.0 release notes

Significant changes:

• Added support for the Nethermind Ethereum client.
• Added support for batch sending telemetry to the ingress server to improve performance.
• New environment variables: See the release notes for details.
• Removed the deleteuser CLI command.
• Removed the LOG_TO_DISK environment variable.

See the v1.2.0 release notes for a complete list of changes and fixes.

Changes to v1.1.0 nodes

v1.1.0 release notes

The v1.1.0 release includes several substantial changes to the way you configure and operate Chainlink nodes:

• Legacy environment variables: Legacy environment variables are supported, but they might be removed in future node versions. See the Configuring Chainlink Nodes page to learn how to migrate your nodes away from legacy environment variables and use the API, CLI, or GUI exclusively to administer chains and nodes.
• Full EIP1559 Support: Chainlink nodes include experimental support for submitting transactions using type 0x2 (EIP-1559) envelope. EIP-1559 mode is off by default, but can be enabled either globally or on a per-chain basis.
• New log level added:
  • [crit]: Critical level logs are more severe than [error] and require quick action from the node operator.
• Multichain support (Beta): Chainlink now supports connecting to multiple different EVM chains simultaneously. This is disabled by default. See the v1.1.0 Changelog for details.

With multliple chain support, eth node configuration is stored in the database.

The following environment variables are DEPRECATED:

• ETH_URL
• ETH_HTTP_URL
• ETH_SECONDARY_URLS

Setting ETH_URL will cause Chainlink to automatically overwrite the database records with the given ENV values every time Chainlink boots. This behavior is used mainly to ease the process of upgrading from older versions, and on subsequent runs (once your old settings have been written to the database) it is recommended to unset these ENV vars and use the API commands exclusively to administer chains and nodes.

If you wish to continue using these environment variables (as it used to work in 1.0.0 and below) you must ensure that the following are set:

• ETH_CHAIN_ID (mandatory)
• ETH_URL (mandatory)
• ETH_HTTP_URL (optional)
• ETH_SECONDARY_URLS (optional)

If, instead, you wish to use the API/CLI/GUI to configure your chains and eth nodes (recommended) you must REMOVE the following environment variables:

• ETH_URL
• ETH_HTTP_URL
• ETH_SECONDARY_URLS

This will cause Chainlink to use the database for its node configuration.

NOTE: ETH_CHAIN_ID does not need to be removed, since it now performs the additional duty of specifying the default chain in a multichain environment (if you leave ETH_CHAIN_ID unset, the default chain is simply the "first").

For more information on configuring your node, check the configuration variables in the docs.

Before you upgrade your nodes to v1.1.0, be aware of the following requirements:

• If you are upgrading from a previous version, you MUST first upgrade the node to at least v0.10.15.
• Always take a Database snapshot before you upgrade your Chainlink nodes. You must be able to roll the node back to a previous version in the event of an upgrade failure.

See the v1.1.0 release notes for a complete list of changes and fixes.

Changes to v1.0.0 and v1.0.1 nodes

v1.0.0 release notes
v1.0.1 release notes

Before you upgrade your nodes to v1.0.0 or v1.0.1, be aware of the following requirements:

• If you are upgrading from a previous version, you MUST first upgrade the node to at least v0.10.15.
• Always take a Database snapshot before you upgrade your Chainlink nodes. You must be able to roll the node back to a previous version in the event of an upgrade failure.