-
Notifications
You must be signed in to change notification settings - Fork 43
Handle protocol version change #659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Un1oR
added a commit
that referenced
this issue
Mar 27, 2025
Un1oR
added a commit
that referenced
this issue
Mar 27, 2025
Un1oR
added a commit
that referenced
this issue
Mar 28, 2025
Un1oR
added a commit
that referenced
this issue
Mar 31, 2025
Un1oR
added a commit
that referenced
this issue
Mar 31, 2025
Un1oR
added a commit
that referenced
this issue
Mar 31, 2025
Un1oR
added a commit
that referenced
this issue
Mar 31, 2025
Un1oR
added a commit
that referenced
this issue
Mar 31, 2025
Un1oR
added a commit
that referenced
this issue
Mar 31, 2025
Un1oR
added a commit
that referenced
this issue
Apr 1, 2025
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 1, 2025
…otocol-version-change [GH-659] Basic protocol version change handling
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now the installation of an archive node does not know how to recognize that the version of the cluster it works with has been incompatibly updated. It is necessary to implement a mechanism for tracking such changes.
The text was updated successfully, but these errors were encountered: