Metadata-Version: 2.3
Name: r3l3453
Version: 0.51.7
Summary: Bump version, tag, commit, release to pypi, bump again, and push.
Author: 5j9
Author-email: 5j9 <5j9@users.noreply.github.com>
License: GNU General Public License v3 (GPLv3)
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
Classifier: Natural Language :: English
Classifier: Topic :: Software Development
Requires-Dist: cyclopts
Requires-Dist: ruff
Requires-Dist: cookiecutter
Requires-Dist: tomlkit
Requires-Dist: uv
Requires-Dist: loguru>=0.7.3
Requires-Python: >=3.12
Project-URL: GitHub, https://github.com/5j9/r3l3453
Description-Content-Type: text/x-rst

`r3l3453` is a small project that I use for semi-automating the release cycle on a few projects of mine. It expects the project to have a very specific configuration that I personally prefer, and therefore may not be suitable for other's projects.

In short what it does is as follows:

* Bump version(s) to a release version according to git log and `Conventional Commits`_.
* Change the title of `Unreleased`_ section in ``CHANGELOG.rst`` to the new version.
* Commit changes.
* Tag the commit.
* Release to PyPI.
* Bump the version again to dev0 version for the next release.
* Push changes to repository.

There is a ``--simulate`` cli option which allows one to see what is going to happen.

.. _Conventional Commits: https://www.conventionalcommits.org/
.. _Unreleased: https://keepachangelog.com/
