Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade deploy_npm for newer NPM versions #374

Open
flyingsilverfin opened this issue Mar 9, 2023 · 1 comment
Open

Upgrade deploy_npm for newer NPM versions #374

flyingsilverfin opened this issue Mar 9, 2023 · 1 comment

Comments

@flyingsilverfin
Copy link
Member

Because of the changes noted in #372, we no longer have a consistent behaviour: NPM deployment works either with username/password OR tokens depending on the environment variables provided.

To attempt to rectify this, we should consistently use token-based authentication if we can. Part of this process should include upgrading deploy_npm to be compatible with newer versions of NPM - it currently requires NPM 8.x to deploy Vaticle's artifacts.

Note: a related but also important step would be to upgrade the testing and snapshot repositories used (eg. Sonatype) to the latest versions.

@alexjpwalker
Copy link
Member

NB we are planning to migrate to a hosted provider at some point to replace our current self-hosted Nexus repository, and should prefer doing this rather than attempting to upgrade our self-hosted installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants