Open vlilloh opened 4 years ago
I'm not sure it's possible what you're asking for, at least in a single step in a job. I think when you're publishing a package it checks the registry, that might be specified in .npmrc
for example, but I guess it can be only a single registry per package. And I think it's not a good idea, in general, to publish to both registries anyway.
Also, I noticed you use secrets.GITHUB_TOKEN
, nothing wrong with that except you want changesets/action
's generated PR to trigger other workflows. GITHUB_TOKEN
does not trigger workflows, in case you'll encounter this problem - add your github personal access token to the secrets (eg. name GH_TOKEN
) and refer to it for GITHUB_TOKEN
like this:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
This is not what you've asked for, but might be helpful.
4 years later, I think it's very reasonable to publish to multiple registries simultaneously now due to the emergence of various runtimes and various registries like Deno, Bun, GitHub, and jsr.io?
Does anyone using changeset/actions to publish to multiple registries?
I've correctly setup the Changesets Release Action to publish to GPR:
But I can't setup the Changesets Release Action to publish the packages both to GPR and to NPM. Is it possible in the latest version?