Skip to content

fix: avoid incorrect successComment deprecation warning - #1334

Open
wyhlyh913 wants to merge 1 commit into
semantic-release:masterfrom
wyhlyh913:fix/1297-success-comment-warning
Open

wyhlyh913 wants to merge 1 commit into
semantic-release:masterfrom
wyhlyh913:fix/1297-success-comment-warning

Conversation

@wyhlyh913

@wyhlyh913 wyhlyh913 commented Nov 6, 2026 •

Copy link
Copy Markdown

What

Fixes #1297.

Only log the successComment deprecation warning when successComment is explicitly set to false.

When no commits are found in a release, the plugin still skips commenting on issues and pull requests, but no longer logs an unrelated deprecation warning.

Tests

  • npx ava --verbose test/success.test.js — 28 tests passed.
  • npx prettier --check lib/success.js test/success.test.js — passed.

Notes

The full unit test run currently has one unrelated failure in test/to-octokit-options.test.js, concerning the expected Undici module path. The targeted success.test.js tests all pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

1 participant