Supabase .NET DevLog #6: Progress Toward v8.0.0
Catch up with the latest Supabase .NET SDK DevLog #6, featuring v8.0.0 preparation, approval tests, and quality gates.
Stock photo for illustration only, not from the actual event
- Development on major version v8.0.0 begins following the monorepo migration.
- A full suite of approval tests is implemented to secure the upcoming serialization changes.
- New automated quality gates via GitHub Actions ensure codebase standards do not degrade.
The weekly development log for the Supabase .NET SDK is back with DevLog #6. Following the completion of the monorepo migration, work has officially kicked off toward the upcoming major release v8.0.0. Developers interested in following what is coming in this new version can review the ongoing Pull Request.
Prior to migrating to System.Text.Json, a comprehensive suite of approval tests was implemented to guarantee that data serialization remains completely unchanged. Because the existing codebase lacked these safety nets, tackling such a major structural migration without them was simply not an option.
Stock photo for illustration only, not from the actual event
For those wondering how approval tests function, the process involves capturing a snapshot and continuously evaluating subsequent outputs against that exact snapshot. This mechanism ensures that data models and queries consistently produce the exact same output without unexpected alterations.
Approval testing plays a vital role when overhauling core serialization frameworks in software projects. By asserting outputs against known snapshots, developers protect against silent breaking changes when switching underlying libraries like System.Text.Json.
In addition to testing, a dedicated quality gate was established for the SDK. Executed via GitHub Actions and local agents, this script-based gate is entirely deterministic, ensuring that codebase health either improves or remains steady over time.
Moving forward, this quality gate functions as a strict prerequisite for all contributions, including those from the core maintainers. It effectively enforces the traditional boy-scout rule across the entire codebase to maintain high standards.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment