Skip to content

Commit 5aaa910

Browse files
authored
Merge pull request #12650 from aslikaya/update_subscribe_link
Update protocol announcement subscription link [Fixes #12627]
2 parents 219df69 + 6717f50 commit 5aaa910

File tree

1 file changed

+1
-1
lines changed
  • public/content/developers/docs/nodes-and-clients/run-a-node

1 file changed

+1
-1
lines changed

public/content/developers/docs/nodes-and-clients/run-a-node/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -433,7 +433,7 @@ Consider creating a service to run your clients automatically on startup. For ex
433433

434434
You need to keep your client software up-to-date with the latest security patches, features, and [EIPs](/eips/). Especially before [hard forks](/history/), make sure you are running the correct client versions.
435435

436-
> Before important network updates, EF publishes a post on its [blog](https://blog.ethereum.org). You can [subscribe to these announcements](https://groups.google.com/a/ethereum.org/g/announcements) to get a notification to your mail when your node needs an update.
436+
> Before important network updates, EF publishes a post on its [blog](https://blog.ethereum.org). You can [subscribe to these announcements](https://blog.ethereum.org/category/protocol#subscribe) to get a notification to your mail when your node needs an update.
437437
438438
Updating clients is very simple. Each client has specific instructions in their documentation, but the process is generally just to download the latest version and restart the client with the new executable. The client should pick up where it left off, but with the updates applied.
439439

0 commit comments

Comments
 (0)