yarn changeset publish is using npm info instead of yarn npm info #965

Activity

1. carterworks commented on Jun 5, 2026

   

   carterworks

   on Jun 5, 2026

   More actions

   With pnpm v11's move from specifying itself in packageManager to the corepack-compatible devEngines.packageManager, this issue has come up again.

   with

     "devEngines": {
       "packageManager": {
         "name": "pnpm",
         "version": "^11.4.0",
         "onFail": "download"
       }
     },

   pnpm changeset publish returns this error

   🦋  error Received an unknown error code: EBADDEVENGINES for npm info "$REPONAME"
   🦋  error The developer of this package has specified the following through devEngines
   🦋  error Invalid devEngines.packageManager
   🦋  error Invalid name "pnpm" does not match "npm" for "packageManager"
   🦋  error [object Object]
   

   Looking forward to #2047 being released
2. Andarist commented on Jun 5, 2026

   

   Andarist

   on Jun 5, 2026

   Member

   More actions

   @carterworks we plan to release v3 by the end of the month. #2047 is unlikely to land right now - but I'm refactoring some of this code that calls out to the package manager CLIs as we speak, so I expect this to get solved by that.

   🎉React with 🎉2Reacted by Carter McBride and Danny
3. smashercosmo

   added 2 commits that reference this issue on Jul 2, 2026

   chore: change devEngines.packageManager.onFail to "warn" untill this is

   ...

   5c2a493

   chore: remove devEngines untill this is resolved changesets/changeset…

   ...

   b2a0c8b
4. mizdra

   added a commit that references this issue on Jul 9, 2026

   chore: use legacy packageManager field to work around changesets issue …

   ...

   e873392
5. bluwy commented on Aug 3, 2026

   

   bluwy

   on Aug 3, 2026

   Member

   More actions

   fixed in #2097

   🎉React with 🎉1Reacted by Carter McBride
6. bluwy

   closed this as completedon Aug 3, 2026