@vinigfer The error with Changelog Reminder is a current limitation of GitHub Actions. The thing is that it won't run for forked repos unless you enable it to do so. See discussion here.

Workflows don't run on forked repositories by default. You must enable GitHub Actions in the Actions tab of the forked repository.

source: https://help.github.com/en/actions/reference/events-that-trigger-workflows

@camilamaia to differ a "test" version from a "production" version, we could potentially make use of pre-releases, or release candidates.

Before tagging a version that is intended to be published (say 1.5.0), we could create a few others to test on Test PyPi first (1.5.0-rc1, 1.5.0-rc2, ...). Then poetry would be able to publish a new version every time a new RC is created.

Later, we could also have an action that every time we push to master, it'd increment the RC version, commit and push the now updated pyproject.toml file, and publish this new version to Test PyPi. But I would leave this to another issue/PR.

We may also want to check this box when creating a release from GitHub:

Guys, closing this PR since can't change the source branch/repo. Continuing it here: #239

Like this approach of 1.5.0-rc1for Test PyPi versus 1.5.0 for both, and also agree to work on that on a next PR