Skip to content

fix: post prereleases once they're promoted to a full release - #110

Merged
anurag629 merged 1 commit into
codercops:developfrom
prakashNalla:fix/109-promoted-release
Oct 30, 2026
Merged

anurag629 merged 1 commit into
codercops:developfrom
prakashNalla:fix/109-promoted-release

Conversation

@prakashNalla

Copy link
Copy Markdown
Collaborator

What does this change?

onRelease now posts on the released action instead of published. A prerelease that's later promoted to a full release only sends edited and released, so it was never posted. A normal release sends both published and released, so it still posts once.

Closes #109

How I tested this

  • npm run typecheck and npm test: typecheck is clean, 387 tests pass.
  • Added a test that sends published (prerelease), edited, then released and expects one post. The release tests now send released, and published on its own is ignored, so a normal release isn't posted twice. The new and updated release tests fail on develop.

AI assistance

Claude helped me w/ understand the issue

Checklist

  • I was assigned the linked issue
  • npm run typecheck and npm test pass
  • New behavior has a test in test/
  • No tokens or secrets in the diff

@anurag629 anurag629 added the hacktoberfest-accepted PR counts for Hacktoberfest label Oct 30, 2026
@anurag629
anurag629 merged commit c6cbd3e into codercops:develop Oct 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted PR counts for Hacktoberfest

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Prereleases promoted to a full release are never posted to #releases

2 participants