ghost/.github/workflows/release.yml

name: Release
on:
  push:
    tags:
      - '*'
jobs:
  automate:
    runs-on: ubuntu-18.04
    env:
      RELEASE_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
      FORCE_COLOR: 1
    steps:
      - uses: actions/checkout@v2
        with:
          fetch-depth: 0
          submodules: true
      - uses: actions/setup-node@v2
        with:
          node-version: '14'

      - run: yarn
      - run: grunt release --skip-tests
      - run: npm config set //registry.npmjs.org/:_authToken=$NODE_AUTH_TOKEN
      - run: npm publish
      - uses: tryghost/action-ghost-release@master
Automated the release process no issue 2020-03-31 12:25:02 -05:00			`name: Release`
			`on:`
			`push:`
			`tags:`
Updated release Action to run on all tags 2020-04-06 04:49:17 -05:00			`- '*'`
Automated the release process no issue 2020-03-31 12:25:02 -05:00			`jobs:`
			`automate:`
Pinned Ubuntu version for tests & release workflows - we were using `ubuntu-latest`, which is an alias for 18.04, but there's an increasingly likely chance that the default becomes 20.04 soon. - we don't officially support 20.04 yet, so we want to pin to our supported version until we're ready 2020-08-18 07:05:15 -05:00			`runs-on: ubuntu-18.04`
Automated the release process no issue 2020-03-31 12:25:02 -05:00			`env:`
Updated CI release workflow to use built-in token no issue - `RELEASE_TOKEN` is currently a GitHub personal token, but this has some downsides: - if the token ever expires and I'm unaware, it'll break the release process - GitHub Releases say the creator was `daniellockyer` even if someone else actually did the release - this commit switches over to using the built-in `GITHUB_TOKEN`, which is owned by the `github-actions` app and should never expire - aside from that, Ghost releases will be created by the neutral `github-actions` account 2021-07-12 07:05:39 -05:00			`RELEASE_TOKEN: ${{ secrets.GITHUB_TOKEN }}`
Tidied up release GitHub Action no issue 2020-04-07 02:19:17 -05:00			`NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}`
Automated the release process no issue 2020-03-31 12:25:02 -05:00			`FORCE_COLOR: 1`
			`steps:`
			`- uses: actions/checkout@v2`
			`with:`
			`fetch-depth: 0`
			`submodules: true`
Update actions/setup-node action to v2 2021-01-04 00:09:55 -05:00			`- uses: actions/setup-node@v2`
Pinned Node version in CI - The default Node version on GitHub Actions is moving to Node 14 and we want to keep building it on 12 for now, so this commit pins the version to 12.18.0 2020-11-02 03:48:05 -05:00			`with:`
Updated release workflow to use Node 14 no issue - Node 14 is now our recommended version and it's easier if we build Ghost with this version - this also works around the fact that 12.18.0 would no longer build Ghost because we have bumped our minimum 12 version 2021-05-10 14:39:04 -05:00			`node-version: '14'`
Pinned Node version in CI - The default Node version on GitHub Actions is moving to Node 14 and we want to keep building it on 12 for now, so this commit pins the version to 12.18.0 2020-11-02 03:48:05 -05:00
Automated the release process no issue 2020-03-31 12:25:02 -05:00			`- run: yarn`
Switched to custom GitHub Action for a release no issue 2020-04-03 06:44:59 -05:00			`- run: grunt release --skip-tests`
Added npm login to release GitHub Action no issue 2020-04-07 05:59:18 -05:00			`- run: npm config set //registry.npmjs.org/:_authToken=$NODE_AUTH_TOKEN`
			`- run: npm publish`
Switched the NPM release and GitHub release around no issue - this allows us to do announcements when we know everything else is done 2020-06-11 11:36:45 -05:00			`- uses: tryghost/action-ghost-release@master`