Skip to content

Commit

Permalink
feat(release): cleanup release docs & workflows (vercel#3290)
Browse files Browse the repository at this point in the history
Remove old release workflows that are no longer being used now that
we're shipping a Rust binary.

Rename our current workflows and improve docs for clarify.
  • Loading branch information
tknickman authored Jan 20, 2023
1 parent aea9514 commit c8e9758
Show file tree
Hide file tree
Showing 6 changed files with 8 additions and 261 deletions.
93 changes: 0 additions & 93 deletions .github/workflows/build_go_lib.yml

This file was deleted.

160 changes: 0 additions & 160 deletions .github/workflows/release-turborepo.yml

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: Create Release Branch
name: 1. Turborepo Release (release branch)

# TODO: Once we have confidence with the release process, add an
# input to allow automatically kicking off the downstream release.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: Build Go Binary
name: 2. Turborepo Release (go binary)

env:
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: Build Rust Wrapper
name: 3. Turborepo Release (rust binary & publish)

on:
workflow_dispatch:
Expand Down Expand Up @@ -121,7 +121,7 @@ jobs:
uses: dawidd6/action-download-artifact@v2
with:
github_token: ${{secrets.TURBOBOT}}
workflow: build_go_binary.yml
workflow: turborepo-release-step-2.yml
workflow_conclusion: success
branch: ${{ inputs.release_branch }}
path: go-artifacts
Expand Down
8 changes: 4 additions & 4 deletions release.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,10 +50,10 @@ We have a multi step release process for Turborepo right now.

**NOTE**: The steps below _must_ be run serially, in the order specified.

1. Create a release branch by triggering the [Create Release Branch](https://github.com/vercel/turbo/actions/workflows/stage.yml) workflow
1. Create a release branch by triggering the [1. Turborepo Release (release branch)](https://github.com/vercel/turbo/actions/workflows/turborepo-release-step-1.yml) workflow
1. Specify the semver increment using the SemVer Increment field
2. Build the Go Library by triggering the [Build Go Library](https://github.com/vercel/turbo/actions/workflows/build_go_lib.yml) workflow.
1. Build the Go Binary by triggering the [2. Turborepo Release (go binary)](https://github.com/vercel/turbo/actions/workflows/turborepo-release-step-2.yml) workflow.
1. Specify the release branch (example: `staging-1.7.0-canary.1`) in _both_ the "use workflow from", and "Staging branch to release from" fields.
3. Build the Rust Wrapper by triggering the [Build Rust Wrapper](https://github.com/vercel/turbo/actions/workflows/build_rust.yml) workflow.
1. Build the Rust Wrapper by triggering the [3. Turborepo Release (rust binary & publish)](https://github.com/vercel/turbo/actions/workflows/turborepo-release-step-3.yml) workflow.
1. Specify the release branch (example: `staging-1.7.0-canary.1`) in _both_ the "use workflow from", and "Staging branch to release from" fields. (this should match step 2.1 above)
4. Open a PR and merge the release branch back into `main`
1. After publish, open a PR to merge the release branch created in step 1 back into `main`

0 comments on commit c8e9758

Please sign in to comment.