update keep updated page (#2665)

This commit is contained in:
0xmiel 2021-06-21 22:50:26 +02:00 committed by GitHub
parent b1d5609171
commit fed0a1dc00
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 3 deletions

View File

@ -1,14 +1,14 @@
# Keep Nimbus updated
Make sure you stay on the lookout for any critical updates to Nimbus. This best way to do so is through the **announcements** channel on our [discord](https://discord.com/invite/XRxWahP).
Make sure you stay on the lookout for any critical updates to Nimbus. This best way to do so is through the **announcements** channel on our [discord](https://discord.com/invite/XRxWahP). The Nimbus eth2 releases page can be found [here](https://github.com/status-im/nimbus-eth2/releases/).
> **Note:** If your beacon node is already running, you'll need to disconnect and reconnect for the changes to take effect.
To update to the latest version, either:
To update to the latest version, either download the binary or compile the beacon node release.
## Download the binary
Open the [Nimbus eth2 releases page](https://github.com/status-im/nimbus-eth2/releases/latest) and copy the link for the file that works on your system.
Open the latest [Nimbus eth2 release](https://github.com/status-im/nimbus-eth2/releases/latest) and copy the link for the file that works on your system.
```
wget <insert download link here>
@ -32,4 +32,13 @@ make nimbus_beacon_node
to [rebuild the beacon node](./build.md).
## Urgency guidelines
As of `v1.0.4`, releases are marked with the following tags:
`low-urgency`: update at your own convenience, sometime within our normal update cycle of two weeks
`medium-urgency`: may contain an important stability fix, it is better to update sooner rather than later
`high-urgency`: update as soon as you can, this is a critical update required for Nimbus to function correctly