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
After the prepare-release PR is automatically created and before publishing the release, the release should be validated to ensure stability.
148
+
149
+
### Current Approach
150
+
151
+
The CI pipeline runs e2e tests on every PR. If these tests pass, the release is considered validated and ready to publish.
152
+
153
+
> **Note**: Previously, releases were validated by deploying to staging environments and letting them run for a period before publishing. This approach is no longer in use. If additional validation is needed in the future, consider introducing a manual testing stage or dedicated validation environments.
154
+
155
+
### Validation Checklist
156
+
157
+
Before publishing, ensure:
158
+
159
+
- [ ] All CI checks pass (unit tests, linting, e2e tests)
160
+
- [ ] The prepare-release PR has been reviewed
161
+
- [ ] Release notes accurately reflect the changes
162
+
- [ ] No known critical issues exist in the changes being released
0 commit comments