video1.0<iframe src="https://www.loom.com/embed/744d191eab8749d18d0d0a5ef19aa319" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/744d191eab8749d18d0d0a5ef19aa319-95c37a0b1d170107.gif115.265This Loom explains the unexpected scope of a Superbase and Vercel update and the related code changes required. The author describes how updating Superbase versions and addressing post hoc items became complex due to multiple uses of CreatePostgresError, a changed function signature requiring a success field, and the need for error handling to use a bona fide PostgresError object via an import rather than a plain dictionary. They also mention that upsert type checking failed and, despite extensive type changes to improve the code, they separated the work to avoid an unrelated massive PR. Overall, the remaining work is what the author outlines at the end of the message.