-
Notifications
You must be signed in to change notification settings - Fork 41
Independent publishing for npm and github registry #73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
cache: npm | ||
- run: npm ci | ||
- run: npm test | ||
- run: npm version ${TAG_NAME} --git-tag-version=false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Task for the future (after verifying this works): I think this can be optimised by combining common steps between the two jobs
.github/workflows/publish.yml
Outdated
- run: npm version ${TAG_NAME} --git-tag-version=false | ||
env: | ||
TAG_NAME: ${{ github.event.release.tag_name }} | ||
- run: npm whoami; npm publish --ignore-scripts --@github:registry='https://npm.pkg.github.com' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you probably don't want --ignore-scripts
here, now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch! removed
Makes publishing to npm and github registry independent
Unlike before, If the first one fails, it would not stop the second