From ca9425571a7cff79dd189043641786c089d24868 Mon Sep 17 00:00:00 2001 From: Mohammed Abu Aboud Date: Mon, 29 Jul 2024 23:14:50 +0200 Subject: [PATCH 1/2] docs: update the pre release steps --- docs/handbook/engineering/pre-releases.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/handbook/engineering/pre-releases.mdx b/docs/handbook/engineering/pre-releases.mdx index 21641e3269..c500fcafed 100644 --- a/docs/handbook/engineering/pre-releases.mdx +++ b/docs/handbook/engineering/pre-releases.mdx @@ -23,6 +23,6 @@ To release a pre-release version of the software, follow these steps: 2. **Increase the version number**: Update the `package.json` file with the new version number. 3. **Open a Pull Request**: Open a pull request from the new branch to the `main` branch. Assign the `pre-release` label to the pull request. 4. **Check the Changelog**: Check the [Activepieces Releases](https://github.com/activepieces/activepieces/releases) page to see if there are any new features or bug fixes that need to be included in the pre-release. Make sure all PRs are labeled correctly so they show in the correct auto-generated changelog. If not, assign the labels and rerun the changelog by removing the "pre-release" label and adding it again to the PR. - -5. **Merge the Pull Request**: Merge the pull request to the `main` branch. -6. **Release the Notes**: Release the notes for the new version. +5. Go to https://github.com/activepieces/activepieces/actions/workflows/release-rc.yml and run it on the release branch to build an image. +6. **Merge the Pull Request**: Merge the pull request to the `main` branch. +7. **Release the Notes**: Release the notes for the new version. From 8c9968915afb0c9a9d02b7b0846b659ca8b851f4 Mon Sep 17 00:00:00 2001 From: Mohammed Abu Aboud Date: Mon, 29 Jul 2024 23:15:29 +0200 Subject: [PATCH 2/2] chore: fix typo --- docs/handbook/engineering/pre-releases.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/handbook/engineering/pre-releases.mdx b/docs/handbook/engineering/pre-releases.mdx index c500fcafed..677e98526a 100644 --- a/docs/handbook/engineering/pre-releases.mdx +++ b/docs/handbook/engineering/pre-releases.mdx @@ -23,6 +23,6 @@ To release a pre-release version of the software, follow these steps: 2. **Increase the version number**: Update the `package.json` file with the new version number. 3. **Open a Pull Request**: Open a pull request from the new branch to the `main` branch. Assign the `pre-release` label to the pull request. 4. **Check the Changelog**: Check the [Activepieces Releases](https://github.com/activepieces/activepieces/releases) page to see if there are any new features or bug fixes that need to be included in the pre-release. Make sure all PRs are labeled correctly so they show in the correct auto-generated changelog. If not, assign the labels and rerun the changelog by removing the "pre-release" label and adding it again to the PR. -5. Go to https://github.com/activepieces/activepieces/actions/workflows/release-rc.yml and run it on the release branch to build an image. +5. Go to https://github.com/activepieces/activepieces/actions/workflows/release-rc.yml and run it on the release branch to build the rc image. 6. **Merge the Pull Request**: Merge the pull request to the `main` branch. 7. **Release the Notes**: Release the notes for the new version.