Skip to content

chore(provision): bump node-type-registry@0.16.0 + drop SpatialRelationEntry cast#26

Merged
pyramation merged 1 commit intomainfrom
devin/1776494679-regen-blueprint-types
Apr 18, 2026
Merged

chore(provision): bump node-type-registry@0.16.0 + drop SpatialRelationEntry cast#26
pyramation merged 1 commit intomainfrom
devin/1776494679-regen-blueprint-types

Conversation

@pyramation
Copy link
Copy Markdown
Contributor

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 — bump node-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 local SpatialRelationEntry interface + as unknown as BlueprintRelation[] cast. The 5 entries now type directly against BlueprintRelation because 0.16.0 exposes source_field/target_field on the RelationSpatial arm of the discriminated union.
  • pnpm-lock.yaml — regenerated for the bumps.

No runtime / provisioning logic changes. The 5 RelationSpatial entries are byte-identical; only the surrounding TypeScript typing got tighter.

Review & Testing Checklist for Human

  • No SDK/CLI regeneration in this PR. You mentioned "we need to generate the code with the new blueprint / new codegen, new CLI." I did not run pnpm export:all here 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 resulting packages/agentic-db pgpm module and derived SDK/CLI are byte-identical to what's on main today. 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.
  • Confirm the @constructive-io/node@0.10.1 bump is safe for packages/worker (graphile-worker background job runner) — I only verified it transitively compiles; I did not exercise the worker itself.
  • Sanity-check the dropped cast: packages/provision/src/schemas/spatial-relations.ts no longer uses as unknown as BlueprintRelation[]; it typechecks directly against 0.16.0's generated BlueprintRelation union.

Test plan

  1. ✅ Local: pgpm deploy --package agentic-db --database agentic_db_testcd packages/integration-tests && pnpm test:orm36/36 passed (same as PR refactor(provision): cross-relations via provisionBlueprint() (drop raw SQL) #25 baseline).
  2. CI: the Integration Tests workflow runs the same pgpm deploy + Jest flow against a fresh constructiveio/postgres-plus:18 service container. Confirm 7/7 green.

Notes

  • Upstream type fix: constructive-io/constructive#1001 (merged, published as node-type-registry@0.16.0).
  • The pre-existing src/blueprint.ts tsc errors around ref / source_ref / target_ref are unchanged — same state as main, unrelated to this PR.

Link to Devin session: https://app.devin.ai/sessions/c5eeee65a3c546c4ac6753bb05fa03e0
Requested by: @pyramation

@devin-ai-integration
Copy link
Copy Markdown

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@pyramation pyramation merged commit 496cf0c into main Apr 18, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant