From b5f0ff226b51b77cb7aa342d3084ac785790c994 Mon Sep 17 00:00:00 2001 From: Leonardo Cavallucci Date: Fri, 22 Sep 2023 13:01:34 +0200 Subject: [PATCH] Migrate to bump-my-version (#760) --- .bumpversion.cfg | 25 ------- CONTRIBUTING.rst | 165 +------------------------------------------- changes/759.feature | 1 + pyproject.toml | 32 +++++++++ tasks.py | 9 ++- 5 files changed, 40 insertions(+), 192 deletions(-) delete mode 100644 .bumpversion.cfg create mode 100644 changes/759.feature diff --git a/.bumpversion.cfg b/.bumpversion.cfg deleted file mode 100644 index 34acf275..00000000 --- a/.bumpversion.cfg +++ /dev/null @@ -1,25 +0,0 @@ -[bumpversion] -current_version = 2.0.3.dev1 -parse = (?P\d+)\.(?P\d+)\.(?P\d+)(\.?)(?P[a-z]*)(?P\d*) -serialize = - {major}.{minor}.{patch}.{release}{relver} - {major}.{minor}.{patch} -commit = True -tag = True -sign_tags = True -tag_name = {new_version} -message = Release {new_version} - -[bumpversion:part:release] -optional_value = gamma -values = - dev - a - b - rc - gamma - -[bumpversion:part:relver] -first_value = 1 - -[bumpversion:file:djangocms_blog/__init__.py] diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 666e4edf..bc866419 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -5,167 +5,4 @@ Contributing Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. -You can contribute in many ways: - -Types of Contributions -********************** - -Report Bugs -=========== - -Report bugs at https://github.com/nephila/djangocms-blog/issues. - -If you are reporting a bug, please include: - -* Your operating system name and version. -* Any details about your local setup that might be helpful in troubleshooting. -* Detailed steps to reproduce the bug. - -Fix Bugs -======== - -Look through the GitHub issues for bugs. Anything tagged with "bug" -is open to whoever wants to implement it. - -Implement Features -================== - -Look through the GitHub issues for features. Anything tagged with "feature" -is open to whoever wants to implement it. - -Write Documentation -=================== - -djangocms-blog could always use more documentation, whether as part of the -official djangocms-blog docs, in docstrings, or even on the web in blog posts, -articles, and such. - -Submit Feedback -=============== - -The best way to send feedback is to file an issue at https://github.com/nephila/djangocms-blog/issues. - -If you are proposing a feature: - -* Explain in detail how it would work. -* Keep the scope as narrow as possible, to make it easier to implement. -* Remember that this is a volunteer-driven project, and that contributions - are welcome :) - -************ -Get Started! -************ - -Ready to contribute? Here's how to set up ``djangocms-blog`` for local development. - -1. Fork the ``djangocms-blog`` repo on GitHub. -2. Clone your fork locally:: - - $ git clone git@github.com:your_name_here/djangocms-blog.git - -3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper - installed, this is how you set up your fork for local development:: - - $ mkvirtualenv djangocms-blog - $ cd djangocms-blog/ - $ pip install -r requirements-test.txt - $ pip install -e . - -4. Create a branch for local development:: - - $ git checkout -b name-of-your-bugfix-or-feature - -Now you can make your changes locally. - -5. When you're done making changes, check that your changes pass flake8 and the -tests, including testing other Python versions with tox:: - - $ tox - -To get tox, pip install it into your virtualenv. - -6. Commit your changes and push your branch to GitHub:: - - $ git add . - $ git commit -m "Your detailed description of your changes." - $ git push origin name-of-your-bugfix-or-feature - -7. Submit a pull request through the GitHub website. - -Development tips ----------------- - -This project allows you to use `pre-commit `_ to ensure an easy compliance -to the project code styles. - -If you want to use it, install it globally (for example with ``pip3 install --user precommit``, -but check `installation instruction `. -When first cloning the project ensure you install the git hooks by running ``pre-commit install``. - -From now on every commit will be checked against our code style. - -Check also the available tox environments with ``tox -l``: the ones not marked with a python version number are tools -to help you work on the project buy checking / formatting code style, running docs etc. - -Testing tips ----------------- -You can test your project using any specific combination of python, django and django cms. - -For example ``tox -epy37-django30-cms37`` runs the tests on python 3.7, Django 3.0 and django CMS 3.7. - -As the project uses `pytest `_ as test runner, you can pass any pytest option by setting the -``PYTEST_ARGS`` environment variable, usually by prepending to the ``tox`` command. Example:: - - PYTEST_ARGS=" -s tests/test_plugins.py::PluginTest -p no:warnings" tox -epy37-django30-cms37 - - -Pull Request Guidelines -======================= - -Before you submit a pull request, check that it meets these guidelines: - -#. Pull request must be named with the following naming scheme: - - ``/(-)-description`` - - See below for available types. - -#. The pull request should include tests. -#. If the pull request adds functionality, the docs should be updated. - Documentation must be added in ``docs`` directory, and must include usage - information for the end user. - In case of public API method, add extended docstrings with full parameters - description and usage example. -#. Add a changes file in ``changes`` directory describing the contribution in - one line. It will be added automatically to the history file upon release. - File must be named as ``.`` with type being: - - * ``.feature``: For new features. - * ``.bugfix``: For bug fixes. - * ``.doc``: For documentation improvement. - * ``.removal``: For deprecation or removal of public API. - * ``.misc``: For general issues. - - Check `towncrier`_ documentation for more details. - -#. The pull request should work for all python / django / django CMS versions - declared in tox.ini. - Check the CI and make sure that the tests pass for all supported versions. - -Release a version -================= - -#. Update authors file -#. Merge ``develop`` on ``master`` branch -#. Bump release via task: ``inv tag-release (major|minor|patch)`` -#. Update changelog via towncrier: ``towncrier --yes`` -#. Commit changelog with ``git commit --amend`` to merge with bumpversion commit -#. Create tag ``git tag `` -#. Push tag to github -#. Publish the release from the tags page -#. If pipeline succeeds, push ``master`` -#. Merge ``master`` back on ``develop`` -#. Bump developement version via task: ``inv tag-dev -l (major|minor|patch)`` -#. Push ``develop`` - -.. _towncrier: https://pypi.org/project/towncrier/#news-fragments +Please read the instructions `here `_ to start contributing to `djangocms-blog`. diff --git a/changes/759.feature b/changes/759.feature new file mode 100644 index 00000000..7a2f2f73 --- /dev/null +++ b/changes/759.feature @@ -0,0 +1 @@ +Migrate to bump-my-version diff --git a/pyproject.toml b/pyproject.toml index 2658020b..39955bed 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -46,3 +46,35 @@ target-version = "py310" [tool.ruff.mccabe] max-complexity = 10 + +[tool.bumpversion] +allow_dirty = false +commit = true +message = "Release {new_version}" +commit_args = "--no-verify" +tag = false +current_version = "2.0.3.dev1" +parse = """(?x) + (?P[0-9]+) + \\.(?P[0-9]+) + \\.(?P[0-9]+) + (?: + .(?Pdev) + (?:(?P[0-9]+))? + )? +""" +serialize = [ + "{major}.{minor}.{patch}.{release}{relver}", + "{major}.{minor}.{patch}" +] + +[tool.bumpversion.parts.release] +values = [ + "dev", + "" +] +optional_value = "dev" + +[[tool.bumpversion.files]] +filename = "djangocms_blog/__init__.py" +search = "{current_version}" diff --git a/tasks.py b/tasks.py index b4d9fcde..d987d76a 100644 --- a/tasks.py +++ b/tasks.py @@ -111,15 +111,18 @@ def tag_release(c, level, new_version=""): """Tag release version.""" if new_version: new_version = f" --new-version {new_version}" - c.run(f"bumpversion --list {level} --no-tag{new_version}") + c.run(f"bump-my-version bump {level}{new_version}") @task -def tag_dev(c, level="patch", new_version=""): +def tag_dev(c, level, new_version=""): """Tag development version.""" if new_version: new_version = f" --new-version {new_version}" - c.run(f"bumpversion --list {level} --message='Bump develop version [ci skip]' --no-tag{new_version}") + elif level == "release": + c.run("bump-my-version bump patch --no-commit") + level = "relver" + c.run(f"bump-my-version bump {level} --message='Bump develop version [ci skip]' {new_version} --allow-dirty") @task(pre=[clean])