Skip to content
Snippets Groups Projects
Commit deaaa816 authored by Yorick Peterse's avatar Yorick Peterse
Browse files

Correct tag_format to tag_regex

The field is called "tag_regex", not "tag_format". This lead to some
Omnibus releases not having a changelog, as the API would use the
incorrect starting point for the range of commits to include.
parent 63bccc64
No related branches found
No related tags found
2 merge requests!51Validate shift of Heptapod 0.25 to oldstable series,!44GitLab 14.0
...@@ -42,4 +42,4 @@ ...@@ -42,4 +42,4 @@
# #
# This does not affect the commits included in the range, as no changelog # This does not affect the commits included in the range, as no changelog
# commits are introduced between the tag commits. # commits are introduced between the tag commits.
tag_format: '^(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(\+(?P<pre>rc\d+))?((\.|\+)(?P<meta>ee\.\d+))?$' tag_regex: '^(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(\+(?P<pre>rc\d+))?((\.|\+)(?P<meta>ee\.\d+))?$'
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment