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: website/content/en/docs/contribution-guidelines/releasing.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,16 +71,9 @@ We will use the `v1.3.0` release version in this example.
71
71
git push -u upstream v1.3.x
72
72
```
73
73
1. Make sure that the list of supported OLM versions stated in the [Overview][overview] section of SDK docs is updated. If a new version of OLM needs to be officially supported, follow the steps in [updating OLM bindata](#updating-olm-bindata) section.
74
-
1. Create and merge a commit that updates the top-level [Makefile] variable `IMAGE_VERSION`
75
-
to the upcoming release tag `v1.3.0`. This variable ensures sample projects have been tagged
76
-
correctly prior to the release commit.
77
-
```sh
78
-
sed -i -E 's/(IMAGE_VERSION = ).+/\1v1\.3\.0/g' Makefile
0 commit comments