ci: bumping version to re trigger semantic releases to fix last failed run #5
Conversation
| @@ -4,7 +4,7 @@ build-backend = "hatchling.build" | |||
|
|
|||
| [project] | |||
| name = "algorand-python-testing" | |||
| version = "0.2.2-beta.1" | |||
| version = "0.2.2-beta.2" | |||
There was a problem hiding this comment.
@daniel-makerx i checked on a forked branch that a manual bump in version would result in semantic releases correctly bumping it, however doing a prod release auto sets initial tag to 0.1.0 for some reason and i suspect its due to the fact that latest available tag is suffixed with beta - so technically we got 0 releases so far but not sure why the bot starts the non beta tag from 0.1.0. I'll deal with this one later on but i think we would also need to set a tag according to latest pypi version which isn't a beta one (so that bot wouldn't start the first release from 0.1.0)
There was a problem hiding this comment.
I assume the 0.1.0 release would be because of a feat: conventional commit, so it would start with 0.0.0 find the feat commit and then infer the next version should be 0.1.0
Proposed Changes