fix(update): supervised PostgreSQL updates ignore server recovery captures and orphan them on finish (#198469) * fix(update): honor server recovery captures in supervised migrations * fix(update): retire supervised PostgreSQL recovery captures Retire PostgreSQL schema captures through the existing snapshot owner before removing supervised update backup manifests. Keep cleanup best effort: preserve the directory on discard failure, warn, and allow update finish to retry. Cover ordered retirement, failure and retry through the real finish command, plus a skip-gated PostgreSQL migrate-to-finish lifecycle case. Rolled-back receipts retain their captures under the existing recovery policy. Co-authored-by: steipete <58493+steipete@users.noreply.github.com> Co-authored-by: qingminglong <qing.minlong@xydigit.com> --------- Co-authored-by: qingminglong <qing.minlong@xydigit.com> Co-authored-by: steipete <58493+steipete@users.noreply.github.com>
fix(update): supervised PostgreSQL updates ignore server recovery cap…
Find Your Interest
- Sentry JavaScript SDK v11 adds tracing for all JS platforms
- Keeping it Bref: Sentry now supports PHP on AWS Lambda
- Measuring soft navigation web vitals
- Add Runtime Controls to AI Agents with NVIDIA OpenShell
- Building Sentry's Laravel AI Integration
- How to detect AI agents and AI assistants
- Seer, the Sentry MCP and CLI, or your own coding agent: where each one fits
- Sentry's .NET SDK 7.0 is ready for .NET 11
- How a broken release name overloaded our symbolication database
- Finding performance wins in our own traces with a coding agent





