The heading markup will need extending by 2 = to account for the 2 extra characters also I think.
To test this, you might want to commit to False when making the above change. This way you can run bumpversion without it automatically committing so that you can see the result.
To use bumpversion, make sure the requirements are installed, then you decide what kind of release is needed between major, minor or patch. Then the command for a minor release would be;
bumpversion minor
This should change the version number as required, update the changelog by moving the unreleased changes under a new title of the new version with the current date and leaving an unreleased header with nothing under it ready for future changes.
Once it's all looking ok, change commit to True in the bumpversion config ready to make the next release.
If you take a look at the changelog, the 3.0 release didn't have the date in brackets like the previous releases.
So first job, add brackets around that 3.0 release date.
Then the template used by bumpversion will need to be updated so that includes brackets around the date. You can see that line here; https://github.com/django-cms/djangocms-admin-style/blob/master/setup.cfg#L22
The heading markup will need extending by 2
=to account for the 2 extra characters also I think.To test this, you might want to commit to
Falsewhen making the above change. This way you can run bumpversion without it automatically committing so that you can see the result.To use bumpversion, make sure the requirements are installed, then you decide what kind of release is needed between major, minor or patch. Then the command for a minor release would be;
This should change the version number as required, update the changelog by moving the unreleased changes under a new title of the new version with the current date and leaving an unreleased header with nothing under it ready for future changes.
Once it's all looking ok, change
committoTruein the bumpversion config ready to make the next release.