Closed getsentry-release closed 1 year ago
Publishing: run#5580016508
Failed to publish. (run logs)
Bad branch? You can delete with ease and start over.
publshing to npm failed
npm: npm WARN tar TAR_ENTRY_INVALID invalid base256 encoding
npm: npm WARN tar TAR_BAD_ARCHIVE: Unrecognized archive format
npm: npm ERR! code TAR_BAD_ARCHIVE
npm: npm ERR! TAR_BAD_ARCHIVE: Unrecognized archive format
npm:
npm: npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-07-17T19_58_57_544Z-debug-0.log
npm:
at pYe (/usr/local/bin/craft:552:3236)
at p (/usr/local/bin/craft:556:467)
at ChildProcess.<anonymous> (/usr/local/bin/craft:556:762)
at ChildProcess.emit (node:events:512:28)
at ChildProcess.emit (node:domain:489:12)
at ChildProcess._handle.onexit (node:internal/child_process:293:12)
[info] npm:
[info] npm:
[info] npm:
[info] npm:
[info] npm:
[info] npm: (repeated 17 times)
[info] npm: + @sentry-internal/eslint-plugin-sdk@7.59.0
[info] npm:
[info] npm: + @sentry/angular@7.59.0
[info] npm: + @sentry/hub@7.59.0
[info] npm:
[info] npm:
I wonder if it's an npm cache issue
Publishing: run#5580534750
Failed to publish. (run logs)
Bad branch? You can delete with ease and start over.
:(
Might have to re-create the release if the assets are messed up. Doing that now
Release request retracted by @AbhiPrasad. You may also want to remove your release branch.
Requested by: @AbhiPrasad
Merge target: master
Quick links:
Assign the accepted label to this issue to approve the release. Leave the
#retract
comment under this issue to retract the release (original issuer only).Targets
Targets marked with a checkbox have already been executed. Administrators can manually tick a checkbox to force craft to skip it.