Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/release-process.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Release Process

Release builds are built, signed, notarized, and uploaded to the CDN by [Buildkite](https://buildkite.com/automattic/wp-local-playgrounds).
Release builds are built, signed, notarized, and uploaded to the CDN by [Buildkite](https://buildkite.com/automattic/studio).
Once the release is on the CDN the auto-update process will start downloading the new version.

## Creating a Release
Expand All @@ -11,7 +11,7 @@ These instructions are for creating version 0.1.0-alpha.5, but the steps are the
- Remember to run `npm install` so the version in `package-lock.json` gets updated too.
2. Merge this PR.
3. Make a note of the commit hash of the PR which was just merged into `trunk`, e.g. `a1c70f3a3be5d28922a48f7f298f6152d6001516`
4. Tag this commit with `v0.1.0-alpha.5`.
4. Tag this commit with `v0.1.0-alpha.5`:
1. On your local machine get the latest code: `git checkout trunk && git pull`
2. Create the tag: `git tag v0.1.0-alpha.5 a1c70f3a3be5d28922a48f7f298f6152d6001516`
3. Push the tag to the GitHub repo: `git push origin v0.1.0-alpha.5`
Expand Down