semantic-release/npm breaks when the package contains too many files with long names

We have a package that contains many files that are in a rather deep folder structure. NPM can pack this correctly without much trouble, however semantic-release fails because it tries to parse the output of npm notice.

npm notice 
npm ERR! code ERR_STRING_TOO_LONG
npm ERR! Cannot create a string longer than 0x1fffffe8 characters
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-03-24T09_34_42_956Z-debug.log
    at makeError (/usr/lib/node_modules/semantic-release/node_modules/execa/lib/error.js:60:11)
    at handlePromise (/usr/lib/node_modules/semantic-release/node_modules/execa/index.js:118:26)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async module.exports (/usr/lib/node_modules/semantic-release/node_modules/@semantic-release/npm/lib/publish.js:30:5)
    at async validator (/usr/lib/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
    at async /usr/lib/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
    at async Promise.all (index 0)
    at async next (/usr/lib/node_modules/semantic-release/node_modules/p-reduce/index.js:16:18) {

npm notice output has 126625 characters so I'm not even sure how I'm hitting this problem at all.

Is there any way to disable this parsing mechanic or figure out what the real issue is?

EDIT: After some research it appears this might have something to do with the package being rather large? 510 MB is the package size. The error is rather misleading here however.