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
An alternative is to push branch and tags separately:
210
-
211
-
$ git push --dry-run origin v0.11.4rc # the branch
212
-
$ git push --dry-run origin v0.11.4rc1 # the tag
213
-
214
-
215
-
Verify that the output corresponds to what you actually wanted to push;
216
-
the correct branch and tag, etc.
217
-
218
-
Remove `--dry-run` when you're happy with the results.
188
+
Use the [Semaphore CI tag-release task](https://semaphore.ci.confluent.io/projects/clients-releases/schedulers/30e1eb9a-91de-43a4-a8de-be4f3de5a3b6) to create tags. Set the parameter accordingly:
189
+
-**PROJECT**: confluent-kafka-python
190
+
-**GIT_REF**: name of your RC branch (`v0.11.4rc` in this tutorial)
191
+
-**TAG_NAME**: name of the new tag (`v0.11.4rc1-dev1`, for example)
192
+
- You can do a test run (set **dry_run** to true) to verify the output before proceeding with the actual tag creation (set **dry_run** to true).
219
193
220
194
221
195
### 5.3. Wait for CI builds to complete
222
196
223
197
Monitor Semaphore CI builds by looking at the *tag* build at
CI jobs are flaky and may fail temporarily. If you see a temporary build error,
227
201
e.g., a timeout, restart the specific job.
@@ -232,11 +206,11 @@ and push a new test tag. Don't forget to delete your previous test tag.
232
206
233
207
### 5.4. Download build artifacts
234
208
235
-
When all CI builds are successful it is time to download the resulting
236
-
artifacts from build's Artifact directory located in another tab in the build:
209
+
When all CI builds are successful it is time to download all the resulting
210
+
artifacts (wheels) from build's `artifacts` directory (located in the `Artifacts` tab in the build).
211
+
212
+
Create a new folder `tools\dl-<tag>` under the repository root, and unzip all artifacts from the downloaded .tgz files there. You should have many artifacts (with .whl suffix) under `tools\dl-<tag>` as we support different operating systems and Python versions.
237
213
238
-
**Note:** The artifacts should be extracted in the folder `tools\dl-<tag>` for
239
-
subsequent steps to work properly.
240
214
241
215
### 5.5. Verify packages
242
216
@@ -253,7 +227,6 @@ the git history to look tidy, remove any test tags, and then go back to
253
227
5.1 and perform the CANDIDATE ITERATION.
254
228
255
229
256
-
257
230
### 5.5.2. Create PR
258
231
259
232
**CANDIDATE ITERATION:**
@@ -365,27 +338,12 @@ Use Preview to check that links work as expected.
365
338
366
339
Create the release.
367
340
368
-
### 6.1. Announcement
369
-
370
-
Write a tweet to announce the new release, something like:
refers to https://confluentinc.atlassian.net/wiki/spaces/TOOLS/pages/2044330444/Create+a+new+version+of+a+documentation+repo#Create-new-release-branches.
346
+
# Update the Python API docs to the latest version: https://github.com/confluentinc/docs-platform.
0 commit comments