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
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -49,8 +49,8 @@ We will update verion numbers according to the following rules:
49
49
50
50
1. Create a PR that updates the version numbers across the codebase ([example](https://github.com/microsoft/autogen/pull/4359))
51
51
2. The docs CI will fail for the PR, but this is expected and will be resolved in the next step
52
-
2. After merging the PR, create and push a tag that corresponds to the new verion. For example, for `0.4.0.dev8`:
53
-
-`git tag 0.4.0.dev8 && git push origin 0.4.0.dev8`
52
+
2. After merging the PR, create and push a tag that corresponds to the new verion. For example, for `0.4.0.dev9`:
53
+
-`git tag 0.4.0.dev9 && git push origin 0.4.0.dev9`
54
54
3. Restart the docs CI by finding the failed [job corresponding to the `push` event](https://github.com/microsoft/autogen/actions/workflows/docs.yml) and restarting all jobs
55
55
4. Run [this](https://github.com/microsoft/autogen/actions/workflows/single-python-package.yml) workflow for each of the packages that need to be released and get an approval for the release for it to run
0 commit comments