Skip to content

Version Packages (#2618) #65

Version Packages (#2618)

Version Packages (#2618) #65

Workflow file for this run

name: Release
on:
push:
branches:
- main
jobs:
release:
runs-on: ubuntu-latest
permissions:
contents: write
id-token: write
issues: write
repository-projects: write
deployments: write
packages: write
pull-requests: write
steps:
- uses: actions/checkout@v2
with:
fetch-depth: 0
token: ${{ secrets.CHANGESETS_GITHUB_TOKEN }}
- name: Use Node.js
uses: actions/setup-node@v2
with:
node-version: 18.x
# Wireit cache
- uses: google/wireit@setup-github-actions-caching/v1
- uses: pnpm/action-setup@v2.2.2
with:
version: 7
- name: Get pnpm store directory
id: pnpm-cache
run: echo "::set-output name=pnpm_cache_dir::$(pnpm store path)"
- name: Setup pnpm cache
uses: actions/cache@v3
with:
path: ${{ steps.pnpm-cache.outputs.pnpm_cache_dir }}
key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
restore-keys: |
${{ runner.os }}-pnpm-store-
- name: Install dependencies
run: pnpm install
- name: Build packages
run: pnpm run build
- name: PR or Publish
id: changesets
uses: changesets/action@v1
with:
# Note: Our `package.json:scripts.version` currently doesn't have `--fix-lockfile` for
# `pnpm install` because of a PNPM bug of some kind.
# See spectacle issue: https://github.com/FormidableLabs/spectacle/issues/1156
version: pnpm run version
publish: pnpm run publish
env:
# Note: we are using a different GITHUB_TOKEN due to the issues in this thread:
# https://github.com/changesets/action/issues/187
GITHUB_TOKEN: ${{ secrets.CHANGESETS_GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}