4.0.7

Aug 05, 2026 · 4 packages · 7 unique changes · 1 release entry

appslibsBreaking changes

This release affects the contracts, sharedLibs, solutions familyies.

Run contractspec connect adoption resolve --family contracts to see how it impacts your project.

Release summaries

drizzle-postgresql-database-platform
Migrate ContractSpec database workflows to contract-source-first Drizzle/PostgreSQL and retire supported Prisma-facing surfaces for the major release.
integrator
Database authoring now starts from portable ContractSpec schema/contracts and emits Drizzle PostgreSQL artifacts instead of supported Prisma schema/client workflows.
maintainer
Database contract metadata, migration provenance, CLI workflows, and release checks must be reviewed as a coordinated breaking migration with no Prisma compatibility shim.
customer
Prisma-specific GraphQL/database support is entering phase-1 retirement; future database integrations should target the portable database model and Drizzle/PostgreSQL adapter path.

Deprecations

- @lssm-tech/lib.graphql-prisma is marked for phase-1 retirement; do not delete the workspace until npm deprecation evidence is recorded.
- Supported Prisma-facing database generation, migration, and documentation workflows are retired in favor of contract-source-first Drizzle/PostgreSQL workflows.

Migration guide

Replace Prisma schema authoring with portable database contracts
Required
Move database source definitions to the portable ContractSpec schema/contracts model and generate Drizzle PostgreSQL artifacts from that source.
When: When code imports Prisma-named entity/generator APIs or writes Prisma schema files through ContractSpec database workflows.
1. Replace Prisma-named public entity/generator APIs with Database-named portable model APIs.
2. Generate Drizzle PostgreSQL schema artifacts from the portable source before invoking CLI database workflows.
3. Review generated artifacts for PostgreSQL target metadata and relation/index coverage.
Replace Prisma delegated CLI workflows
Required
Stop relying on ContractSpec CLI commands that delegate to Prisma and use the Drizzle/PostgreSQL-backed database commands instead.
When: When scripts call database generate, migrate, check, seed, or schema composition commands from the old Prisma workflow.
1. Update database config files to the new database.config.ts and drizzle.config.ts conventions.
2. Point schema output to ./drizzle/schema.ts and migration output to ./drizzle/migrations.
3. Run deterministic dry-run migration checks when no real PostgreSQL DATABASE_URL is available.
Retire Prisma-specific GraphQL package usage
Required
Treat @lssm-tech/lib.graphql-prisma as retired for new database platform work and plan a separate portable GraphQL/database adapter if needed.
When: When an app or bundle depends on @lssm-tech/lib.graphql-prisma for the migrated database path.
1. Avoid adding new imports from @lssm-tech/lib.graphql-prisma.
2. Record npm deprecation evidence before any repository deletion is attempted.
3. Use the portable database model as the integration boundary for future GraphQL work.

Upgrade steps

Verify the Drizzle/PostgreSQL vertical slice
assisted
Validate schema generation, contracts-spec v2 registration, CLI dry-run or PostgreSQL migration behavior, and one example/app adoption proof.
Packages: @lssm-tech/lib.schema, @lssm-tech/lib.contracts-spec, @lssm-tech/app.cli-database, @lssm-tech/lib.graphql-prisma, contractspec
1. Run focused lib.schema generator tests after portable database API changes.
2. Run focused lib.contracts-spec database and migration tests after contract versioning changes.
3. Run CLI database generation/migration checks with DATABASE_URL or a documented dry-run gap.
4. Run the no-supported-Prisma grep gate before release readiness.

Unique release changes

- @lssm-tech/lib.graphql-prisma is marked for phase-1 retirement; do not delete the workspace until npm deprecation evidence is recorded.
4 packages · 4 occurrences
- Migrate ContractSpec database workflows to contract-source-first Drizzle/PostgreSQL and retire supported Prisma-facing surfaces for the major release.
4 packages · 4 occurrences
- Move database source definitions to the portable ContractSpec schema/contracts model and generate Drizzle PostgreSQL artifacts from that source.
4 packages · 4 occurrences
- Stop relying on ContractSpec CLI commands that delegate to Prisma and use the Drizzle/PostgreSQL-backed database commands instead.
4 packages · 4 occurrences
- Supported Prisma-facing database generation, migration, and documentation workflows are retired in favor of contract-source-first Drizzle/PostgreSQL workflows.
4 packages · 4 occurrences
- Treat @lssm-tech/lib.graphql-prisma as retired for new database platform work and plan a separate portable GraphQL/database adapter if needed.
4 packages · 4 occurrences
- Validate schema generation, contracts-spec v2 registration, CLI dry-run or PostgreSQL migration behavior, and one example/app adoption proof.
4 packages · 4 occurrences

Impacted packages

@lssm-tech/app.cli-database
Layer: apps · 7 changes
@lssm-tech/lib.contracts-spec
Layer: libs · 7 changes
@lssm-tech/lib.graphql-prisma
Layer: libs · 7 changes
@lssm-tech/lib.schema
Layer: libs · 7 changes