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: docs/release_management.md
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,16 +8,23 @@ Currently, we made Codex binaries available in three places:
8
8
9
9
# Cutting a Release
10
10
11
-
Currently, choosing the version number for the next release is a manual process. In general, just go to https://github.com/openai/codex/releases/latest and see what the latest release is and increase the minor version by `1`, so if the current release is `0.20.0`, then the next release should be `0.21.0`.
11
+
Run the `codex-rs/scripts/create_github_release` script in the repository to publish a new release. The script will choose the appropriate version number depending on the type of release you are creating.
12
12
13
-
Assuming you are trying to publish `0.21.0`, first you would run:
13
+
To cut a new alpha release from `main` (feel free to cut alphas liberally):
TIP: Add the `--dry-run` flag to report the next version number for the respective release and exit.
19
26
20
-
This will kick off a GitHub Action to build the release, so go to https://github.com/openai/codex/actions/workflows/rust-release.yml to find the corresponding workflow. (Note: we should automate finding the workflow URL with `gh`.)
27
+
Running the publishing script will kick off a GitHub Action to build the release, so go to https://github.com/openai/codex/actions/workflows/rust-release.yml to find the corresponding workflow. (Note: we should automate finding the workflow URL with `gh`.)
21
28
22
29
When the workflow finishes, the GitHub Release is "done," but you still have to consider npm and Homebrew.
0 commit comments