Fix release note generation by adding missing permissions#8484
Fix release note generation by adding missing permissions#8484andrewlock wants to merge 2 commits intomasterfrom
Conversation
BenchmarksBenchmark execution time: 2026-04-20 12:27:34 Comparing candidate commit 8db4a13 in PR branch Found 1 performance improvements and 2 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics, 87 known flaky benchmarks.
|
Summary of changes
Adds
pull_requestspermission to draft-releasedd-octo-stschainguard fileReason for change
The release note generation has been silently failing since we switched to STS:
I think that's because we're missing the
pull_requestspermission in the dd-octo-sts file, and the issues endpoint we're using silently filters this out. This also seems to only apply to app permissions, which is what dd-octo-sts uses, not to fine-grained tokens, which is why we couldn't replicate it locally.Implementation details
pull_requests: readto the draft release STS definition.Test coverage
Nope, we just have to wait for the next release, and hope nothing breaks 😬