Skip to content

Commit

Permalink
chore: update publish script to publish CLI tool to NPM [] (#680)
Browse files Browse the repository at this point in the history
  • Loading branch information
primeinteger committed Jun 28, 2024
1 parent 8c77a33 commit 651f998
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion .github/workflows/publish.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,8 @@ jobs:
run: echo -e "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}\n//npm.pkg.github.com/:_authToken=${{ steps.vault.outputs.GITHUB_PACKAGES_WRITE_TOKEN }}\n@contentful:registry=https://npm.pkg.github.com" > ./.npmrc
env:
GITHUB_TOKEN: ${{ steps.vault.outputs.GITHUB_PACKAGES_WRITE_TOKEN }}
secrets:
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
# We only want to publish if there are changes to any package. Since the lerna --force-publish flag publishes even if there are no changes
# we check if there are changes to the packages first, and if not, we exit early
- name: Changed packages check
Expand All @@ -72,7 +74,6 @@ jobs:
run: echo "No changes to packages to publish, skipping publish step"
- name: 'Version and publish'
env:
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
GITHUB_TOKEN: ${{ steps.vault.outputs.GITHUB_PACKAGES_WRITE_TOKEN }}
# GH_TOKEN needed by lerna to create releases on github
GH_TOKEN: ${{ steps.vault.outputs.GITHUB_PACKAGES_WRITE_TOKEN }}
Expand Down

0 comments on commit 651f998

Please sign in to comment.