Add a way to set a custom NPM registry#57
Draft
mcmire wants to merge 5 commits into
Draft
Conversation
This change makes it possible to test actions that involve publishing of
NPM packages because it allows us to point to a private NPM registry.
For instance, you could run the action by saying:
``` yaml
- uses: MetaMask/action-publish-release@v2
with:
npm-registry-uri-fragment: //npm.fury.io/yourusernamehere/
npm-token: ${{ secrets.NPM_TOKEN }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```
and now when a package is accessed or published, Gemfury will be used
instead of the official NPM registry.
Contributor
Author
|
Testing this in a fork, stand by... |
Contributor
Author
|
Moving this to draft until this is fully tested. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change makes it possible to test actions that involve publishing of NPM packages because it allows us to point to a private NPM registry. For instance, you could run the action by saying:
and now when a package is accessed or published, Gemfury will be used instead of the official NPM registry.
Note: In making this change I have removed backward compatibility with NPM and assume that the project in question is using Yarn v3. This aligns this action with
action-npm-publish.