mirror of
https://github.com/svg/svgo.git
synced 2026-01-25 18:41:39 +03:00
ci: add publish action for releases (#2181)
Defines a GitHub action to publish releases from GitHub CI using the
npm trusted publishers method.
I've tested this on a smaller project I maintain
github.com/jsonresume/jsonresume-theme-class and everything went
great, so I'm adopting this in svg/svgo as well.
This makes the process of releasing a little less stressful, and
significantly reduces the likelihood for human error, like releasing
versions under the wrong dist-tag. 😓
The only difference between this workflow and other ones I've defined is
that for SVGO, I use `jq` to check if the version name includes `-rc.`
which indicates it's a release candidate. If so, we use the `rc`
dist-tag.
This commit is contained in:
28
.github/workflows/publish.yml
vendored
Normal file
28
.github/workflows/publish.yml
vendored
Normal file
@@ -0,0 +1,28 @@
|
||||
name: Node.js Package
|
||||
|
||||
on:
|
||||
release:
|
||||
types: [created]
|
||||
workflow_dispatch:
|
||||
|
||||
permissions:
|
||||
id-token: write
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
publish-npm:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v5
|
||||
- run: corepack enable
|
||||
- uses: actions/setup-node@v6
|
||||
with:
|
||||
node-version: 22
|
||||
registry-url: https://registry.npmjs.org
|
||||
- run: yarn install
|
||||
- run: |
|
||||
if jq -r .version <package.json | grep -q \\-rc.; then
|
||||
yarn npm publish --access public --tag rc
|
||||
else
|
||||
yarn npm publish --access public
|
||||
fi
|
||||
Reference in New Issue
Block a user