-
-
Notifications
You must be signed in to change notification settings - Fork 174
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 #752 from adopted-ember-addons/release-plan
start using release-plan
- Loading branch information
Showing
5 changed files
with
458 additions
and
44 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 |
|---|---|---|
| @@ -0,0 +1,93 @@ | ||
| name: Release Plan Review | ||
| 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 | ||
| permissions: | ||
| contents: write | ||
| pull-requests: write | ||
| 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 | ||
| # We need to download lots of history so that | ||
| # github-changelog can discover what's changed since the last release | ||
| with: | ||
| fetch-depth: 0 | ||
| ref: 'main' | ||
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 18 | ||
|
|
||
| - uses: pnpm/action-setup@v3 | ||
| with: | ||
| version: 8 | ||
| - run: pnpm install --frozen-lockfile | ||
|
|
||
| - name: "Generate Explanation and Prep Changelogs" | ||
| id: explanation | ||
| run: | | ||
| set +e | ||
| pnpm release-plan prepare 2> >(tee -a stderr.log >&2) | ||
| if [ $? -ne 0 ]; then | ||
| echo 'text<<EOF' >> $GITHUB_OUTPUT | ||
| cat stderr.log >> $GITHUB_OUTPUT | ||
| echo 'EOF' >> $GITHUB_OUTPUT | ||
| else | ||
| echo 'text<<EOF' >> $GITHUB_OUTPUT | ||
| jq .description .release-plan.json -r >> $GITHUB_OUTPUT | ||
| echo 'EOF' >> $GITHUB_OUTPUT | ||
| fi | ||
| env: | ||
| GITHUB_AUTH: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| - uses: peter-evans/create-pull-request@v6 | ||
| with: | ||
| commit-message: "Prepare Release using 'release-plan'" | ||
| labels: "internal" | ||
| branch: release-preview | ||
| title: Prepare Release | ||
| body: | | ||
| This PR is a preview of the release that [release-plan](https://github.com/embroider-build/release-plan) has prepared. To release you should just merge this PR 👍 | ||
| ----------------------------------------- | ||
| ${{ steps.explanation.outputs.text }} |
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,62 @@ | ||
| # For every push to the master branch, this checks if the release-plan was | ||
| # updated and if it was it will publish stable npm packages based on the | ||
| # release plan | ||
|
|
||
| name: Publish Stable | ||
|
|
||
| on: | ||
| workflow_dispatch: | ||
| push: | ||
| branches: | ||
| - main | ||
| - master | ||
|
|
||
| concurrency: | ||
| group: publish-${{ github.head_ref || github.ref }} | ||
| 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 result of `success` | ||
| # when the .release-plan.json file was changed on the last commit. This | ||
| # plus the fact that this action only runs on main will be enough of a guard | ||
| - 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 | ||
|
|
||
| publish: | ||
| name: "NPM Publish" | ||
| runs-on: ubuntu-latest | ||
| needs: check-plan | ||
| if: needs.check-plan.outputs.command == 'release' | ||
| permissions: | ||
| contents: write | ||
| pull-requests: write | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 18 | ||
| # This creates an .npmrc that reads the NODE_AUTH_TOKEN environment variable | ||
| registry-url: 'https://registry.npmjs.org' | ||
|
|
||
| - uses: pnpm/action-setup@v3 | ||
| with: | ||
| version: 8 | ||
| - run: pnpm install --frozen-lockfile | ||
| - name: npm publish | ||
| run: pnpm release-plan publish | ||
|
|
||
| env: | ||
| GITHUB_AUTH: ${{ secrets.GITHUB_TOKEN }} | ||
| NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} |
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
Oops, something went wrong.