Yarn release run script failing

[elisechant]

Running yarn release on a newly cloned repo fails:

~/Sites/thinkmill/monorepo-starter-2(master) » yarn release                                                                     elisechant@Elises-MacBook-Pro
yarn run v1.21.1
$ yarn build && changeset publish
$ preconstruct build
🎁 info building bundles!
🎁 success built bundles!
🦋  info npm info @monorepo-starter/simple-package
🦋  info npm info @monorepo-starter/with-multi-entrypoints
🦋  error an error occurred while running `npm profile get`: E401
🦋  error Unable to authenticate, your authentication token seems to be invalid.
🦋  error Unable to authenticate, your authentication token seems to be invalid.
🦋  warn @monorepo-starter/simple-package is not being published because version 1.0.0 is already published on npm
🦋  warn @monorepo-starter/with-multi-entrypoints is not being published because version 1.0.0 is already published on npm
🦋  warn No unpublished packages to publish
ExitError: The process exited with code: 1
    at getTokenIsRequired (/Users/elisechant/Sites/thinkmill/monorepo-starter-2/node_modules/@changesets/cli/dist/cli.cjs.dev.js:491:11)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

This should just work with no configuration.

[Noviny]

It looks like you're not logged into npm on your machine (it failed to authenticate you)

Additionally, there's no way we can make this work out of the box, as most people who clone this won't have publish rights to the package names @monorepo-starter/simple-package and will need to add/update their own packages.

[elisechant]

@Noviny yep that's true. Still we should capture that as an environment requirement.

Additionally, there's no way we can make this work out of the box

We should manage this somehow. People will think something is wrong, not that that is the expectation. A CLI would solve this.