Publishing to multiple registries

[limonte]

GitHub Package Registry is in public beta stage now 🎉 🎉 🎉

Which means that developers will want to publish their npm packages to both npm and GitHub registries.

Is it possible to configure semantic-release so it'll publish to multiple registries at the same time?

[gr2m]

It should now. I tried a while ago and the only blocker was that GPR created tags & releases when publishing a package, that behavior has recently been removed so no conflict errors should occur. All you'd need to do is set the different registry URL and set NPM_TOKEN to GITHUB_TOKEN in your action. Can you give it a try? Would love to know myself

[limonte]

Thank you @gr2m for the feedback!

All you'd need to do is set the different registry URL and set NPM_TOKEN to GITHUB_TOKEN in your action.

Could you please be more specific on how can I set the different registry URL?

[gr2m]

It came up in the discussion here:
#161

I think that the GitHub registry now also works as a proxy for npm's registry, I don't know if that means that it will publish to both or only fallback to the latter on install

[pvdlg]

I don't think publishing to two different registry is a good idea. It just create an opportunity for inconsistencies.

As the GitHub Registry is a proxy to the npm one, you can publish to the npm registry and your package is going to be available to users using the GitHub one.

If you publish to the GitHub one, I guess your package will be accessible only to the GitHub registry users.

[gr2m]

As the GitHub Registry is a proxy to the npm one, you can publish to the npm registry and your package is going to be available to users using the GitHub one.

That's a good point, GitHub kinda solved to need to publish to two registries for a transitional time.

Does that resolve your problem Limon?

[pvdlg]

Closing as no response provided

[lifeiscontent]

@pvdlg it seems given the docs on setup-node github action that you should just set the NPM_TOKEN to what the GITHUB_TOKEN should be, I've done this but semantic release seems to error.

https://github.com/actions/setup-node

https://github.com/lifeiscontent/isomorphic-querystring/blob/master/.github/workflows/ci.yml

can we update semantic release to accommodate what setup-node does?

[rafegoldberg]

@lifeiscontent setting the NPM_TOKEN env variable for the semantic release step has worked for me in various GitHub workflows. Pretty simple to set it up in the config file:

jobs:
  release:
    steps:
      - name: Build and publish release.
        run: npx semantic-release
        env:
          GH_TOKEN: secrets.GITHUB_TOKEN
          NPM_TOKEN: ${{ secrets.NPM_TOKEN || secrets.GITHUB_TOKEN }}

(Or you could use the simple template repo I've set up!)