successComment deprecation warning is logged for releases with no commits, even when successComment is not set

从 lib/success.js 中的 success() 入口点开始，检查将 successComment === false 与空的 commits 列表结合起来的分支。使用 commits: [] 且不提供 successComment 选项来复现该行为，然后添加一个回归测试，表明只有显式设置为 false 的 successComment 才会记录弃用警告，而空的 commits 仍会记录其正常消息。

On 12.0.9 (same code on master), lib/success.js logs the "'false' for 'successComment' is deprecated" warning for any release with an empty commits list, even when successComment was never set.

if (successComment === false || isEmpty(commits)) {
  if (isEmpty(commits)) {
    logger.log("No commits found in release");
  }
  logger.log("Skip commenting on issues and pull requests.");
  logger.warn(
    `DEPRECATION: 'false' for 'successComment' is deprecated and will be removed in a future major version. Use 'successCommentCondition' instead.`,
  );
}

Both halves of the condition end up in the same branch, so the logger.warn runs for the empty-commits case too. We hit it through a monorepo release tool that creates releases for packages whose path-filtered commit list is empty (dependency-only releases). Nothing in our config sets successComment or successCommentCondition, and the warning shows up once per such release.

Following the advice in the message doesn't help either: the first branch is taken before successCommentCondition is read, so setting it to false or a condition changes nothing about the warning.

To reproduce, call success() with commits: [] and no successComment option. You get the "No commits found in release" log line followed by the deprecation warning.

I think the warning should only be logged when successComment === false. Happy to send a PR for that with a test if that's welcome.