feat(v2): Phase 2 — records (schema-version-pinned rows, validated bulk-upsert, references view)#227
Merged
Conversation
Also surfaces the specific 'No record IDs provided' 422 on empty delete ids (roborev job 70: the post-parse length check was unreachable).
…itions and record write process - Clarified table names and purposes for `schemas`, `schema_versions`, and `v2_records`. - Enhanced the description of the record write process, emphasizing validation and error handling. - Updated API endpoint descriptions for schemas, schema versions, and records to reflect recent changes.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 2 of 6 — v2 Records
Rebased onto
developafter Phase 1 (#219) squash-merged. Contains only Phase 2 (records) — Phase 1 commits dropped as already-upstream, so this is a clean, conflict-free squash.Adds the v2
recordentity — one typed row pinned to aschema_version, carrying the cross-schemareferencejoin key and Pandera-validatedfieldsJSONB:V2RecordORM (v2_records) +V2RecordStatusenum + alembic migration (chains onto Phase 1's9f3010c649c8)POST /api/v2/schemas/{id}/records:bulk-upsert, all-or-nothing 422), paginated list, bulk deleteGET /api/v2/references/{reference:path}cross-schema document viewSchemaPolicyPlan:
docs/superpowers/plans/2026-07-03-v2-records.md. 55 v2 tests green.