paritytech / opstooling-js

Shared functionality for OpsTooling projects
https://www.npmjs.com/package/@eng-automation/js
Apache License 2.0
0 stars 1 forks source link

Publish opstooling-js to npm registry #31

Closed mutantcornholio closed 1 year ago

mutantcornholio commented 1 year ago

Currently we publish it to as a tag on git repo, which forces devDeps installation as well as running prepare scripts.

With the security questions around sorted out, let's publish the package to NPM registry.

mordamax commented 1 year ago

Related: https://github.com/paritytech/ci_cd/wiki/Publish-NPM-package-to-npmjs.com

From "Security Discussion: NPM & Cargo"

image
mutantcornholio commented 1 year ago

So, if nobody objects, I'm picking @eng-automation/js for this package (and @eng-automation/integrations, @eng-automation/js-style, ... for others)

mutantcornholio commented 1 year ago

https://github.com/paritytech/npm_publish_automation/pull/32

mordamax commented 1 year ago
npm ERR! 402 Payment Required - PUT https://registry.npmjs.org/@eng-automation%2fjs - You must sign up for private packages

npm ERR! A complete log of this run can be found in:

https://github.com/paritytech/npm_publish_automation/actions/runs/4620840626/jobs/8171506007

mutantcornholio commented 1 year ago
npm ERR! 402 Payment Required - PUT https://registry.npmjs.org/@eng-automation%2fjs - You must sign up for private packages

npm ERR! A complete log of this run can be found in:

https://github.com/paritytech/npm_publish_automation/actions/runs/4620840626/jobs/8171506007

Yeah, this is still in progress

alvicsam commented 1 year ago

Guys, sorry I've missed the discussion. Is it possible to publish packages to @parity org? There is no strict requirement but I think it's better for naming consistency. So to have something like this:

mordamax commented 1 year ago

@alvicsam please see our discussions in Security Discussion: NPM & Cargo -> and https://github.com/paritytech/npm_publish_automation/blob/main/packages.ts There's no parity, each team can have their own name and that's ok we scoped out team bundles under one name, and don't plan to create more

Related: https://github.com/paritytech/ci_cd/wiki/Publish-NPM-package-to-npmjs.com

From "Security Discussion: NPM & Cargo" image

alvicsam commented 1 year ago

Okay, I see. Created @eng-automation org

mutantcornholio commented 1 year ago

All common packages have been published https://www.npmjs.com/package/@eng-automation/js https://www.npmjs.com/package/@eng-automation/js-style https://www.npmjs.com/package/@eng-automation/integrations https://www.npmjs.com/package/@eng-automation/testing