From 1f49949e498b90576d2bba466b2e022d971db910 Mon Sep 17 00:00:00 2001 From: Charly Gomez Date: Wed, 19 Mar 2025 16:04:14 +0100 Subject: [PATCH 1/2] add note on alpha to docs --- docs/publishing-a-release.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/publishing-a-release.md b/docs/publishing-a-release.md index 290c6a3076c8..f26b6650d264 100644 --- a/docs/publishing-a-release.md +++ b/docs/publishing-a-release.md @@ -20,9 +20,9 @@ _These steps are only relevant to Sentry employees when preparing and publishing [@getsentry/releases-approvers](https://github.com/orgs/getsentry/teams/release-approvers) to approve the release. a. Once the release is completed, a sync from `master` ->` develop` will be automatically triggered -## Publishing a release for previous majors +## Publishing a release for previous majors or alpha versions -1. Run `yarn changelog` on a previous major branch (e.g. `v8`) and determine what version will be released (we use +1. Run `yarn changelog` on a previous major branch (e.g. `v8` or `9.7.0-alpha`) and determine what version will be released (we use [semver](https://semver.org)) 2. Create a branch, e.g. `changelog-8.45.1`, off a previous major branch (e.g. `v8`) 3. Update `CHANGELOG.md` to add an entry for the next release number and a list of changes since the @@ -32,9 +32,9 @@ _These steps are only relevant to Sentry employees when preparing and publishing (as the commits already exist on this branch). 6. Once the PR is merged, open the [Prepare Release workflow](https://github.com/getsentry/sentry-javascript/actions/workflows/release.yml) and fill in ![run-release-workflow.png](./assets/run-release-workflow.png) - 1. The major branch you want to release for, e.g. `v8` - 2. The version you want to release, e.g. `8.45.1` - 3. The major branch to merge into, e.g. `v8` + 1. The major branch you want to release for, e.g. `v8` or `9.7.0-alpha` + 2. The version you want to release, e.g. `8.45.1` `9.7.0-alpha.1` + 3. The major branch to merge into, e.g. `v8` `9.7.0-alpha` 7. Run the release workflow ## Updating the Changelog From 888fcebbdb3d9cb357fee2f6b1dcf4d852f222f6 Mon Sep 17 00:00:00 2001 From: Charly Gomez Date: Wed, 19 Mar 2025 16:36:15 +0100 Subject: [PATCH 2/2] Update docs/publishing-a-release.md Co-authored-by: Francesco Gringl-Novy --- docs/publishing-a-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/publishing-a-release.md b/docs/publishing-a-release.md index f26b6650d264..1ee26a12de77 100644 --- a/docs/publishing-a-release.md +++ b/docs/publishing-a-release.md @@ -20,7 +20,7 @@ _These steps are only relevant to Sentry employees when preparing and publishing [@getsentry/releases-approvers](https://github.com/orgs/getsentry/teams/release-approvers) to approve the release. a. Once the release is completed, a sync from `master` ->` develop` will be automatically triggered -## Publishing a release for previous majors or alpha versions +## Publishing a release for previous majors or prerelease (alpha, beta) versions 1. Run `yarn changelog` on a previous major branch (e.g. `v8` or `9.7.0-alpha`) and determine what version will be released (we use [semver](https://semver.org))