[sean0407]

Summary

• Emit the successComment deprecation warning only when successComment is explicitly false.
• Keep the no-commit behavior that skips issue and pull request comments.

Evidence

• Reproduction: run a release with an empty commits array and leave successComment unset. The combined skip condition is true, and the current implementation logs a deprecation warning for a value that was not configured.
• Regression coverage verifies that the empty-commits case does not warn and that successComment: false still warns.
• Changed files: lib/success.js, test/success.test.js.
• Checks run: node --check lib/success.js, node --check test/success.test.js, and git diff --check passed.

Merge Danger

Low. The change only narrows when the deprecation warning is logged; comment skipping and all release behavior remain unchanged.