[Snyk] Security upgrade postmark from 3.11.0 to 4.0.0

[q1blue]

This PR was automatically created by Snyk using the credentials of a real user.

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

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • packages/email-server/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	676/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.1	Cross-site Request Forgery (CSRF) SNYK-JS-AXIOS-6032459	Yes	Proof of Concept

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

Commit messages

Package name: postmark

The new version differs by 19 commits.

• c3d1101 updated docs
• e43cd52 set lock file to node v14
• 784c977 update copy
• de4f1aa update workflow
• ee60272 update workflow
• 1d3b4d7 updated locked versions
• 7f71cf9 updated copy
• caef632 copy update
• 7bd94d5 updated lock file
• 27278f9 updated changelog
• 16a4b8b fix copy
• 67494a4 copy update
• 072e8d8 added latest node
• d7604f3 updated test nodes
• d1ecd48 update image names
• 161d47a remove legacy npm installlation call and use newer ci image containers
• 1e6e925 updated workflow
• 5cf017f update ci workflow
• 54316e8 updated axios version

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

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Request Forgery (CSRF)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 44a9433

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR