release-tools
release-tools copied to clipboard
Scripts for making (C)Python releases
`str.splitlines()` doesn't preserve trailing lines (unless using `keepends=True`), whereas `str.split('\n')` does. Use the latter form, and assert that modified files end with a blank line in tests. A
Currently test signing isn't supported because you need to have installed the (normally untrusted) root onto the build machine first. This is because the signing tools won't submit files for...
Currently, `.github/workflows/build-release.yml` takes a tag number: https://github.com/python/release-tools/blob/9721c249ff1de736fcf180c4a806ce75372ebf2a/.github/workflows/build-release.yml#L35-L37 Which can be used as the input when triggering a run: https://github.com/python/release-tools/actions/workflows/build-release.yml It would be useful if we could also give a branch...
To avoid issues such as https://github.com/python/pythondotorg/issues/2767 and to remove some manual work, it would be useful to autofill the "Release Notes URL" field for each release (and/or have a default...
We're only bumping the first line ("This is Python version 3.15.0 alpha 0") and for all releases (in `tweak_readme()`). There's some other 3.14->3.15 things we can automate for the first...