As a first solution we will implement it like this:
A PR must have [semver:FOO] in its merge message.
FOO must be one of {major, minor, patch, skip}. If none is provided then publishing will not run. (same as skip)
When its merged, a workflow in CircleCi will first off all build test and lint.
Then publish workflow will:
bump version with poetry version [major/minor/patch]
then publish to pypi.
Then it will commit the edited file that poetry version [major] updates [pyproject.toml]
Then push that to master branch with a Bumped [major/minor/patch] version, [semver:skip] in commit message.
We need to add continuous delivery(publishing)
As a first solution we will implement it like this:
A PR must have [semver:FOO] in its merge message. FOO must be one of {major, minor, patch, skip}. If none is provided then publishing will not run. (same as skip)
Alternative: Do stuff manually