mirror of
https://github.com/Unleash/unleash.git
synced 2025-02-04 00:18:01 +01:00
73d13a07c7
Use the tag created by the build action when running npm version, otherwise the checkout actions gets the HEAD of the commit that triggered the original workflow resulting in the usage of the previous version. Potentially in the future, instead of triggering the build manually we could consider using the tag as a trigger for the build process and then all the dependent workflows should work fine. It's good we have this manual for validation, and we workaround some of the limitations before we invest more into more automation
46 lines
1.3 KiB
YAML
46 lines
1.3 KiB
YAML
name: 'Publish to npm'
|
|
on:
|
|
workflow_call:
|
|
inputs:
|
|
version:
|
|
description: "Which version number should we use for the release"
|
|
type: 'string'
|
|
required: true
|
|
|
|
jobs:
|
|
build:
|
|
runs-on: ubuntu-latest
|
|
|
|
strategy:
|
|
matrix:
|
|
node-version: [18.x]
|
|
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
with:
|
|
ref: v${{ inputs.version }} # tag that should be created by the caller workflow
|
|
- name: Setup to npm
|
|
uses: actions/setup-node@v4
|
|
with:
|
|
node-version: 18.x
|
|
registry-url: 'https://registry.npmjs.org'
|
|
cache: 'yarn'
|
|
- name: Build
|
|
run: |
|
|
yarn install --frozen-lockfile
|
|
- name: Publish to npm
|
|
run: |
|
|
LATEST=$(npm show unleash-server version)
|
|
TAG=$(node scripts/npm-tag.js $LATEST)
|
|
npm publish --tag ${TAG:-latest}
|
|
env:
|
|
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
|
|
- uses: aws-actions/configure-aws-credentials@v2
|
|
with:
|
|
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
|
|
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
|
|
aws-region: ${{ secrets.AWS_DEFAULT_REGION }}
|
|
- name: Publish static assets to S3
|
|
run: |
|
|
aws s3 cp frontend/build s3://getunleash-static/unleash/v${{ inputs.version }} --recursive
|