zeekayandHanzo Dev 1223f1dc5f Relock against the catalog the manifests already declare ...

The lockfile was last regenerated before the move to catalogs, so it
still carried literal specifiers and a resolution a year behind the
manifests. Frozen installs refused on the overrides mismatch; a fresh
install then stopped outright, because package.json asks for
@hanzo/design and @hanzo/logo from the catalog and neither had an entry.
Give them one, at the versions already installed.

The one range that did not say what it meant is prisma. A caret on a
release candidate had walked the CLI to 8.0.0-rc.15, which drops the
generate command altogether, while @prisma/client and @prisma/adapter-pg
stayed on 7.10.0. Pin the CLI to the same 7.10 line so the three agree
and build-db runs again. Prisma 7 reads the connection URL from
prisma.config.ts, which already holds it, so the datasource block no
longer needs its own url.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-17 01:15:45 -07:00

..

migrations

merge: upstream/master (preserve Hanzo brand, 6048 commits)

2026-06-02 09:37:35 -07:00

schema.prisma

Relock against the catalog the manifests already declare

2026-09-17 01:15:45 -07:00