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
- Body: ADO Work Item (`AB#<ID>`), summary of features and bug fixes, version update note
94
-
-**Do NOT merge until Step 9**
95
-
96
-
Ask the user for the **ADO Work Item ID** before creating the PR — this is the only input needed.
84
+
-**Do NOT merge until Step 8**
97
85
98
86
---
99
87
100
-
### STEP 3.5 — Draft GitHub Release Notes
88
+
### STEP 2.5 — Draft GitHub Release Notes
101
89
102
-
Do this immediately after creating the GitHub PR. Use the git log and Rust changes collected in Step 3.
90
+
Do this immediately after creating the GitHub PR. Use the git log and Rust changes collected in Step 2.
103
91
104
92
Draft the GitHub Release body using the **Release Notes Format** below. Include Rust-originated changes under `## Enhancements` or `## Bug Fixes`, each suffixed with *(via `mssql_py_core`)*. Present to the user for approval and save the approved draft for Step 9.
105
93
106
94
---
107
95
108
-
### STEP 3.9 — Wait for GitHub PR Approval
96
+
### STEP 2.9 — Wait for GitHub PR Approval
109
97
110
98
> ⚠️ **GATE**: Do NOT proceed to Step 4 until the GitHub release PR has been **approved** by at least one reviewer.
111
99
@@ -115,7 +103,7 @@ Ask the user to confirm the GitHub PR has been approved before continuing.
115
103
116
104
---
117
105
118
-
### STEP 4 — Create ADO Release PR
106
+
### STEP 3 — Create ADO Release PR
119
107
120
108
The agent will cherry-pick the GitHub release commit and push the branch to ADO:
121
109
@@ -136,7 +124,7 @@ Then open ADO and create a PR: title `RELEASE:X.X.X`, source `release/vX.X.X`
136
124
137
125
---
138
126
139
-
### STEP 5 — Wait for ADO Build Pipeline
127
+
### STEP 4 — Wait for ADO Build Pipeline
140
128
141
129
`Build-Release-Package-Pipeline` auto-triggers after the ADO release PR merges to `main`. It builds wheels for:
142
130
-**Windows**: Python 3.10–3.14, x64 + ARM64
@@ -148,17 +136,17 @@ Then open ADO and create a PR: title `RELEASE:X.X.X`, source `release/vX.X.X`
148
136
149
137
---
150
138
151
-
### STEP 6 — Run Dummy Release Pipeline
139
+
### STEP 5 — Run Dummy Release Pipeline
152
140
153
-
Manually trigger `dummy-release-pipeline` in ADO. Select the artifact from the **specific build run from Step 5** (not a later scheduled run — cross-check by trigger timestamp).
141
+
Manually trigger `dummy-release-pipeline` in ADO. Select the artifact from the **specific build run from Step 4** (not a later scheduled run — cross-check by trigger timestamp).
154
142
155
143
This uses Maven ContentType, not PyPI. **Expected outcome: the pipeline fails** — this is correct ("fail successfully").
156
144
157
145
> ⚠️ **MANUAL**: Ask user to confirm the dummy pipeline completed with the expected failure.
158
146
159
147
---
160
148
161
-
### STEP 7 — Verify Artifact Count
149
+
### STEP 6 — Verify Artifact Count
162
150
163
151
In ADO, open the Step 5 build run → **Artifacts** tab. Count must be **exactly 34**.
164
152
@@ -170,7 +158,7 @@ If count ≠ 34: **halt** and investigate before proceeding.
170
158
171
159
---
172
160
173
-
### STEP 8 — Run Official Release Pipeline
161
+
### STEP 7 — Run Official Release Pipeline
174
162
175
163
> ⚠️ **CONFIRM WITH USER**: Ask "Ready to release to PyPI? This will publish to production." before triggering.
176
164
@@ -182,7 +170,7 @@ Once confirmed, verify the release is indexed on PyPI before proceeding: `https:
182
170
183
171
---
184
172
185
-
### STEP 9 — Finalize
173
+
### STEP 8 — Finalize
186
174
187
175
1. Merge the GitHub release PR (`release/X.X.X` → `main`)
188
176
2. Create GitHub Release (tag: `vX.X.X`, title: `Release Notes - Version X.X.X`, body: approved draft from Step 3.5, mark as latest)
@@ -256,22 +244,21 @@ Present this at the start and track progress:
256
244
257
245
```
258
246
Release vX.X.X Checklist:
259
-
[ ] 1. GitHub main CI is green (PR validation, lint-check, devskim)
260
-
[ ] 2. ADO sync PR merged (MANUAL)
261
-
[ ] 3. Git log + Rust changes auto-resolved; presented to user for sanity check
0 commit comments