[Snyk] Fix for 1 vulnerabilities

[snyk-bot]

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json
  • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	776/1000 Why? Recently disclosed, Has a fix available, CVSS 9.8	Prototype Pollution SNYK-JS-LODASH-590103	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: sails

The new version differs by 116 commits.

• 134f7e6 1.2.2
• 8779c33 Update merge-defaults version
• e2232b7 Upgrade sort-route-addresses version
• dfb62ee Upgrade sails-stringfile version
• 6ad847e 1.2.1
• d6f2aca 1.2.0
• 56f8276 Merge pull request #5270 from balderdashy/upgrades
• a2f44e9 Merge pull request #4561 from MatteoAzzarelli/master
• 1850274 More additions to changelog
• 4122e07 Start updating changelog
• fcd4ed0 Merge branch 'master' into upgrades
• bd00c91 Merge branch 'master' of github.com:balderdashy/sails
• 06f2f2f Note re programmatic usage of generators
• d2caaa4 Update CI configuration
• aad1e63 Update CI configuration
• 57cb678 Change heading in README to use markdown instead of html, in case it fixes the weird double-logo situation on npm
• 3d37acf Update version of i18n-2 to get rid of deprecation warning
• 08cd38f Update rc version
• 536ce3b Upgrade machinepack-redis and update usage
• 5671ecc Update usage of spawnChildProcess in test
• 86b95dc Use .now() for spawnChildProcess, because of upgraded machine runner in the new version
• ac1c0e2 Upgrade machinepack-process dependency
• dd7d9d9 Merge pull request #4745 from tomsaleeba/tomsaleeba-patch-1
• 3ad3dc3 fix: #4445 only set the response content-type header when sending a JS object if the user hasn't already set one

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic