Skip to content

Commit

Permalink
chore: Fix github publish workflow
Browse files Browse the repository at this point in the history
commit 3cdc737 broke the workflow that published NPM packages on new  releases, as we need to pass a tag if --non-interactive is used.

So instead, going forward the tag names will not contain the prefix 'v', which also matches the npm package tagging convention
  • Loading branch information
MonkeyDo committed Jun 27, 2024
1 parent b5cae45 commit 350fbe8
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/workflows/deploy-release-to-npm.yml
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ jobs:
# This script will not bump the version and will use the version from package.json
# It will just fail if trying to publish an already published version
- name: Build and publish the package
run: yarn publish --non-interactive
run: yarn publish --non-interactive --new-version ${{ github.event.release.tag_name }} --no-git-tag-version
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

Expand Down

0 comments on commit 350fbe8

Please sign in to comment.