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
Versioning schema is very confusing. Documentation refers to version 10002-rc2 or 10003-rc1 which is visible on Release page but then downloading a ZIP file via URL gives completely different version v1.1.1-1640627705. We are operating on files in our build scripts, so build scripts refer to different versions than what external documentation is referring to. Going back to verify and double-check what is deployed and what InjectiveLabs is refering to takes extra time to navigate through release pages and finds download URLs.
Why there is unnecessary discrepancy between filenames and your release versioning?
Another one, can you build versioning into the binary also consistently what you are releasing?
injective@injective:/$ injectived version
Version dev (260e526)
Compiled at 20211227-1757 using Go go1.17.2 (amd64)
Per above command output, I have no idea what version this is?
The text was updated successfully, but these errors were encountered:
Versioning schema is very confusing. Documentation refers to version
10002-rc2
or10003-rc1
which is visible on Release page but then downloading a ZIP file via URL gives completely different versionv1.1.1-1640627705
. We are operating on files in our build scripts, so build scripts refer to different versions than what external documentation is referring to. Going back to verify and double-check what is deployed and what InjectiveLabs is refering to takes extra time to navigate through release pages and finds download URLs.Why there is unnecessary discrepancy between filenames and your release versioning?
Another one, can you build versioning into the binary also consistently what you are releasing?
Per above command output, I have no idea what version this is?
The text was updated successfully, but these errors were encountered: