If release logic is published borked labels, it should explode the build #186

New Issue

decentral1se · 2021-06-17T07:44:00Z

decentral1se commented

2021-06-17 07:44:00 +00:00

Maybe we can add some additional validation after the release to check that what we have generated in the label looks good? If not, then fail the release run and this way we'll catch failures easier than having to keep an eye out for them.

![image](/attachments/a80d4f52-9e92-43f5-a222-049efc8d8f62) Maybe we can add some additional validation after the release to check that what we have generated in the label looks good? If not, then fail the release run and this way we'll catch failures easier than having to keep an eye out for them.

image.png

15 KiB

decentral1se added this to the Beta release milestone 2021-06-17 07:44:00 +00:00

decentral1se added the

bug

label 2021-06-17 07:44:00 +00:00

decentral1se referenced this issue from a commit

2021-07-06 10:27:35 +00:00

Add label generation checking

decentral1se closed this issue

2021-07-06 10:27:35 +00:00

This repo is archived. You cannot comment on issues.