@@ -127,20 +127,7 @@ The automated release process is new, and may need some debugging pending more r
127127
128128## Manual Release Process
129129
130- ### 1. Moratorium Check and Obtain Release Lock
131- Run script manually to check for moratorium and obtain release lock.
132-
133- ``` bash
134- # Get the latest SHA from the most recent tag
135- export SHA=" $( git rev-parse $( git tag --sort=-creatordate | head -n 1) ^{commit}) "
136-
137- ./scripts/release/tps-check-lock heroku-applink-python $SHA
138- ```
139-
140- ** Required environment variables**
141- TPS_API_TOKEN - This can be found in team password manager
142-
143- ### 2. Creating a Release Branch
130+ ### 1. Creating a Release Branch
144131
145132Run the draft-release script locally:
146133``` bash
@@ -164,6 +151,20 @@ This method will:
164151Merge pull request release-v$VERSION
165152```
166153
154+ ### 2. Moratorium Check and Obtain Release Lock
155+ Run script manually to check for moratorium and obtain release lock.
156+
157+ ``` bash
158+ # Get the latest SHA from the most recent commit (ensure this commit is the release branch commit to main)
159+ export SHA=" $( git rev-parse origin/main) "
160+
161+ ./scripts/release/tps-check-lock heroku-applink-python $SHA
162+ ```
163+
164+ ** Required environment variables**
165+ TPS_API_TOKEN - This can be found in team password manager
166+
167+
167168### 3. Pushing the tag to Github
168169
169170Once the release branch as been merged into main, you will want to push the signed tag to github.
@@ -184,20 +185,20 @@ git checkout $(git describe --tags --abbrev=0)
184185uv build
185186```
186187
187- ### 4 . Create the Github Release
188+ ### 5 . Create the Github Release
188189
189190``` bash
190191gh release create v$VERSION --generate-notes dist/* .whl dist/* .tar.gz
191192```
192193
193- ### 5 . Publish to PyPI
194+ ### 6 . Publish to PyPI
194195Publish the package to pypi using __ token__ as the username, and the shared team heroku applink manual publishing token as the token.
195196
196197``` bash
197198uv publish
198199```
199200
200- ### 6 . Publish to Change Management
201+ ### 7 . Publish to Change Management
201202Run script manually to publish to change management. Ensure you are using '@salesforce ' email address.
202203
203204``` bash
0 commit comments