#data gathering for a release pipeline proposes

1 messages · Page 1 of 1 (latest)

grizzled copper
#

@round olive the basic idea is to always have a pull request with a proposed release ready, and when it approved by one or more maintainers, it can directly drop the prepared artifacts onto pypi (aka release decission to release landing on pypi should be less than 10 second)

wraith vine
#

I have something a little bit like that

I use Release Drafter, it creates a draft release like this based on PR titles

it adds Added/Changed/Removed etc based on PR labels I add, and works out the next semver version

when it's time to release, I edit the draft, amend if needed, and click "Publish release"

that also adds the tag and triggers the CI to release to PyPI using Trusted Publishers

grizzled copper
#

@wraith vine i hada look at that earlier - i prefer to use/integrate tools like towncrier, scriv, regendoc and entangled

wraith vine
#

definitely get more control with those tools

grizzled copper
#

@wraith vine also i recently started to use scriv for setuptools_scm and i want to get back to a workflow where i propose a deploy in one click