-
Notifications
You must be signed in to change notification settings - Fork 109
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #604 from embroider-build/update-release-plan
update release-plan
- Loading branch information
Showing
5 changed files
with
621 additions
and
567 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,14 +3,42 @@ on: | |
push: | ||
branches: | ||
- main | ||
- master | ||
pull_request: | ||
types: | ||
- labeled | ||
|
||
concurrency: | ||
group: plan-release # only the latest one of these should ever be running | ||
cancel-in-progress: true | ||
|
||
jobs: | ||
check-plan: | ||
name: 'Check Release Plan' | ||
runs-on: ubuntu-latest | ||
outputs: | ||
command: ${{ steps.check-release.outputs.command }} | ||
|
||
steps: | ||
- uses: actions/checkout@v4 | ||
with: | ||
fetch-depth: 0 | ||
ref: 'main' | ||
# This will only cause the `check-plan` job to have a "command" of `release` | ||
# when the .release-plan.json file was changed on the last commit. | ||
- id: check-release | ||
run: if git diff --name-only HEAD HEAD~1 | grep -w -q ".release-plan.json"; then echo "command=release"; fi >> $GITHUB_OUTPUT | ||
|
||
prepare_release_notes: | ||
name: Prepare Release Notes | ||
runs-on: ubuntu-latest | ||
timeout-minutes: 5 | ||
needs: check-plan | ||
outputs: | ||
explanation: ${{ steps.explanation.outputs.text }} | ||
# only run on push event if plan wasn't updated (don't create a release plan when we're releasing) | ||
# only run on labeled event if the PR has already been merged | ||
if: (github.event_name == 'push' && needs.check-plan.outputs.command != 'release') || (github.event_name == 'pull_request' && github.event.pull_request.merged == true) | ||
|
||
steps: | ||
- uses: actions/checkout@v4 | ||
|
@@ -21,12 +49,16 @@ jobs: | |
- uses: actions/setup-node@v4 | ||
with: | ||
node-version: 16 | ||
|
||
- run: npm ci | ||
- name: "Generate Explanation and Prep Changelogs" | ||
|
||
- name: 'Generate Explanation and Prep Changelogs' | ||
id: explanation | ||
run: | | ||
set -x | ||
npx release-plan prepare | ||
echo 'text<<EOF' >> $GITHUB_OUTPUT | ||
jq .description .release-plan.json -r >> $GITHUB_OUTPUT | ||
echo 'EOF' >> $GITHUB_OUTPUT | ||
|
@@ -36,8 +68,8 @@ jobs: | |
- uses: peter-evans/create-pull-request@v5 | ||
with: | ||
commit-message: "Prepare Release using 'release-plan'" | ||
author: "github-actions[bot] <[email protected]>" | ||
labels: "internal" | ||
author: 'github-actions[bot] <[email protected]>' | ||
labels: 'internal' | ||
branch: release-preview | ||
title: Prepare Release | ||
body: | | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Release Process | ||
|
||
Releases in this repo are mostly automated using [release-plan](https://github.com/embroider-build/release-plan/). Once you label all your PRs correctly (see below) you will have an automatically generated PR that updates your CHANGELOG.md file and a `.release-plan.json` that is used prepare the release once the PR is merged. | ||
|
||
## Preparation | ||
|
||
Since the majority of the actual release process is automated, the remaining tasks before releasing are: | ||
|
||
- correctly labeling **all** pull requests that have been merged since the last release | ||
- updating pull request titles so they make sense to our users | ||
|
||
Some great information on why this is important can be found at [keepachangelog.com](https://keepachangelog.com/en/1.1.0/), but the overall | ||
guiding principle here is that changelogs are for humans, not machines. | ||
|
||
When reviewing merged PR's the labels to be used are: | ||
|
||
* breaking - Used when the PR is considered a breaking change. | ||
* enhancement - Used when the PR adds a new feature or enhancement. | ||
* bug - Used when the PR fixes a bug included in a previous release. | ||
* documentation - Used when the PR adds or updates documentation. | ||
* internal - Internal changes or things that don't fit in any other category. | ||
|
||
**Note:** `release-plan` requires that **all** PRs are labeled. If a PR doesn't fit in a category it's fine to label it as `internal` | ||
|
||
## Release | ||
|
||
Once the prep work is completed, the actual release is straight forward: you just need to merge the open [Plan Release](https://github.com/embroider-build/ember-auto-import/pulls?q=is%3Apr+is%3Aopen+%22Prepare+Release%22+in%3Atitle) PR |
Oops, something went wrong.