Update client prompt on Logs

[ZaineJJ]

On logs receive this

[10-02|12:12:06.780] INFO peer/peer.go:663 beacon attempting to connect with newer version. You may want to update your client {"nodeID": "NodeID-9CkG9MBNavnw7EVSRsuFr7ws9gascDQy3", "beaconVersion": "avalanche/1.8.6"}

[alexpeterson91]

This is not normally an issue, anytime there is any updated release, a lot of times this is just a notice that a node has connected to yours that has a higher version than yours, Avalanche releases a LOT of versions and often will go through 10-20+ minor release versions (we often try and update since most often they're minor edge security patches), and release notes upstream will shows that it's backwards compatible many many versions for example v1.19.16 is backwards compatible to v1.19.0 with some exceptions depending on the releases we do put out. but also often times only for the previous minor patch, so most of the time its not needed, so we try to release on the protocol schedule and stay ahead of hard forks, we've. not had the best track record with avalanche over the years but theyve had quite a lot of HFs to be honest and we dont have a ton of avalanche users, but i've been trying to maintain avalanche and at least keep it running which it is right now, we just had a hard fork in the last day or so and we had our HF version out just in the knick of time.

So this is a pretty common thing to see in the logs, and unless you have other errors like too old to connect not just you may want to update your client as they happen everytime theres a new release however minor or insignificant and you connect to someone who's updated to it. I have alerts set for hardforks and major versions on many chains, AVAX is one, so expect to see it updated more often, and unless your node is offline, not syncing or in a restart loop or something this is normally just an informational post from the software about a minor patch version that likely just doesn't even affect your node, if it does we review all changelogs whenever a new release is published upstream to check to see if we need to upgrade at all, if we need to change things to make the upgrade work, or any other number of things: most importantly security patches. We release whats needed and dont whats not, so dont worry too much about this message you almost definitely will be seeing it again in the normal course of use. Shouldn't be an issue or concern in the vast majority of cases though.