From 0abcd26de6f1053e442265d6c65919b6193fdd16 Mon Sep 17 00:00:00 2001 From: Crystal Gomes Date: Mon, 24 Jun 2024 19:42:58 -0400 Subject: [PATCH] Announce deprecation date for older upkeeps (#1982) * Announce deprecation date for older upkeeps' ' * correct date * Bump date * Apply suggestions from code review Co-authored-by: Dwight Lyle --------- Co-authored-by: Dwight Lyle --- .../chainlink-automation/concepts/best-practice.mdx | 10 ++++++++-- .../overview/automation-release-notes.mdx | 8 ++++++++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/src/content/chainlink-automation/concepts/best-practice.mdx b/src/content/chainlink-automation/concepts/best-practice.mdx index b60c7399bd3..4fd0bf2d00e 100644 --- a/src/content/chainlink-automation/concepts/best-practice.mdx +++ b/src/content/chainlink-automation/concepts/best-practice.mdx @@ -12,9 +12,15 @@ whatsnext: This guide outlines the best practices when using Chainlink Automation. These best practices are important for using Chainlink Automation securely and reliably when you [create Automation-compatible contracts](/chainlink-automation/guides/compatible-contracts). -### Use Automation 2.0 +### Use the latest version of Chainlink Automation -To get the best reliability and security guarantees for your upkeep we recommend that you use [Automation 2.0](/chainlink-automation/overview/automation-release-notes/#2023-10-02---v20-release). Consider migrating upkeeps to Automation 2.0 if you have upkeeps on an earlier version. +To get the best reliability and security guarantees for your upkeep, use the latest version of Chainlink Automation and [migrate existing upkeeps](/chainlink-automation/guides/migrate-to-v2). Versions earlier than 2.1 are no longer supported, and existing upkeeps on versions earlier than 2.1 will stop being performed on August 29, 2024. + +### Make registry and registrar addresses configurable + +Where your upkeep calls the registry or the registrar, you must make the address configurable so you can migrate your upkeep easily with the one-click migration capability. If you don't make the address configurable, you must redeploy the upkeep for migrations. + +Alternatively, set the forwarder address when your upkeep is deployed and read the registry from the forwarder during your execution to simplify it. ### Use the Forwarder diff --git a/src/content/chainlink-automation/overview/automation-release-notes.mdx b/src/content/chainlink-automation/overview/automation-release-notes.mdx index 68c6a5a5137..326c2ab1267 100644 --- a/src/content/chainlink-automation/overview/automation-release-notes.mdx +++ b/src/content/chainlink-automation/overview/automation-release-notes.mdx @@ -13,6 +13,7 @@ whatsnext: **Chainlink Automation Release Notes** +- [Deprecation of older upkeeps](#2024-06-24---deprecation-of-older-upkeeps) - [Automation on Gnosis](#2024-06-06---automation-on-gnosis) - [Registrar deprecation through v2.0](#2024-06-03---registrar-deprecation-through-v20) - [Automation on Polygon Amoy](#2024-04-23---automation-on-polygon-amoy) @@ -35,6 +36,13 @@ whatsnext: - [Keepers v1.1 launch on Ethereum](#2021-08-05---keepers-v11-launch-on-ethereum) - [Questions](#questions) +## 2024-06-24 - Deprecation of older upkeeps + +Existing upkeeps on versions earlier than v2.1 will stop being performed on August 29, 2024. +[Migrate your older upkeeps to the latest version of Automation](/chainlink-automation/guides/migrate-to-v2). + +Older Automation registrars through v2.0 have [already been deprecated](#2024-06-03---registrar-deprecation-through-v20), so you can't register new upkeeps on versions earlier than v2.1. + ## 2024-06-06 - Automation on Gnosis Chainlink Automation is live on [Gnosis](/chainlink-automation/overview/supported-networks#gnosis-chain-xdai).