All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
0.10.1 - 2024-10-02
- add support for
Python 3.11
- update
twine
version to5.1.1
or newer to fix KeyError issue - drop release testing with
Python 3.7
- yaml syntax is correct for all workflow files
0.10.0 - 2023-07-08
--validate
argument can be used to validate an existing version file against the latest changelog entryRenderVersionFile
provides acontent
property with the rendered file content after calling therender_file
functionsave_file
parameter ofrender_file
function can be used to only render, but not save content to file- pre-commit hook and config files
0.9.0 - 2022-11-12
- Version of
changelog2version
can be requested with--version
argument, see #22 - Verbosity of internal logger can be set with
-vvvv
asDEBUG
, default level isCRITICAL
, see #22 - Usage example in README for description and version extraction from JSON in console, introduced in 0.7.0, see #20
0.8.0 - 2022-11-11
- Create release candidate tag and release on every pull request build. The release description is the latest changelog content, the release title is the latest changelog version. The release is marked as pre-release, see #18
0.7.0 - 2022-11-11
- Changelog parsed as JSON contains a new key
description
like the PyPi package JSON info, compare tohttps://pypi.org/pypi/changelog2version/json
, with the description/content of the latest change, see #19, relates to #18 - Increase unittest coverage above 95%
- Line breaks are no longer used in this changelog for enumerations
- Issues are referenced as
#123
instead of[#123][ref-issue-123]
to avoid explicit references at the bottom or some other location in the file - Output of
changelog2version
call with--print
but without--debug
option is JSON compatible
0.6.0 - 2022-10-26
- Changelog can be parsed as JSON file with a similar format as the pypi
package JSON info available at
https://pypi.org/pypi/PACKAGENAME/json
, see #16 The new option--output
writes the data in JSON valid format to a file specified file,--print
flag sends the data in JSON valid format tosys.stdout
. In both cases--pretty
flag can be set to output the data with an indentation of 4.
--version_file
argument is optional in order to allow a JSON output only
0.5.0 - 2022-10-20
- Support additional version info file content in python version files by
adding the content given by
--additional_version_info="-rc1234"
to the end of the constructed__version__
content. This will create the following line in aversion.py
file:__version__ = '.'.join(__version_info__) + '-rc1234'
A created package will thereby be named0.5.0rc1234
if the version is0.5.0
, resolve #14
0.4.0 - 2022-08-07
- Property
semver_data
to access extracted VersionInfo from parsed semver line inExtractVersion class
- Header and python version template file
RenderVersionFile class
to render template files with provided content, resolve #5- Examples folder with example C script to demonstrate template rendering on other files than python
--template_file
argument to specify a custom template file for rendering--additional_template_data
to add custom data for the template renderingc
is now a valid and supported file type of--version_file_type
- Documentation extended for new CLI args with more detailed examples
Jinja2
is a required package for this package
parser_valid_file
function returns a resolved path--version_file_type
is no longer case sensitive--version_file
does no longer have to exist- Run GitHub CI unittest workflow also on pull requests
- Functions to update python version files from
update_version.py
script
- Only one job in GitHub CI unittest workflow
- Let GitHub CI unittest workflow fail when Codecov runs into errors during upload
0.3.0 - 2022-08-05
- Regex to extract the first version line from a changelog supports the full feature scope of semantic versioning, resolve #8
- Regex to get the semantic versioning content of a version line supports the full feature scope of semantic versioning, resolve #8
- Testing of this package with
nose2
and coverage report generation withcoverage
including upload to Codecov was moved to new GitHub CI unittest workflow, resolve #11
nose2
andcoverage
steps as well as upload to Codecov removed from GitHub CI release workflow and GitHub CI test workflow
0.2.0 - 2022-08-03
ExtractVersion class
to extract the version line from a changelog file and to parse the semver content from a version line, resolve #4semver_line_regex
andversion_line_regex
args forchangelog2version
to provide custom regular expressions to parse a version line from a changelog and to extract the semver content from a line
- Main parsing code of
update_version script
moved to newExtractVersion class
- Extend usage example in
README
file - Rename test data changelog files
- Split unittest for
ExtractVersion
fromupdate_version
test - Let the pipeline fail is there are flake8 violations
0.1.1 - 2022-07-31
- Update root
README
file with usage instructions - Use
0.0.0
as default in the checked in package version file - Use
release/v1.5
branch ofpypa/gh-action-pypi-publish
in the GitHub CI release workflow file
0.1.0 - 2022-07-31
- This changelog file
.coveragerc
file.flake8
file- Script to create report directories
unittest.cfg
filerequirements.txt
file to setup required packages- Initial
changelog2version
package
.gitignore
file after fork to latest Python gitignore templatesetup.py
file after forktox.ini
file after fork to usenose2
and create coverage report- GitHub CI release workflow updated to run
on
main
branch and update version file before package build - GitHub CI test workflow updated to create
package with updated version file, archive build artifacts, not running on
main
ordevelop
branch and using package extras