Skip to content

Read the current skip-changelog label - #21

Merged
Sushisource merged 1 commit into
mainfrom
fix-changelog-label
Aug 26, 2026
Merged

Sushisource merged 1 commit into
mainfrom
fix-changelog-label

Conversation

@Sushisource

Copy link
Copy Markdown
Member

What was changed

Changed the reusable changelog workflow to query the pull request API for its current labels instead of reading labels from the triggering event snapshot. Added the pull-requests read permission required for that query and documented the caller permission contract.

Why?

Pull request events can be queued and executed out of order. On temporalio/sdk-go#2624, two labeled-event runs passed, then a stale event with an empty labels snapshot ran later and superseded them with a failure even though skip-changelog was currently applied.

Reading current PR state makes every queued run agree with the label state at execution time.

Checklist

  1. Closes: N/A

  2. How was this tested:

  • actionlint
  • ShellCheck
  • git diff --check
  • Mocked current label present and absent responses
  • Mocked API failure
  • Mocked valid Unreleased and invalid released-section additions
  1. Any docs updates needed?

The README now documents that callers must grant pull-requests read access.

@Sushisource
Sushisource requested a review from a team as a code owner August 26, 2026 17:26
@Sushisource
Sushisource merged commit d8129c7 into main Aug 26, 2026
3 checks passed
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