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
Then, copy and paste the content of the outputted file into the `Submit a key` section on
90
-
the [MIT PGP Public Key Server][mit-keyserver] or any other public keyserver that forwards
90
+
the [SKS PGP Public Key Server][sks-keyserver] or any other public keyserver that synchronizes
91
91
the key to other public keyservers. Once that is done, other people can download your public
92
92
key and you are ready to sign releases.
93
93
@@ -184,8 +184,6 @@ Commit changes to the following six files:
184
184
185
185
Create a new PR for `release-v1.3.0`.
186
186
187
-
**Note:** CI will not pass for this commit because the new version `v1.3.0` does not exist yet in GitHub.
188
-
189
187
### 2. Create a release tag, binaries, and signatures
190
188
191
189
The top-level `release.sh` script will take care of verifying versions in files described in step 1, and tagging and verifying the tag, as well as building binaries and generating signatures by calling `make release`.
@@ -258,5 +256,5 @@ You've now fully released a new version of the Operator SDK. Good work!
0 commit comments