(CONT-233) - Add version input to gem_release_prep.yml

[jordanbreen28]

Prior to this PR, the version of the gem would need to be manually updated, pushed and merged into main each time before running release_prep.yml.
This PR introduces a "version" input parameter, that can be specified when running the workflow which eliminates the need for the above.

[ekohl]

I think for Puppet modules it can determine what kind of bump it needs to be based on the merged PRs and their labels. Any chance this could be generalized to gems using https://keepachangelog.com compatible changelogs?

[jordanbreen28]

I think for Puppet modules it can determine what kind of bump it needs to be based on the merged PRs and their labels. Any chance this could be generalized to gems using https://keepachangelog.com compatible changelogs?

Thanks @ekohl - pdk is responsible for automatically updating the version number of our modules when running pdk release prep --force.

At the moment PDK isn't compatible with our tools/gems, but I do think that it would be worth exploring our options, and as you say generalise this, in the future :-)

[ekohl]

That would be great, because I can also see Vox Pupuli using it outside of the PDK. Do you happen to know which piece of code is responsible today?

[jordanbreen28]

Apologies @ekohl - Looks like the code responsible in PDK can be found here, PDK seems to work with the github changelog generator in order to compute the next module version. Hope this helps :-)

[ekohl]

Ah, that's much more low level than I thought. I personally had thought about parsing the Markdown and extracting headers. I suppose this also works. It's roughly the approach I had also thought of. I'd also see if I can pass an argument to the generator to mark next version as "Unreleased" instead of some version. That makes parsing a bit more reliable.