Releasesby GlyphNew Incidents page rolling out now
PagerDuty is rolling out a redesigned Incidents page with status badges and an updated grid view. The update improves bulk actions for setting priorities, adding notes, and assigning responders, and allows inline workflow execution.
Also shipped Nov 13, 2026PagerDuty in November 2026 →
AI Function task support in Declarative Automation Bundles (Beta)
Databricks introduced Beta support for AI Function tasks within Declarative Automation Bundles.
Give agents only the access they need
Buildkite released token permissions and queue scopes for agent tokens, allowing teams to restrict agent capabilities and limit job acceptance to specific queues.
Many-to-many relationships in semantic views (Preview)
Snowflake Cortex AI launched a public preview for modeling many-to-many relationships between logical tables within semantic views.
BigQuery connections for MySQL, Oracle, and PostgreSQL are in preview
Google Cloud introduced BigQuery federated query connections to MySQL, Oracle, and PostgreSQL in public preview.
Upcoming deprecation of selected GitHub Copilot models in December
GitHub announced the upcoming deprecation of several Copilot models on December 14, 2026, including Claude Fable 5, Gemini 3.8 Flash, and Grok 4.6.
Aurora PostgreSQL with express configuration now supported in CloudFormation
AWS added support for Aurora PostgreSQL express configuration in CloudFormation, enabling single-property automated cluster creation and faster serverless database setup.
More from PagerDutyEvery PagerDuty release →
New Resolution Reason field in the Resolution Form now rolling out to customers
Record why an incident was closed, such as Duplicate, False Positive / Non-Issue, or Solved (Permanently), in a new optional field on the resolution form. Filter by it in the Operations Console and PD Reliability Console to spot noise, and give Paige, PagerDuty’s SRE Agent, structured data to tell noise from real fixes.
Postmortems End of Life Completed
The Postmortems feature has been retired in favor of the upgraded Post-Incident Reviews in the PagerDuty web UI.
UI improvements now generally available for PD Reliability Platform customers
Customers on PD Reliability Platform now have an improved UI experience, including: Consolidated settings: Brings all your configuration and admin settings together in one place. New nav: Provides streamlined access to your most important capabilities. Your Subscription: Shows where the opportunities are to shift work off humans and onto AI and automation.
Claude auto-connect (beta) for PagerDuty MCP Server now in Early Access
With Claude auto-connect, members with a matching PagerDuty account are connected to PagerDuty in Claude automatically, with no sign-in screen and no identity provider (IdP) configuration. Members act as themselves in PagerDuty, with the permissions they already have there.
End of Life: Amazon Q Business integration for PagerDuty Advance
The PagerDuty Advance integration with Amazon Q Business will be retired on December 8, 2026. The integration will be removed from the UI and associated Slack and Microsoft Teams commands will cease to function.
Post-Incident Reviews Public API now Generally Available
The Post-Incident Reviews REST API is now generally available, allowing users to programmatically list, create, update, and fetch incident review data. It supports filtering by status and action items for integration with external tools.
Postmortems End of Life: Transition to Post-Incident Reviews by October 31, 2026
PagerDuty Postmortems will reach end of life on October 31, 2026. Users are encouraged to transition to the new Post-Incident Reviews capability.
AI-Powered Incident Communications Generally Available now
AI-Powered Incident Communications is now generally available. The SRE Agent coordinates communications in Slack, while the Scribe Agent captures discussions to generate AI drafts for status pages.