Skip to content

Conversation

@martenrichter
Copy link
Contributor

This PR fixes an issue where previously published packages are not recognized for other npm registries, such as GitHub packages.
Closes #603 .

@krassowski krassowski added the enhancement New feature or request label May 3, 2025
Copy link
Collaborator

@krassowski krassowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@krassowski krassowski changed the title Use npm error code 409 Check for npm error code 409 to skip previously published packages in private registries May 12, 2025
@krassowski krassowski enabled auto-merge (squash) May 12, 2025 16:25
@krassowski krassowski merged commit b360d15 into jupyter-server:main May 12, 2025
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Supporting publishing to multiple npm registries

2 participants