Supporting publishing to multiple npm registries

[martenrichter]

Problem

I have created a jupyter lab extension and related packages for an open source software.
For historical reasons, the software publishes its internal packages to GitHub packages and all packages that can be useful to others to the normal npm registry.
How would it be possible to release to two package registries simultaneously?

Proposed Solution

May be an option to only publish npm packages? Or to pass multiple registries to the commands?

Additional context

[jtpio]

May be an option to only publish npm packages?

This may already be possible by skipping other steps such as the one building the Python artifacts?

Or to pass multiple registries to the commands?

Right, this would likely need to be added as a configurable. Currently not sure the releaser can handle publishing to multiple registries.

[martenrichter]

Thanks this may work, I have just tried it.
But I was hit by the fact that other registry report slightly different error messages:

npm error code E409
npm error 409 Conflict - PUT https://npm.pkg.github.com/@fails-components%2fjupyter-applet-view - Cannot publish over existing version
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-02-09T16_49_14_715Z-debug-0.log

so that the special case in

jupyter_releaser/jupyter_releaser/lib.py

Line 453 in 4d4ffb1

if "EPUBLISHCONFLICT" in stderr or "previously published versions" in stderr:

is not applied.