Uh oh!
There was an error while loading. Please reload this page.
Allow actions to specify target registry domain to publish - #309
Conversation
🦋 Changeset detectedLatest commit: 4c56449 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
luisfagottani
commented
Jan 12, 2024
Hey @ImadBoumzaoued, we need this feat to be able to define a custom registry url. Can you merge this, plz!!? |
Andarist
commented
Jan 12, 2024
We only create -name: Creating.npmrcrun: |cat<<EOF>"$HOME/.npmrc"//registry.npmjs.org/:_authToken=$NPM_TOKENEOF
env:
NPM_TOKEN: ${{secrets.NPM_TOKEN}}You can control your target registry in the |
luisfagottani
commented
Jan 15, 2024
That's right @Andarist, but I didin't need the home variable, just created with The only thing I think it's a little strange is the output from changeset warning me that doesn't exist a npm user file, even if I created an step before. Otherwise, all good. |

At the moment GitHub Actions will create
.npmrcthat only point to default's NPM registry (which isregistry.npmjs.org). This actions option will allow user to change registry domain that script will create, and configure.