Skip to content

feat!: simplify alert components (#252) (#254) #14

feat!: simplify alert components (#252) (#254)

feat!: simplify alert components (#252) (#254) #14

on:
push:
branches:
- main
permissions:
contents: write
pull-requests: write
name: release-please
jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: googleapis/release-please-action@v4
id: release
with:
# this assumes that you have created a personal access token
# (PAT) and configured it as a GitHub action secret named
# `MY_RELEASE_PLEASE_TOKEN` (this secret name is not important).
token: ${{ secrets.RELEASE_PLEASE_TOKEN }}
# This is a built-in strategy in release-please, see "Action Inputs" for more options
release-type: node
# The logic below handles the npm publication:
- uses: actions/checkout@v4
# These if statements ensure that a publication only occurs when a new release is created:
- uses: actions/setup-node@v4
if: ${{ steps.release.outputs.release_created }}
with:
node-version: 20
registry-url: "https://registry.npmjs.org"
- name: Install dependencies
if: ${{ steps.release.outputs.release_created }}
run: npm ci
- name: Compile
if: ${{ steps.release.outputs.release_created }}
run: npx tsc
- name: Publish to NPM
if: ${{ steps.release.outputs.release_created }}
run: npm publish
env:
NODE_AUTH_TOKEN: ${{ secrets.DATABIOSPHERE_FINDABLE_UI_NPM_PUBLISH_TOKEN }} # Ensure this token is scoped to only the permissions required for npm publication to limit security risks.