Describe the bug
I use cocogitto with custom scripts to update also version numbers in our code. While this an additional tag will be created. The bump command will create the MODULE_A-VERSION correctly but instead having this new version in outputs.version, it returns the CUSTOM_TAG-VERSION.
To Reproduce
Create a release and within the release add another commit with a tag like global-1.2.3
Action will bump correctly but returns wrong tag in ${{steps.release.output.version}}, as the cog.sh search for latest git tag.
Expected behavior
The correct new MODULE_A-VERSION is returned like if you call cog get-version --package MODULE_A and combine them in a String like "MODULE_A-${{steps.get-version.output.version}}".
Additional context
None.
Describe the bug
I use cocogitto with custom scripts to update also version numbers in our code. While this an additional tag will be created. The bump command will create the MODULE_A-VERSION correctly but instead having this new version in outputs.version, it returns the CUSTOM_TAG-VERSION.
To Reproduce
Create a release and within the release add another commit with a tag like global-1.2.3
Action will bump correctly but returns wrong tag in ${{steps.release.output.version}}, as the cog.sh search for latest git tag.
Expected behavior
The correct new MODULE_A-VERSION is returned like if you call
cog get-version --package MODULE_Aand combine them in a String like "MODULE_A-${{steps.get-version.output.version}}".Additional context
None.