1# Zed Releases
 2
 3Zed currently maintains two public releases for macOS:
 4
 5- [Stable](https://zed.dev/download). This is the primary version that people download and use.
 6- [Preview](https://zed.dev/releases/preview), which receives updates a week ahead of stable for early adopters.
 7
 8Typically we cut a new minor release every Wednesday. The current Preview becomes Stable, and the new Preview contains everything on main up until that point.
 9
10If bugs are found and fixed during the week, they may be cherry-picked into the release branches and so new patch versions for preview and stable can become available throughout the week.
11
12## Wednesday release process
13
14You will need write access to the Zed repository to do this:
15
16- Checkout `main` and ensure your working copy is clean.
17- Run `./script/bump-zed-minor-versions` and push the tags
18  and branches as instructed.
19- Wait for the builds to appear at https://github.com/zed-industries/zed/releases (typically takes around 30 minutes)
20- Copy the release notes from the previous Preview release(s) to the current Stable release.
21- Write new release notes for Preview. `/script/get-preview-channel-changes` can help with this, but you'll need to edit and format the output to make it good.
22- Download the artifacts for each release and test that you can run them locally.
23- Publish the releases.
24
25## Patch release process
26
27If your PR fixes a panic or a crash, you should cherry-pick it to the current stable and preview branches. If your PR fixes a regression in recently released code, you should cherry-pick it to the appropriate branch.
28
29You will need write access to the Zed repository to do this:
30
31- Cherry pick them onto the correct branch. You can either do this manually, or leave a comment of the form `/cherry-pick v0.XXX.x` on the PR, and the GitHub bot should do it for you.
32- Run `./script/trigger-release {preview|stable}`
33- Wait for the builds to appear at https://github.com/zed-industries/zed/releases (typically takes around 30 minutes)
34- Add release notes using the `Release notes:` section of each cherry-picked PR.
35- Download the artifacts for each release and test that you can run them locally.
36- Publish the release.
37
38## Nightly release process
39
40- Merge your changes to main
41- Run `./script/trigger-release {nightly}`