Commit 9df6fe4
committed
Release job version verification checks for an exact match
The step in the release process that checks whether a release number has
already been used, we are failing while trying to ship v2.2.2 because
v2.2.2rc1 already exists. We need to check for an exact match rather than
doing a simple grep match.
Use `git rev-parse` to do an exact match check for whether a git tag
already exists.1 parent 0d3d43f commit 9df6fe4
1 file changed
+3
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
65 | 65 | | |
66 | 66 | | |
67 | 67 | | |
68 | | - | |
69 | | - | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
70 | 71 | | |
71 | 72 | | |
72 | 73 | | |
| |||
0 commit comments