Skip to content

Prepare a new release - #642

Open
mistotebe wants to merge 1 commit into
python-ldap:3.4from
mistotebe:prep_3.4.8
Open

mistotebe wants to merge 1 commit into
python-ldap:3.4from
mistotebe:prep_3.4.8

Conversation

@mistotebe

Copy link
Copy Markdown
Contributor

No description provided.

@droideck droideck left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!
A couple of things before the merge and a tag:

  • 3.4.6 and 3.4.7 release commits also bumped the version numbers in __version__ files accordingly. So I think we need to do it here too.
  • I also noticed we don't have SECURITY.md, CONTRIBUTING.rst, README.rst, .readthedocs.yaml, Doc/requirements.txt and Misc/python-ldap.supp (the Makefile's valgrind target uses the last one) in MANIFEST.in. And they were released in https://pypi.org/project/python-ldap/3.4.7/#files so I suspect the content just was in your venv when you were doing the build. IMO, worth adding the files explicitly so we can release with python -m build in isolation.

Comment thread CHANGES
@@ -1,5 +1,20 @@
Released 3.4.8 (unreleased)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The date is missing (but maybe you wanted to handle that later at the merge time)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exactly

@mistotebe

Copy link
Copy Markdown
Contributor Author

Looks good! A couple of things before the merge and a tag:

* 3.4.6 and 3.4.7 release commits also bumped the version numbers in `__version__` files  accordingly. So I think we need to do it here too.

True, I forgot we did that in the PR, and it makes more sense so done.

* I also noticed we don't have SECURITY.md, CONTRIBUTING.rst, README.rst, .readthedocs.yaml, Doc/requirements.txt and Misc/python-ldap.supp (the Makefile's valgrind target uses the last one) in **MANIFEST.in**. And they were released in https://pypi.org/project/python-ldap/3.4.7/#files so I suspect the content just was in your venv when you were doing the build. IMO, worth adding the files explicitly so we can release with `python -m build` in isolation.

I didn't realise they would actually land in the source package. OK, done.

@mistotebe
mistotebe requested a review from droideck September 9, 2026 14:19

@droideck droideck left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants