Skip to content

Manual Semantic Release #3

Manual Semantic Release

Manual Semantic Release #3

Manually triggered October 24, 2024 01:29
Status Failure
Total duration 34s
Artifacts

release.yaml

on: workflow_dispatch
Fit to window
Zoom out
Zoom in

Annotations

1 error
release
Error: Command failed with exit code 1: npm publish /home/runner/work/relative-to-alias-resolver/relative-to-alias-resolver --userconfig /tmp/950aaa7d6d55cf6612f02aacc8939bc4/.npmrc --tag latest --registry https://registry.npmjs.org/ npm WARN package-json relative-to-alias-resolver@1.0.0 No bin file found at dist/cli.js npm WARN package-json relative-to-alias-resolver@1.0.0 No bin file found at dist/cli.js npm WARN package-json relative-to-alias-resolver@1.0.0 No bin file found at dist/cli.js npm WARN publish npm auto-corrected some errors in your package.json when publishing. Please run "npm pkg fix" to address these errors. npm WARN publish errors corrected: npm WARN publish "bin[relative-to-alias-resolver]" script name was cleaned npm WARN package-json relative-to-alias-resolver@1.0.0 No bin file found at dist/cli.js npm notice npm notice 📦 relative-to-alias-resolver@1.0.0 npm notice === Tarball Contents === npm notice 1.0kB .github/workflows/release.yaml npm notice 248B .nycrc npm notice 3B .prettierrc npm notice 357B CHANGELOG.md npm notice 617B build.mjs npm notice 1.3kB package.json npm notice 302B release.config.js npm notice 12.4kB tsconfig.json npm notice === Tarball Details === npm notice name: relative-to-alias-resolver npm notice version: 1.0.0 npm notice filename: relative-to-alias-resolver-1.0.0.tgz npm notice package size: 5.4 kB npm notice unpacked size: 16.3 kB npm notice shasum: 756c1530d952df25f6e3cb16439563af876306a3 npm notice integrity: sha512-LiU5TJIm3weCj[...]vpvqfl4xMNlnA== npm notice total files: 8 npm notice npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access npm ERR! code E403 npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/relative-to-alias-resolver - You may not perform that action with these credentials. npm ERR! 403 In most cases, you or one of your dependencies are requesting npm ERR! 403 a package version that is forbidden by your security policy, or npm ERR! 403 on a server you do not have access to. npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-24T01_30_05_055Z-debug-0.log