Version control issues #212
Replies: 3 comments 1 reply
-
Despite the announcement of v0.2.3, the readme is still showing v0.2.2, VERSION is still v0.2.1, and the docker run below fails with v0.2.3 not found:
While a container built using "latest" in place of "v0.2.3" runs as expected, it's anyone's guess what version of FastKoko is actually running. |
Beta Was this translation helpful? Give feedback.
-
Truth is, I haven't a clue as to what rev is in the latest container, except that it doesn't show some problems seen in earlier editions. The ages in repos suggest little has changed, but there are changes in behavior, so something's changed. I'll continue to use FastKoko, etc. as needed, but I simply have no trust in the current and forthcoming versions as far as knowing what rev has or doesn't have what. So long as things work, "if it ain't broke, don't fix it": I'm not doing further updates. This isn't a build pipeline issue, it's sloppy version control. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Given all the changes discussed and made, I'm not sure what's the true release version. On the code page it's V0.2.2 which is two weeks old. A lot has been changed since then. Clone the repo, and VERSION is three weeks old and contains v0.2.1.
I strongly recommend taking some time to sort out a new release with the stable mods.
Beta Was this translation helpful? Give feedback.
All reactions