-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Bug] Auto detect framework upgrade's dependency on a specific binary version #6281
Comments
This is much harder to do because we don't have a way to publicly query the binary version a node is running on. Plus it could vary from node to node so it's hard to get some real signal on top of public tool. |
This issue is stale because it has been open 45 days with no activity. Remove the |
This issue is stale because it has been open 45 days with no activity. Remove the |
🐛 Bug
Changes in Move that require a framework upgrade might have dependencies on changes in the VM. We want to automate discovering this dependency if possible to avoid cases where we do a framework upgrade without the VM changes being rolled out first.
Having tests that cover specific features might help but in many cases, these tests might be skipped or don't have coverage of all possible cases. It'd still be helpful to have auto detection when we attempt a release where there's a dependency on a binary that is not yet released to sufficient validator nodes.
The text was updated successfully, but these errors were encountered: