Prepare 5.1 release.

docs/changes.rst

@@ -1,11 +1,15 @@
 
 .. note:: The buildout versions file for all current versions can be found at https://zopefoundation.github.io/groktoolkit/
 
-6.0 (unreleased)
+5.1 (2024-08-22)
 ----------------
 
 - Drop support for Python 3.7.
 
+- Update to ZTK 3.0.
+
+- Update dependencies to their newest versions.
+
 5.0 (2024-04-23)
 ----------------
 

docs/conf.py

@@ -67,7 +67,7 @@
 # other places throughout the built documents.
 #
 # The short X.Y version.
-version = '5.0'
+version = '6.0'
 # The full version, including alpha/beta/rc tags.
 release = version
 

docs/release.rst

@@ -50,14 +50,13 @@ Creating a release
 ------------------
 
 * Check whether there is a new version of ZTK (Compare
-  https://zopefoundation.github.io/zopetoolkit/ with ``buildout.cfg``)
+  https://zopefoundation.github.io/zopetoolkit/ with ``grok.cfg``)
 
   * If there is newer version: Update to it and run the tests using ``tox -pauto``.
 * Make sure all tests are running successfully.
 * Decide on a version number for the new release, taking https://semver.org/
   into account. (Please note: dropping support for a Python version is
-  considered a major change as it enforces changes for users of GROK toolkit
-  who are using the no longer supported Python version.)
+  **no longer** considered a major change, as it is the usual way of life.)
 * Update ``docs/changes.rst`` with a new entry describing your release or
   update an existing not yet released one. (also set the release date).
 * Update ``version`` and ``copyright`` in ``docs/conf.py`` to the new version

grok.cfg

@@ -4,7 +4,7 @@
 
 [buildout]
 extends =
-  https://zopefoundation.github.io/zopetoolkit/releases/2.2/ztk-versions.cfg
+  https://zopefoundation.github.io/zopetoolkit/releases/3.0/ztk-versions.cfg
   grok-versions.cfg
   grok-sources.cfg