Skip to content

fix: ensure release failure comments are posted to PR#125

Merged
azu merged 2 commits intomasterfrom
fix-release-failure-comment
Oct 12, 2025
Merged

fix: ensure release failure comments are posted to PR#125
azu merged 2 commits intomasterfrom
fix-release-failure-comment

Conversation

@azu
Copy link
Member

@azu azu commented Oct 12, 2025

The comment job was not running when release failed because it checked for 'released == true' which is never set on failure.

Changes:

  • Changed condition from 'needs.release.outputs.released == true' to 'needs.release.result != skipped'
  • Added default empty value for VERSION in failure comment
  • Used bash parameter expansion to conditionally add 'v' prefix

This ensures PR comments are posted for both success and failure cases.

🤖 Generated with Claude Code

azu and others added 2 commits October 12, 2025 14:45
The comment job was not running when release failed because it checked
for 'released == true' which is never set on failure.

Changes:
- Changed condition from 'needs.release.outputs.released == true' to
  'needs.release.result != skipped'
- Added default empty value for VERSION in failure comment
- Used bash parameter expansion to conditionally add 'v' prefix

This ensures PR comments are posted for both success and failure cases.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@azu azu merged commit 2b0d787 into master Oct 12, 2025
4 checks passed
@azu azu deleted the fix-release-failure-comment branch October 12, 2025 05:59
@github-actions
Copy link
Contributor

Release failed

Please check the workflow logs for details.
🔗 Workflow run: https://github.com/textlint/editor/actions/runs/18439981334

This was referenced Oct 12, 2025
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.

1 participant