Update npm plugin #653
Open
Update npm plugin #653
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi. Please merge master to your branch to re-run CI. |
Dazix
force-pushed
the
update_npm_plugin
branch
from
58aa5a0 to
1cbac9a
Compare
|
Hi, I just did a rebase on the upstream master, but no CI was triggered. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
fix
What is the current behavior?
npm plugin works only for npmjs.com tokens
What is the new behavior (if this is a feature change)?
npm plugin now supports variable token length e.g. token for gitlab registry
Does this PR introduce a breaking change?
no breaking change
Other information: