Repository navigation
This release adds the issues / status_changed webhook event and an issue status field on issue payloads. Existing code that builds issue records by hand or switches exhaustively over issue events needs small changes.
⚠️ Breaking changes
- New
issuesevent in the sealed hierarchy:GitHubWebhookIssuesEventnow also permitsGitHubWebhookIssuesStatusChangedEvent. An exhaustiveswitchoverGitHubWebhookIssuesEventwithout adefaultno longer compiles. Add acase GitHubWebhookIssuesStatusChangedEvent ebranch. statuscomponent added to issue records:GitHubWebhookIssue(incommonand inissues),GitHubWebhookIssuesClosedIssue,GitHubWebhookIssuesOpenedIssue,GitHubWebhookIssuesTransferredChangesNewIssueand the other per-action issue records gained@Nullable GitHubWebhookIssueStatus statusin the middle of the component list. Code that calls their canonical constructors directly (mostly tests and fixtures) must pass the new argument,nullif there is no status. Records decoded from webhooks are not affected.
✨ What's new
- Issue status events: the decoder now handles
issuesevents with actionstatus_changedand returnsGitHubWebhookIssuesStatusChangedEvent. It carriesstatus(the new status) andchanges.changes.status().from()is the previous status ornull.changes.state()andchanges.stateReason()are set only when the change also closed or reopened the issue, or changed the close reason. Available in cloud and GHEC. GitHubWebhookIssueStatus: new record withcategory,idandname, available asissue.status()on every issue payload. It isnullwhen the issue has no status. Issue statuses are a GitHub preview feature, so only accounts enrolled in the preview receive them.
🔧 Improvements
- Updated to
common-core7. The webhook JSON mapper is now built on the sharedJsonMappers.snakeCase()base and behaves as before. Unknown enum constants still read asnull, and a JSON string is still read into a collection property as a collection of one.
Full Changelog: v2026.3.10.2...v2026.3.10.3