You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per discussion, we can be extra careful with the value of the release tag. While there isn't a scenario where this could be null, it could be a non-semantic value.
Why is this needed?
Prevent release workflow from failing or having unintended version published.
Which area does this relate to?
Automation
Solution
We could verify the value follows semantic versioning and is not null. Alternatively, we could also have a manual approval step for when the workflow runs.
We've moved towards a two-person release as all activities are automated now. This gives us enough safety and ensures our messaging is adequate to what we're releasing from more than one point of view.
Summary
As per discussion, we can be extra careful with the value of the release tag. While there isn't a scenario where this could be null, it could be a non-semantic value.
Why is this needed?
Prevent release workflow from failing or having unintended version published.
Which area does this relate to?
Automation
Solution
We could verify the value follows semantic versioning and is not null. Alternatively, we could also have a manual approval step for when the workflow runs.
Acknowledgment
The text was updated successfully, but these errors were encountered: