bump allow scripts

[EtDu]

• Fixes https://app.circleci.com/pipelines/github/MetaMask/metamask-extension/9600/workflows/0dbdedd0-7bb8-45fa-9a29-7357d5fd8907/jobs/280180

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[metamaskbot]

Builds ready [10888b8]

• builds: chrome, firefox, opera
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• build viz: Build System
• code coverage: Report
• storybook: Storybook
• all artifacts

Page Load Metrics (691 ± 52 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	54	97	69	11	5
		domContentLoaded	470	850	689	109	52
		load	472	851	691	109	52
		domInteractive	470	850	689	109	52

[Gudahtt]

So the only change is that there is now a trailing newline - is that correct?

[kumavis]

@Gudahtt correct - it now appends a newline when generating the policy https://npmfs.com/compare/@lavamoat/allow-scripts/1.0.5/1.0.6/

[EtDu]

For the sake of our linter. Maybe we broke someone else's... 🤷

[Gudahtt]

Doubtful. It's a requirement of the POSIX standard, for one thing. The npm CLI will always include a trailing newline in newly generated package.json files as well, and they typically dictate the format used by any tooling.

Though this might still be broken on Windows, for any projects that are setup to use \r\n. Ideally allow-scripts would preserve the pre-existing formatting.