7fe943bb49
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
27 lines
622 B
YAML
27 lines
622 B
YAML
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
|