What happened:
go-struct-converter had v0.2.0-rc2, chronicle misidentified the next version as v0.2.1. But more importantly, once v0.2.0 is released, it should contain the full changelog from the prior non-rc release, as for all intents and purposes, that is what users are getting upgraded. It seems ignoring RC tags/releases altogether would address 2 issues at once.
What you expected to happen:
v0.2.0 version is speculated, it has full change log from prior release (in this case v0.1.0)
How to reproduce it (as minimally and precisely as possible):
Release an RC version as a pre-release, e.g.: https://github.com/anchore/go-struct-converter/releases/tag/v0.2.0-rc2, run chronicle.
What happened:
go-struct-converterhadv0.2.0-rc2, chronicle misidentified the next version asv0.2.1. But more importantly, oncev0.2.0is released, it should contain the full changelog from the prior non-rc release, as for all intents and purposes, that is what users are getting upgraded. It seems ignoring RC tags/releases altogether would address 2 issues at once.What you expected to happen:
v0.2.0version is speculated, it has full change log from prior release (in this casev0.1.0)How to reproduce it (as minimally and precisely as possible):
Release an RC version as a
pre-release, e.g.: https://github.com/anchore/go-struct-converter/releases/tag/v0.2.0-rc2, run chronicle.