Skip to content

Make npm & registry target more robust #166

Description

@HazAT

When publishing we should make the npm and registry target not fail if the version already exists.
It makes the publishing process annoying if it stops working somewhere middle in the process.

npm

npm: npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/@sentry%2fangular - You cannot publish over the previously published versions: 6.0.0.

registry

ℹ info [registry] › Adding the version file to the registry for canonical name "npm:@sentry/browser"...
✖ error Error: Version file for "6.0.0" already exists. Aborting.

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions