This repository has been archived by the owner on Jul 28, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
59 lines (53 loc) · 1.75 KB
/
npmpublish.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
name: publish
on:
release:
types: [created]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v1
with:
node-version: 12
- run: npm ci
- run: npm test
publish-npm:
needs: build
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v1
with:
node-version: 12
registry-url: https://registry.npmjs.org/
- run: npm ci
# This will tell npm to publish your scoped package with public access.
- run: npm publish --access public
env:
NODE_AUTH_TOKEN: ${{secrets.npm_token}}
# Disabled job
publish-gpr:
# This doesn't work and read
# https://github.com/actions/setup-node/issues/73#issuecomment-599199211
# to know why. Github package repository doens't work for package
# which are not scoped hence not publishing
# Hence, disabling it
if: 1 == 0
needs: build
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v1
with:
node-version: 12
registry-url: https://npm.pkg.github.com/
- run: npm ci
# Read https://joeattardi.codes/2019-11-16-github-package/ to know more
# about this hack. I think the above issue should explain this
- run: echo registry=https://npm.pkg.github.com/amzn >> $NPM_CONFIG_USERCONFIG
- run: npm publish
env:
NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}