Hey Alex, Im happy to see you experimenting with these tools Keep in mind that balena-versionist is simply a wrapper around versionist, what it does is to essentially build a versionist.conf.js file on the fly, from your repo.yml configuration. It is opinionated, in the sense the versionist.conf.js that comes out, will follow our own conventions, and may also assume some things that happen through our CI system. This is the problem you are running into right now, if you have a look at the previous step (run balena-versionist) you will see an error reported
Omitting v0.0.2. No valid git reference was found.
If you run into any issues, feel free to let us know on GitHub!
at ChildProcess.exithandler (child_process.js:295:12)
at ChildProcess.emit (events.js:223:5)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Not sure why this is marked as successful, but this means that versionist failed to run. The reason is that the configuration that is generated on the fly, will assume that a github release (or a tag) matching the latest documented version exists (this is done because versionist wants to process all the “new” commits, from the latest one to the latest documented version), and will error out if such reference is not found.
You can manually create a reference to have this work, I would also suggest adding another step after pushing the changes, that adds the tag and pushes that back to origin as well. Keep in mind the tag should use the same version format that appears in the changelog, so in this case it would be
Hope this information is helpful, let me know if you need any more help setting this up.