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
Copy file name to clipboardExpand all lines: RELEASE.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
The release process is also automated in the way any specific commit, from the master branch ideally, can be potentially released, for such it's required the below steps:
6
6
7
7
1. Checkout the commit to be released
8
-
1. Create a tag with the format `v.[0-9]+.[0-9]+.[0-9]+`, i.e.: `v1.0.2`
8
+
1. Create a tag with the format `[0-9]+.[0-9]+.[0-9]+`, i.e.: `1.0.2`
9
9
1. Push the tag to the upstream.
10
10
1. Then, the CI pipeline will trigger a release.
11
11
1. Wait for an email/slack to confirm the release is ready to be approved, it might take roughly 20 minutes.
0 commit comments