includeDependencies option description is a bit confusing

[DMXL]

Sometimes it's necessary to include a package as a direct dependency instead of a peer dependency. This can happen if your package has a very specific requirement on the dependency and cannot accept another version.

Isn't this describing the scenario where we DON'T want to rely on external dependencies?

[pmowrer]

I agree it's confusing. Honestly, I'd rather remove the option since it doesn't align with this plugin's use-case.

[pmowrer]

🎉 This issue has been resolved in version 2.2.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀