-
Notifications
You must be signed in to change notification settings - Fork 479
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
Add CI job to check if updateBinary downloads the correct release #659
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more minor tweaks but the overall direction of the PR is good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's still #659 (comment) left to resolve but this is not a major issue so I'm already approving. Fine to merge whether you decide to go with my suggestion there or not.
Before merging please squash the commits a bit. Does not have to be just one but in this case this seems like the best option.It all looks like review fixes and we usually squash those into the original commits they change. |
2b11884
to
b18711d
Compare
6e17949
to
aca5193
Compare
Co-authored-by: Kamil Śliwak <[email protected]>
aca5193
to
1283652
Compare
This PR addresses the comments made here #648 (comment) and is part of the solution for the issue #632.
It adds a CI job to test if the current version is equal to the downloaded release when using the
updateBinary
command.