You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building from main, the version should include -main or/and GIT_COMMIT_ID-dirty
to make sure users don't get confused which version they are using. Today, if a user
clones the git tree, build the binary and replace ocm-cli in a running system it will look
like they installed/deployed the version 0.1.60 (based on ocm-cli version). Which is not true.
Of course, sysadmins can always check the sha256 from the binary but it's hard to assume steps
for all people/orgs.
When building from main, the version should include
-main
or/andGIT_COMMIT_ID-dirty
to make sure users don't get confused which version they are using. Today, if a user
clones the git tree, build the binary and
replace ocm-cli
in a running system it will looklike they installed/deployed the version
0.1.60
(based onocm-cli version
). Which is not true.Of course, sysadmins can always check the
sha256
from the binary but it's hard to assume stepsfor all people/orgs.
Example:
Cloning
Building
Getting the version from the build
Official release info: https://github.com/openshift-online/ocm-cli/releases/tag/v0.1.60
github-actions released this
Dec 03, 2021
· 18 commits to main since this releasev0.1.60 f16d2ea
The text was updated successfully, but these errors were encountered: