humanwhocodes/env

v3.0.4 didn't publish

nzakas opened this issue · 3 comments

nzakas commented

Got the publish command to run by updating the release-please configuration, but the publish failed with an error:

> @humanwhocodes/env@3.0.4 prepare
> npm run build
> @humanwhocodes/env@3.0.4 build
> rollup -c && tsc && node -e "fs.copyFileSync('./dist/env.d.ts', './dist/env.d.cts')"

src/env.js → dist/env.cjs, dist/env.mjs, dist/env.js...
created dist/env.cjs, dist/env.mjs, dist/env.js in 54ms

src/env.js → dist/env.min.js...
created dist/env.min.js in 161ms
npm notice
npm notice 📦  @humanwhocodes/env@3.0.4
npm notice Tarball Contents
npm notice 1.5kB LICENSE
npm notice 4.6kB README.md
npm notice 9.4kB dist/env.cjs
npm notice 4.8kB dist/env.d.cts
npm notice 4.8kB dist/env.d.ts
npm notice 9.3kB dist/env.js
npm notice 1.7kB dist/env.min.js
npm notice 9.3kB dist/env.mjs
npm notice 1.8kB package.json
npm notice Tarball Details
npm notice name: @humanwhocodes/env
npm notice version: 3.0.4
npm notice filename: humanwhocodes-env-3.0.4.tgz
npm notice package size: 6.2 kB
npm notice unpacked size: 47.2 kB
npm notice shasum: 53fcf3175399b38ae7a6df1dcfbc39edff1218ca
npm notice integrity: sha512-u6q87srLtRcT7[...]NGoYxtghGV4WA==
npm notice total files: 9
npm notice
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm error code E404
npm error 404 Not Found - PUT https://registry.npmjs.org/@humanwhocodes%2fenv - Not found
npm error 404
npm error 404  '@humanwhocodes/env@3.0.4' 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-05-28T14_52_15_892Z-debug-0.log
Error: Process completed with exit code 1.

Not sure what's going on, so filing this until I have time to investigate further.

boneskull commented

@nzakas Possible that the token expired?

nzakas commented

Ah good call! Yes, it looks like this repo was using an old repository secret rather than the one I have set up on the organization, so I was looking in the wrong place. I think it should work the next time we release. 👍

  • 👍1