Skip to content

v3.5.1

v3.5.1 #17

name: Publish npm package
on:
release:
types: [published]
# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
group: publish-npm-package
cancel-in-progress: false
env:
VITE_BROWSERSTACK_USERNAME: "${{ secrets.VITE_BROWSERSTACK_USERNAME }}"
VITE_BROWSERSTACK_KEY: "${{ secrets.VITE_BROWSERSTACK_KEY }}"
jobs:
publish-node-lts:
name: "node.js lts"
runs-on: ubuntu-latest
environment: BrowserStackEnv
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: "lts/*"
registry-url: "https://registry.npmjs.org"
cache: "npm"
- name: Build
run: |
npm install
npm run build
npm test
- name: npm publish @next
run: |
npm publish --tag next
if: 'github.event.release.prerelease'
env:
NODE_AUTH_TOKEN: "${{ secrets.NPM_PUBLISH_TOKEN }}"
- name: npm publish
run: |
npm publish
if: '!github.event.release.prerelease'
env:
NODE_AUTH_TOKEN: "${{ secrets.NPM_PUBLISH_TOKEN }}"