chore: fix publint failure in release workflow

[achou11]

Fixes an issue seen here where running publint during npm pack --dry-run fails on npm v12. The release action we use uses npm v12 and runs the dry run internally which is how this error surfaces.

There might be an fix in publint but it's currently not released (link).

I've opted for not running publint as part of the test scripts and instead having it be its own script that runs as a dedicated script in CI. Also no longer runs as part of the release workflow build command.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	publint@​0.3.17 ⏵ 0.3.21	+1		+1	-1

View full report

[achou11]

Maybe just opting to run publint as part of the build-command input in the release workflow might make more sense? I feel like I might be misunderstanding what --pack false actually does...

[gmaclennan]

I don't think the postpack is needed? The CI check ensures we don't release with it broken. This is all we can do until publint fixes things.

[achou11]

I don't think the postpack is needed? The CI check ensures we don't release with it broken. This is all we can do until publint fixes things.

Addressed via 7ba0103 (also updated PR description)