Activity

1. Andarist commented on Nov 19, 2021

   

   Andarist

   on Nov 19, 2021

   Member

   More actions

   Could you share more info about your setup? What kind of registry are you using? How compatible such registries are with npm registry in general? I don't know much about custom registries so I really need some extra information to introduce educated changes to the codebase that would improve the mentioned situation.
2. jacobp100 commented on Nov 20, 2021

   

   jacobp100

   on Nov 20, 2021

   Author

   More actions

   All our internal packages are scoped under some name (we have a few scopes), and they're served from nexus. Every other package comes from npm. However, when you're using changesets within a scoped package, it's talking to nexus for package info and authentication. Nexus isn't the best - and misses a lot of features of npm. The key one here being authentication info.
3. andersonba commented on Mar 17, 2022

   

   andersonba

   on Mar 17, 2022

   More actions

   @jacobp100 still having the problem? I'm facing this too. We also use Nexus for some scopes.

   No changesets found, attempting to publish any unpublished packages to npm
   Found existing user .npmrc file
   Didn't find existing auth token for the npm registry in the user .npmrc file, creating one
   [command]/usr/local/bin/yarn changeset publish
   yarn run v1.22.17
   $ /home/runner/work/web/web/node_modules/.bin/changeset publish
   🦋  info npm info @my-org/my-lib
   🦋  warn Received 404 for npm info "@my-org/my-lib"
   🦋  info @my-org/my-lib is being published because our local version (0.2.3) has not been published on npm
   🦋  info Publishing "@my-org/my-lib" at "0.2.3"
   🦋  error npm ERR! 400 Bad Request - PUT *** - Repository does not allow updating assets: npm-internal
   

   See the last line, because the "npm info" doesn't work as expected, changesets tries to publish but an error occurs because we already published the same version at another time.

   FYI @Andarist
4. gethari commented on Nov 19, 2024

   

   gethari

   on Nov 19, 2024

   More actions

   @jacobp100 still having the problem? I'm facing this too. We also use Nexus for some scopes.

   No changesets found, attempting to publish any unpublished packages to npm
   Found existing user .npmrc file
   Didn't find existing auth token for the npm registry in the user .npmrc file, creating one
   [command]/usr/local/bin/yarn changeset publish
   yarn run v1.22.17
   $ /home/runner/work/web/web/node_modules/.bin/changeset publish
   🦋  info npm info @my-org/my-lib
   🦋  warn Received 404 for npm info "@my-org/my-lib"
   🦋  info @my-org/my-lib is being published because our local version (0.2.3) has not been published on npm
   🦋  info Publishing "@my-org/my-lib" at "0.2.3"
   🦋  error npm ERR! 400 Bad Request - PUT *** - Repository does not allow updating assets: npm-internal
   

   See the last line, because the "npm info" doesn't work as expected, changesets tries to publish but an error occurs because we already published the same version at another time.

   FYI @Andarist

   did you get a workaround for this ?
5. bluwy commented on Jun 30, 2026

   

   bluwy

   on Jun 30, 2026

   Member

   More actions

   I think this is indirectly solved by #2065 now
6. bluwy

   closed this as completedon Jun 30, 2026