Not able to publish the package to npm.

[nalnir]

Using github actions.
My publish.yaml looks like this:

name: "Publish"
on:
  push:
    branches: 
      - "main"

concurrency: ${{ github.workflow }}-${{ github.ref }}

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: pnpm/action-setup@v2
        with:
          version: 7
      - uses: actions/setup-node@v3
        with: 
          node-version: 16.x
          cache: "pnpm"

      - run: pnpm install --frozen-lockfile
      - name: Create Release Pull Request or Publish 
        id: changesets
        uses: changesets/action@v1
        with: 
          publish: pnpm run publish
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

When I push the changes to githug the release action is successful but I get this message:

"body": "This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.\n\n\n# Releases\n## @crypties/arcane-blessings@0.0.3\n\n### Patch Changes\n\n- 052b371: Initial publish\n",

When I merge the PR then I get the errror:

setting git user
/usr/bin/git config user.name "github-actions[bot]"
/usr/bin/git config user.email "github-actions[bot]@users.noreply.github.com"
setting GitHub credentials
No changesets found, attempting to publish any unpublished packages to npm
No user .npmrc file found, creating one
/home/runner/setup-pnpm/node_modules/.bin/pnpm run publish
 ERR_PNPM_NO_SCRIPT  Missing script: publish

Command "publish" not found.
Error: Error: The process '/home/runner/setup-pnpm/node_modules/.bin/pnpm' failed with exit code 1
Error: The process '/home/runner/setup-pnpm/node_modules/.bin/pnpm' failed with exit code 1

[nalnir]

Ok, had some issues in my yaml. First of all: jobs: build: should be jobs: publish second my pnpm script: pnpm publish had a type and instead of changeset publish I had changesets publish so I fixed that as well. However now I'm getting 404 error:

info npm info @crypties/arcane-blessings
🦋  warn Received 404 for npm info "@crypties/arcane-blessings"
🦋  info @crypties/arcane-blessings is being published because our local version (0.0.6) has not been published on npm
🦋  info Publishing "@crypties/arcane-blessings" at "0.0.6"
🦋  error an error occurred while publishing @crypties/arcane-blessings: E404 Not Found - PUT https://registry.npmjs.org/@crypties%2farcane-blessings - Scope not found 
🦋  error 
🦋  error  '@crypties/arcane-blessings@0.0.6' is not in this registry.
🦋  error 
🦋  error Note that you can also install from a
🦋  error tarball, folder, http url, or git url.
🦋  error npm notice Publishing to https://registry.npmjs.org/
🦋  error npm ERR! code E404
🦋  error npm ERR! 404 Not Found - PUT https://registry.npmjs.org/@crypties%2farcane-blessings - Scope not found
🦋  error npm ERR! 404 
🦋  error npm ERR! 404  '@crypties/arcane-blessings@0.0.6' is not in this registry.
🦋  error npm ERR! 404 
🦋  error npm ERR! 404 Note that you can also install from a
🦋  error npm ERR! 404 tarball, folder, http url, or git url.
🦋  error {
🦋  error   "error": {
🦋  error     "code": "E404",
🦋  error     "summary": "Not Found - PUT https://registry.npmjs.org/@crypties%2farcane-blessings - Scope not found",
🦋  error     "detail": "\n '@crypties/arcane-blessings@0.0.6' is not in this registry.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
🦋  error   }
🦋  error }
🦋  error 
🦋  error npm ERR! A complete log of this run can be found in:
🦋  error npm ERR!     /home/runner/.npm/_logs/2023-09-09T02_[51](https://github.com/nalnir/arcane-blessings/actions/runs/6128491180/job/16635592502#step:6:52)_06_182Z-debug-0.log
🦋  error 
🦋  error packages failed to publish:
🦋  @crypties/arcane-blessings@0.0.6
 ELIFECYCLE  Command failed with exit code 1.
Error: Error: The process '/home/runner/setup-pnpm/node_modules/.bin/pnpm' failed with exit code 1
Error: The process '/home/runner/setup-pnpm/node_modules/.bin/pnpm' failed with exit code 1

I have NPM_TOKEN set in my Github, but I am not able to set my GITHUB_TOKEN becuase github does not allow token name that starts with GITHUB_

[nalnir]

So I just changed the name for GITHUB_TOKEN and instead in my publish.yaml I have it like this: GITHUB_TOKEN: ${{ secrets.CI_TOKEN }}

But the error is still 404. I don't know what am I suppose to do now

[MikelArnaiz]

GITHUB_TOKEN is already provided by GitHub, you don't have to add it to your secrets, you can just use it

env:
  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Token automatically added by Github

[zendostrike]

Im having the same problem, trying to publish to npm but I always get the same message:
No changesets found, attempting to publish any unpublished packages to npm

[jorenbroekema]

Instead of env -> NPM_TOKEN try to use NODE_AUTH_TOKEN:

      - name: Create Release Pull Request or Publish to npm
        id: changesets
        uses: changesets/action@v1
        with:
          # This expects you to have a script called release which does a build for your packages and calls changeset publish
          publish: npm run release
          commit: 'chore: release'
          # to ensure the lock file also gets bumped accordingly and added to the commit
          version: npm run version
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

[Andarist]

The provided information is too sparse. Without a repro case there is not much I can do about it

[jorenbroekema]

@Andarist a quick repro could be made with a new scoped npm package (unpublished), set to version 0.0.1 and try to publish it with the basic usage example from this action's docs. I used a granular NPM access token with read/write access to that scope. This is how I reproduced this issue this morning with latest version of changesets action. The 404 npm error upon publishing through the action is because NPM_TOKEN env variable does not work. NODE_AUTH_TOKEN does. NPM tends to throw 404 errors instead of 401/403 when your access token is missing or doesn't have access.

[Andarist]

I don't know why Changesets are relying on NPM_TOKEN but the changesets/action (by default) tries to write it into an .npmrc file and that should be respected:

action/src/index.ts

Lines 58 to 85 in ff7179c

	let userNpmrcPath = `${process.env.HOME}/.npmrc`;
	if (fs.existsSync(userNpmrcPath)) {
	core.info("Found existing user .npmrc file");
	const userNpmrcContent = await fs.readFile(userNpmrcPath, "utf8");
	const authLine = userNpmrcContent.split("\n").find((line) => {
	// check based on https://github.com/npm/cli/blob/8f8f71e4dd5ee66b3b17888faad5a7bf6c657eed/test/lib/adduser.js#L103-L105
	return /^\s*\/\/registry\.npmjs\.org\/:[_-]authToken=/i.test(line);
	});
	if (authLine) {
	core.info(
	"Found existing auth token for the npm registry in the user .npmrc file"
	);
	} else {
	core.info(
	"Didn't find existing auth token for the npm registry in the user .npmrc file, creating one"
	);
	fs.appendFileSync(
	userNpmrcPath,
	`\n//registry.npmjs.org/:_authToken=${process.env.NPM_TOKEN}\n`
	);
	}
	} else {
	core.info("No user .npmrc file found, creating one");
	fs.writeFileSync(
	userNpmrcPath,
	`//registry.npmjs.org/:_authToken=${process.env.NPM_TOKEN}\n`
	);
	}

Setting up repro on my own is not an option for two reasons:

1. It takes time
2. I can't be sure I'd set it up in the very same way you would.

[ethanz-code]

Trying to use NODE_AUTH_TOKEN solved my problem