Hmm. Didn't work:

npm notice Publishing to https://registry.npmjs.org/ with tag next and public access
npm error code E404
npm error 404 Not Found - PUT https://registry.npmjs.org/@mapbox%2fnode-pre-gyp - Not found
npm error 404
npm error 404  '@mapbox/[email protected]' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-12-07T19_47_33_314Z-debug-0.log

Hmm, i have never seen that error before. that url is says got a 404 seems like it exists... can you re-run that job?

The only other thing I could think of is a permission issue on the NPM_TOKEN in the repository secrets

The error message is quite misleading. From searching it, it seems it's the error you get when there's an auth issue. I wonder if there's something wrong with the NPM_TOKEN.

@mapsam @pratikyadav could you take a look?

Just an FYI for anyone looking, that error is on the release workflow at https://github.com/mapbox/node-pre-gyp/actions/runs/12215633640/job/34077817098

That step just basically runs

  npm config set //registry.npmjs.org/:_authToken "${NPM_TOKEN}"
  npm publish --tag next --access public

(which worked in my test )

Hello! Excited to see 2.x coming along 😄 I'm no longer at Mapbox so won't be able to get a viable NPM token, but I'm fairly certain the one originally set up from #744 (comment) had a ~3 month expiration on it.

Tagging @bilindhajer who helped me set that up originally, maybe he or others with permissions could lend a hand.

@benmccann @acalcutt if you try the workflow again it will work :)

Someone with admin rights could either rerum the failed 'publish' job in https://github.com/mapbox/node-pre-gyp/actions/runs/12215633640/job/34077817098 or manually run the release action again. I think that should pick up the new npm key and complete the npm upload if it works.

The workflow will also re-run on the next push if you wanted me to increment the pre-release version and try again that way.

Re-ran the failed test.

Looks like it worked now! https://www.npmjs.com/package/@mapbox/node-pre-gyp/v/2.0.0-rc.0

Thanks everyone for pitching in to get this done together!!

It looks like the RC has 800k downloads/week and no issues reported against it. Should we cut a final release? Anyone want to send the PR for it?