Skip to content

fix: publish GitHub release notes after npm releases - #301

Merged
kmbroai merged 2 commits into
mainfrom
dev/kyleb/automatic-github-release-notes
Aug 7, 2026
Merged

fix: publish GitHub release notes after npm releases#301
kmbroai merged 2 commits into
mainfrom
dev/kyleb/automatic-github-release-notes

Conversation

@kmbroai

@kmbroai kmbroai commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Explicitly dispatch the verified GitHub release workflow after protected npm publication so bot-dispatched releases no longer depend on a suppressed event.
  • Remove the obsolete workflow_run trigger and its event-derived tag/run fallback; manual backfills continue through workflow_dispatch.
  • Isolate actions: write from npm signing and preserve exact release-tag, source-commit, workflow-run, and provenance verification.
  • Wait briefly for the publishing workflow to finish, and fail safely on mismatched runs or a bounded timeout.

Validation

  • Focused release automation and release-cut suites: 193 passed.
  • Full randomized SDK suite: 950 passed, 10 expected platform/integration skips.
  • Ownership-security negative controls passed.
  • TypeScript typecheck/model generation, package build, and Prettier formatting passed.
  • Parsed both workflow YAML files and validated the modified Bash scripts.

@github-actions github-actions Bot added the bug Something isn't working label Aug 7, 2026
@kmbroai kmbroai closed this Aug 7, 2026
@kmbroai kmbroai reopened this Aug 7, 2026
@kmbroai
kmbroai merged commit 381eabb into main Aug 7, 2026
17 checks passed
@kmbroai
kmbroai deleted the dev/kyleb/automatic-github-release-notes branch August 7, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants