The formats of the published release tags are inconsistent. Some releases are tagged with lower v prefix, some have a capital V, and there is also one which has release as prefix.
Unfortunately, the inconsistent use of tags confuses the concourse github-release-resource, which breaks our automation pipelines. It would be nice if the versioning would follow a certain pattern.
HI @s4heid I am sorry for this incosistent and I also found this issue when I build myself pipeline. The next releases will be tagged with lower v prefix.
The formats of the published release tags are inconsistent. Some releases are tagged with lower
v
prefix, some have a capitalV
, and there is also one which hasrelease
as prefix.Unfortunately, the inconsistent use of tags confuses the concourse github-release-resource, which breaks our automation pipelines. It would be nice if the versioning would follow a certain pattern.