-
Notifications
You must be signed in to change notification settings - Fork 67
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
Dynamically set the NPM tag #510
Conversation
I'm not seeing why the test |
f9d718b
to
f916583
Compare
@blink1073 I'm unsure what to do about the linter error (it is not a modified line):
Do you have any advice? |
for more information, see https://pre-commit.ci
See my commit. :) |
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.
Thank you!
The current publishing action does not deal with setting the NPM tag although we look if the release is a prerelease or not.
This sets the npm tag depending on whether the release is a prerelease or not. It adds also a new
npm_tag
option to override the tag.This was tested successfully on https://github.com/jupyterlab/jupyterlab-git/actions/runs/5312255052/jobs/9616511151