Skip to content

Latest commit

 

History

History

changelog

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
2.18.0_2021-05-24
2.18.0_2021-05-24
 
 
2.18.1_2021-07-20
2.18.1_2021-07-20
 
 
2.18.3_2021-10-27
2.18.3_2021-10-27
 
 
2.19.0_2021-11-15
2.19.0_2021-11-15
 
 
2.20.0_2022-02-16
2.20.0_2022-02-16
 
 
2.21.0_2022-06-07
2.21.0_2022-06-07
 
 
2.21.1_2022-06-15
2.21.1_2022-06-15
 
 
2.21.2_2022-09-07
2.21.2_2022-09-07
 
 
3.0.0_2022-12-12
3.0.0_2022-12-12
 
 
3.0.1_2022-12-21
3.0.1_2022-12-21
 
 
3.0.2_2023-01-26
3.0.2_2023-01-26
 
 
3.0.3_2023-02-13
3.0.3_2023-02-13
 
 
3.0.4_2023-03-07
3.0.4_2023-03-07
 
 
4.0.0_2023-05-29
4.0.0_2023-05-29
 
 
4.1.0_2023-08-23
4.1.0_2023-08-23
 
 
4.1.1_2023-10-18
4.1.1_2023-10-18
 
 
4.2.0_2024-02-12
4.2.0_2024-02-12
 
 
4.2.1_2024-02-22
4.2.1_2024-02-22
 
 
4.2.2_2024-05-30
4.2.2_2024-05-30
 
 
4.3.0_2024-07-01
4.3.0_2024-07-01
 
 
4.3.1_2024-07-22
4.3.1_2024-07-22
 
 
4.4.0_2024-09-30
4.4.0_2024-09-30
 
 
4.4.1_2024-10-30
4.4.1_2024-10-30
 
 
unreleased
unreleased
 
 
CHANGELOG.tmpl
CHANGELOG.tmpl
 
 
README.md
README.md
 
 
TEMPLATE.md
TEMPLATE.md
 
 

README.md

Changelog

We are using calens to properly generate a changelog before we are tagging a new release.

Create Changelog items

Create a file according to the template for each feature, fix, change... in the unreleased folder. The file should be named after the # of the merged PR it is describing. The following change types are possible: Bugfix, Change, Enhancement, Security.

Automated Changelog build and commit

  • After each merge to master, the CHANGELOG.md file is automatically updated and the new version will be committed to master while skipping CI.

Create a new Release

  • Copy the files from the unreleased folder into a folder matching the schema 0.3.0_2020-01-10