release-tools
release-tools copied to clipboard
python
Scripts for making (C)Python releases
The post-release-branch update of main, where it bumps the Python version number, failed to update a few things, which broke CI (https://github.com/python/cpython/actions/runs/5049581081). At the very least: - configure wasn't regenerated...
BPO | [46077](https://bugs.python.org/issue46077) --- | :--- Nosy | @gpshead, @ydroneaud *Note: these values reflect the state of the issue at the time it was migrated and might not reflect the...
See: https://github.com/python/cpython/issues/77105
Hello all :wave: I recently talked with a friend of mine (@sdelquin) and he has a specific use-case for the ftp directory on his Python seminars and usually the students...
Closes https://github.com/python/release-tools/issues/123
The test phase of the build pipeline is missing: * libmpdec * tkinter It would be nice to copy what's being done on the CPython repository so we can properly...
...when bumping the minor version number. Also fix a minor typo in the area.
PEP 101 talks about manually updating the top-level `README.rst` file to the new version in the final steps (`bump`) of the release process as part of the post-release commit. In...
During the release of 3.12.5: ```pytb 💥 Checking the magic number is up-to-date Traceback (most recent call last): File "./run_release.py", line 1283, in main() File "./run_release.py", line 1279, in main...
Closes #156, this implementation recurses into sub-directories to find all artifacts instead of relying on a pre-defined set.