Skip to content

fix: use release_created (singular) output for release-please v4#15

Merged
thoroc merged 2 commits into
mainfrom
fix/release-please-outputs
Feb 6, 2026
Merged

fix: use release_created (singular) output for release-please v4#15
thoroc merged 2 commits into
mainfrom
fix/release-please-outputs

Conversation

@thoroc

@thoroc thoroc commented Feb 6, 2026

Copy link
Copy Markdown
Owner

Fixes the release workflow by using the correct output name. In release-please-action v4, releases_created (plural) is broken and always returns true. Must use release_created (singular) instead.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-copilot Please review this PR focusing on:

  1. Code quality, best practices, and potential bugs
  2. Security vulnerabilities and unsafe patterns
  3. Performance implications
  4. Documentation accuracy and completeness
  5. Test coverage and edge cases

Please provide specific, actionable feedback.

@thoroc
thoroc force-pushed the fix/release-please-outputs branch from 9da4abd to 6fe9558 Compare February 6, 2026 22:53

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-copilot Please review this PR focusing on:

  1. Code quality, best practices, and potential bugs
  2. Security vulnerabilities and unsafe patterns
  3. Performance implications
  4. Documentation accuracy and completeness
  5. Test coverage and edge cases

Please provide specific, actionable feedback.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-copilot Please review this PR focusing on:

  1. Code quality, best practices, and potential bugs
  2. Security vulnerabilities and unsafe patterns
  3. Performance implications
  4. Documentation accuracy and completeness
  5. Test coverage and edge cases

Please provide specific, actionable feedback.

@thoroc
thoroc merged commit 8b182f4 into main Feb 6, 2026
8 checks passed
@thoroc
thoroc deleted the fix/release-please-outputs branch February 6, 2026 22:59
@thoroc thoroc mentioned this pull request Feb 6, 2026
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