Closed mutantcornholio closed 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)
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
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
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:
@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
Okay, I see. Created @eng-automation org
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.