chore(provision): bump node-type-registry@0.16.0 + drop SpatialRelationEntry cast#26
Merged
pyramation merged 1 commit intomainfrom Apr 18, 2026
Merged
Conversation
…ode@0.10.1, drop SpatialRelationEntry cast
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
4 tasks
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
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.
Summary
Consumes the RelationSpatial type fix from constructive-io/constructive#1001 (published as
node-type-registry@0.16.0+@constructive-io/node@0.10.1):packages/provision/package.json— bumpnode-type-registry^0.14.0→^0.16.0,@constructive-io/node^0.10.0→^0.10.1.packages/worker/package.json— bump@constructive-io/node^0.10.0→^0.10.1.packages/provision/src/schemas/spatial-relations.ts— drop the localSpatialRelationEntryinterface +as unknown as BlueprintRelation[]cast. The 5 entries now type directly againstBlueprintRelationbecause0.16.0exposessource_field/target_fieldon theRelationSpatialarm of the discriminated union.pnpm-lock.yaml— regenerated for the bumps.No runtime / provisioning logic changes. The 5
RelationSpatialentries are byte-identical; only the surrounding TypeScript typing got tighter.Review & Testing Checklist for Human
pnpm export:allhere because (a) it requires the live Constructive cnc platform server (auth.localhost:3000 + api.localhost:3000), which isn't running in my environment, and (b) PR #25 was a pure refactor — the resultingpackages/agentic-dbpgpm module and derived SDK/CLI are byte-identical to what's onmaintoday. If you want me to prove that by actually running the full cycle on a machine with the cnc stack up, say the word and I'll do it as a follow-up.@constructive-io/node@0.10.1bump is safe forpackages/worker(graphile-workerbackground job runner) — I only verified it transitively compiles; I did not exercise the worker itself.packages/provision/src/schemas/spatial-relations.tsno longer usesas unknown as BlueprintRelation[]; it typechecks directly against0.16.0's generatedBlueprintRelationunion.Test plan
pgpm deploy --package agentic-db --database agentic_db_test→cd packages/integration-tests && pnpm test:orm→ 36/36 passed (same as PR refactor(provision): cross-relations via provisionBlueprint() (drop raw SQL) #25 baseline).pgpm deploy+ Jest flow against a freshconstructiveio/postgres-plus:18service container. Confirm 7/7 green.Notes
node-type-registry@0.16.0).src/blueprint.tstsc errors aroundref/source_ref/target_refare unchanged — same state asmain, unrelated to this PR.Link to Devin session: https://app.devin.ai/sessions/c5eeee65a3c546c4ac6753bb05fa03e0
Requested by: @pyramation