https://pypdf.readthedocs.io/en/stable/dev/releasing.html#how-is-it-done cannot be applied directly when not having direct write access to the main branch. The following comments document what I did and observed:

1. Run python make_release.py

2. Adapt the three generated files. For version 4.1.0, DEV: Fix changelog generator regarding whitespace and handling of "Other" group #2492 had to be mitigated.

3. Create new branch: git checkout -b release_4.1.0

4. Commit the changes: git commit --file RELEASE_COMMIT_MSG.md (Do not use the -e parameter here - this will open the editor and might strip the headings due to the lines starting with # being interpreted as comments.)

5. Verify the commit message: git log

6. Create PR and ask for review

7. The PR title check is failing - needs some adjustments

8. Merge the PR, ensuring that the title only is REL: 4.1.0 and the body contains the correct message.

9. git checkout main && git pull

10. Create the tag: git tag 4.1.0 --file RELEASE_TAG_MSG.md (No -s due to not signing it.)

11. Verify the tag message: git show 4.1.0

    • In my case, I needed git config core.commentChar ";" before creating the tag, as otherwise the # lines would disappear again ...
    • Delete a wrong tag: git tag -d 4.1.0

12. Push the tag: git push --tags - Permissions not sufficient

13. CI should do the remaining steps of creating the release and uploading the release to PyPI