Skip to content

Commit

Permalink
chore: updates pipeline to not use nx publish due to nx bug
Browse files Browse the repository at this point in the history
  • Loading branch information
rustygreen committed Feb 27, 2024
1 parent 3fbd2c1 commit 926cc76
Showing 1 changed file with 33 additions and 3 deletions.
36 changes: 33 additions & 3 deletions .github/workflows/publish.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,38 @@ jobs:
- name: Print environment info
run: npm run nx -- report

- name: Publish packages
run: npm run nx -- release publish
# Switch back to using NX once this bug is fixed:
# https://github.com/nrwl/nx/issues/21855 - @russell.green
#
# - name: Publish packages
# run: npm run nx -- release publish
# env:
# NODE_AUTH_TOKEN: ${{ secrets.NPM_ACCESS_TOKEN }}
# NPM_CONFIG_PROVENANCE: true

# TODO: Remove these steps once the above step is able to
# be added back in - @russell.green

- name: Publish "core" package
run: cd dist/libs/core && npm publish --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
NPM_CONFIG_PROVENANCE: true

- name: Publish "bootstrap" package
run: cd dist/libs/bootstrap && npm publish --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
NPM_CONFIG_PROVENANCE: true

- name: Publish "material" package
run: cd dist/libs/material && npm publish --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
NPM_CONFIG_PROVENANCE: true

- name: Publish "primeng" package
run: cd dist/libs/primeng && npm publish --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_ACCESS_TOKEN }}
NODE_AUTH_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
NPM_CONFIG_PROVENANCE: true

0 comments on commit 926cc76

Please sign in to comment.