Skip to content

Commit 31111d2

Browse files
committed
chore: prepare for release 6.3.1
Update everything to reflect release version 6.3.1.
1 parent e3884b7 commit 31111d2

File tree

5 files changed

+88
-31
lines changed

5 files changed

+88
-31
lines changed

CHANGELOG.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,50 @@
1+
# 2023-03-18 RELEASE 6.3.1
2+
3+
4+
This is a patch release that includes a singular user facing fix, which is the
5+
inclusion of the `test` directory in the `sdist` release artifact.
6+
7+
## build: explicitly specify `packages` in `pyproject.toml` (#2280)
8+
9+
Commit [334787b](https://github.com/RDFLib/rdflib/commit/334787b), closes [#2280](https://github.com/RDFLib/rdflib/issues/2280).
10+
11+
12+
The default behaviour makes it more of a hassle to republish RDFLib to
13+
a separate package, something which I plan to do for testing purposes
14+
and possibly other reasons.
15+
16+
More changes may follow in a similar vein.
17+
18+
19+
## build: include test in sdist (#2282)
20+
21+
Commit [e3884b7](https://github.com/RDFLib/rdflib/commit/e3884b7), closes [#2282](https://github.com/RDFLib/rdflib/issues/2282).
22+
23+
24+
A perhaps minor regression from earlier versions is that the sdist does not include the test folder, which makes it harder for downstreams to use a single source of truth to build and test a reliable package. This restores the test folder for sdists.
25+
26+
## docs: don't use kroki (#2284)
27+
28+
Commit [bea782f](https://github.com/RDFLib/rdflib/commit/bea782f), closes [#2284](https://github.com/RDFLib/rdflib/issues/2284).
29+
30+
31+
The Kroki server is currently experiencing some issues which breaks our
32+
build, this change eliminates the use of Kroki in favour of directly
33+
using the generated SVG images which is checked into git alongside the
34+
PlantUML sources.
35+
36+
I also added a task to the Taskfile to re-generate the SVG images from
37+
the PlantUML sources by calling docker.
38+
39+
## chore: post 6.3.0 release tasks (#2279)
40+
41+
Commit [7beae75](https://github.com/RDFLib/rdflib/commit/7beae75), closes [#2279](https://github.com/RDFLib/rdflib/issues/2279).
42+
43+
44+
Bump version of RDFLib and update docker `requirements.{in,txt}`.
45+
46+
47+
148
# 2023-03-16 RELEASE 6.3.0
249

350
This is a minor release that includes bug fixes and features.

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The stable release of RDFLib may be installed with Python's package management t
6161
Alternatively manually download the package from the Python Package
6262
Index (PyPI) at https://pypi.python.org/pypi/rdflib
6363

64-
The current version of RDFLib is 6.3.0, see the ``CHANGELOG.md`` file for what's new in this release.
64+
The current version of RDFLib is 6.3.1, see the ``CHANGELOG.md`` file for what's new in this release.
6565

6666
### Installation of the current main branch (for developers)
6767

docs/developers.rst

Lines changed: 38 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -358,43 +358,53 @@ RDFLib 5.0.0 maintained compatibility with Python versions 2.7, 3.4, 3.5, 3.6, 3
358358
Releasing
359359
---------
360360

361-
Set to-be-released version number in :file:`rdflib/__init__.py` and
362-
:file:`README.md`. Check date in :file:`LICENSE`.
361+
Create a release-preparation pull request with the following changes:
363362

364-
Add :file:`CHANGELOG.md` entry.
363+
* Updated copyright year in the ``LICENSE`` file.
364+
* Updated copyright year in the ``docs/conf.py`` file.
365+
* Updated main branch version and current version in the ``README.md`` file. The
366+
main branch version should be the next major version with an ``a0`` suffix to
367+
indicate it is alpha 0. When releasing 6.3.1, the main branch version in the
368+
README should be 6.4.0a0.
369+
* Updated version in the ``pyproject.toml`` file.
370+
* Updated ``__date__`` in the ``rdflib/__init__.py`` file.
371+
* Accurate ``CHANGELOG.md`` entry for the release.
365372

366-
Commit this change. It's preferable make the release tag via
367-
https://github.com/RDFLib/rdflib/releases/new ::
368-
Our Tag versions aren't started with 'v', so just use a plain 5.0.0 like
369-
version. Release title is like "RDFLib 5.0.0", the description a copy of your
370-
:file:`CHANGELOG.md` entry.
371-
This gives us a nice release page like this::
372-
https://github.com/RDFLib/rdflib/releases/tag/4.2.2
373+
Once the PR is merged, switch to the main branch, build the release and upload it to PyPI:
373374

374-
If for whatever reason you don't want to take this approach, the old one is::
375-
376-
Tagging the release commit with::
377-
378-
git tag -am 'tagged version' X.X.X
375+
.. code-block:: bash
376+
377+
# Clean up any previous builds
378+
\rm -vf dist/*
379379
380-
When pushing, remember to do::
380+
# Build artifacts
381+
poetry build
381382
382-
git push --tags
383+
# Check that the built wheel works correctly:
384+
pipx run --spec "$(readlink -f dist/rdflib*.whl)" rdfpipe --version
383385
386+
# Publish to PyPI
387+
poetry publish
388+
384389
385-
No matter how you create the release tag, remember to upload tarball to pypi with::
390+
Once this is done, create a release tag from `GitHub releases
391+
<https://github.com/RDFLib/rdflib/releases/new>`_. For a release of version
392+
6.3.1 the tag should be ``6.3.1`` (without a "v" prefix), and the release title
393+
should be "RDFLib 6.3.1". The release notes for the latest version be added to
394+
the release description. The artifacts built with ``poetry build`` should be
395+
uploaded to the release as release artifacts.
386396

387-
rm -r dist/X.X.X[.-]* # delete all previous builds for this release, just in case
397+
The resulting release will be available at https://github.com/RDFLib/rdflib/releases/tag/6.3.1
388398

389-
rm -r build
390-
python setup.py sdist
391-
python setup.py bdist_wheel
392-
ls dist
399+
Once this is done announce the release at the following locations:
393400

394-
# upload with twine
395-
# WARNING: once uploaded can never be modified, only deleted!
396-
twine upload dist/rdflib-X.X.X[.-]*
401+
* Twitter: Just make a tweet from your own account linking to the latest release.
402+
* RDFLib mailing list.
403+
* RDFLib Gitter / matrix.org chat room.
397404

398-
Set new dev version number in the above locations, i.e. next release ``-dev``: ``5.0.1-dev`` and commit again.
405+
Once this is all done, create another post-release pull request with the following changes:
399406

400-
Tweet, email mailing list and inform members in the chat.
407+
* Set the just released version in ``docker/latest/requirements.in`` and run
408+
``task docker:prepare`` to update the ``docker/latest/requirements.txt`` file.
409+
* Set the version in the ``pyproject.toml`` file to the next minor release with
410+
a ``a0`` suffix to indicate alpha 0.

pyproject.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[tool.poetry]
22
name = "rdflib"
3-
version = "6.4.0a0"
3+
version = "6.3.1"
44
description = """RDFLib is a Python library for working with RDF, \
55
a simple yet powerful language for representing information."""
66
authors = ["Daniel 'eikeon' Krech <eikeon@eikeon.com>"]

rdflib/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@
5656
__docformat__ = "restructuredtext en"
5757

5858
__version__: str = _DISTRIBUTION_METADATA["Version"]
59-
__date__ = "2023-03-16"
59+
__date__ = "2023-03-18"
6060

6161
__all__ = [
6262
"URIRef",

0 commit comments

Comments
 (0)