File tree Expand file tree Collapse file tree 2 files changed +5
-2
lines changed Expand file tree Collapse file tree 2 files changed +5
-2
lines changed Original file line number Diff line number Diff line change 2
2
This document explains how to publish all OT modules at version x.y.z. Ensure that you’re following semver when choosing a version number.
3
3
4
4
Release Process:
5
+ * [ Checkout a clean repo] ( #checkout-a-clean-repo )
5
6
* [ Create a new branch] ( #create-a-new-branch )
6
7
* [ Open a Pull Request] ( #open-a-pull-request )
7
8
* [ Create a Release] ( #Create-a-Release )
@@ -10,6 +11,8 @@ Release Process:
10
11
* [ Check PyPI] ( #Check-PyPI )
11
12
* [ Troubleshooting] ( #troubleshooting )
12
13
14
+ ## Checkout a clean repo
15
+ - To avoid pushing untracked changes, check out the repo in a new dir
13
16
14
17
## Create a new branch
15
18
The following script does the following:
@@ -74,7 +77,6 @@ git commit -m
74
77
75
78
If for some reason the action failed, do it manually:
76
79
77
- - To avoid pushing untracked changes, check out the repo in a new dir
78
80
- Switch to the release branch (important so we don't publish packages with "dev" versions)
79
81
- Build distributions with ` ./scripts/build.sh `
80
82
- Delete distributions we don't want to push (e.g. ` testutil ` )
Original file line number Diff line number Diff line change 1
- #! /bin/bash -x
1
+ #! /bin/bash
2
2
#
3
3
# This script:
4
4
# 1. parses the version number from the branch name
@@ -73,6 +73,7 @@ function update_changelog() {
73
73
}
74
74
75
75
# create the release branch
76
+ git fetch origin master
76
77
git checkout master
77
78
git reset --hard origin/master
78
79
git checkout -b release/${VERSION}
You can’t perform that action at this time.
0 commit comments