fix: empty commit to trigger a release on the @latest npm tag

[wolfy1339]

---

Behavior

Before the change?

• The latest release wasn't published to the @latest tag on npm

After the change?

• The empty commit will trigger a release and publish the release to the @latest tag on npm

Other information

• Follow up to The automated release is failing 🚨 #831 (comment)

---

Additional info

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes (Please add the Type: Breaking change label)
• No

If Yes, what's the impact:

• N/A

Pull request type

Please add the corresponding label for change this PR introduces:

• Dependencies/code cleanup: Type: Maintenance

---

[github-actions]

🎉 This PR is included in version 10.9.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 11.0.0-beta.10 🎉

The release is available on:

• GitHub release
• npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 10.9.1 🎉

The release is available on:

• GitHub release
• npm package (@release-10.x dist-tag)

Your semantic-release bot 📦🚀