Skip to content

v0.15.0-dev.1

v0.15.0-dev.1: Release 0.15.0: ORM family to 8.0.0-rc.8, engine to 0.3.0 (#263)
@wmadden-electric wmadden-electric tagged this 26 Aug 08:47 
* Move the ORM family to 8.0.0-rc.7

The pins sat at rc.4 while the Prisma CLI moved to 8.0.0-rc.10, whose
starter schemas use field types rc.4 rejects. Any project holding
composer-prisma-cloud was pinned to rc.4 through its exact peer, so it
could not use the current CLI at all.

Every @prisma/orm-* spec moves together, as check:orm-pins requires:
the target extension, the auth module, the public composer-prisma-cloud
package (dependency, peer, and dev), and the four examples.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* Migrate the examples and the auth pack to the rc.7 ORM API

The rc.4 -> rc.7 move is an API migration, not a pin bump (the four
blocking findings on #263):

- .take(n) is gone from the collection API; orders now uses .limit(n).
- ORM rc.6 retired the pg/timestamptz@1 codec. Columns respell to
  TimestamptzString (text representation, no Temporal polyfill; the same
  choice the CLI's own scaffold makes): orders' placedAt and the auth
  pack's Tstz alias. Ordering methods came back once the contracts were
  re-emitted against the installed codec table.
- The CLI reads prisma.config.ts and never read prisma-next.config.ts
  (the rc.4 hard cut), so 'prisma contract emit' in an example failed
  with CLI.CONFIG_SECTION_INVALID. The examples' ORM configs are renamed
  to prisma.config.ts; the deploy still loads them by explicit path from
  pnPostgres. The auth pack's dead flat-shape anchor is replaced by an
  envelope-shape one beside the pack sources.
- Every contract is re-emitted. pn-widgets, catalog, and the auth app
  space keep their storage hashes, so their committed migrations stand.
  orders and the auth pack change hash: their baselines are re-authored
  (the pack's ops SQL is byte-identical), examples/auth's auth space is
  re-materialised, and the committed snapshots are refreshed.

Typecheck, lint, cast ratchet, orm-pin and contract-snapshot lints, and
the full test suite (integration included) pass locally.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* Keep the examples' ORM config named prisma-next.config.ts

The standalone prisma-composer bin also discovers prisma.config.ts, and
its engine mounts only the composer section — an orm key there fails
deploy with CLI.CONFIG_UNKNOWN_SECTION (the pn-widgets E2E job caught
it). Only the unified prisma CLI recognises both sections, so in this
repo, where examples deploy through the standalone bin, the ORM config
keeps its own filename. Re-emitting works via the CLI's --config flag;
each config now names the command.

User-facing docs keep prisma.config.ts: scaffolded projects deploy
through the unified CLI, where one file carries both sections.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* chore(release): v0.15.0 — ORM family to 8.0.0-rc.8, engine to 0.3.0

Moves every @prisma/orm-* pin from 8.0.0-rc.7 to 8.0.0-rc.8 and every @prisma/cli-engine pin from 0.2.3 to 0.3.0 — rc.8 of the ORM peers engine 0.3.0, so they move together. The engine now declares @prisma/management-api-sdk as a peerDependency (^1.55.0) instead of a dependency; the workspace resolves it to 1.60.0 and consumer installs get it from the hosting prisma shell.

pnpm bump-minor advances the workspace to 0.15.0 and regenerates the lockfile. The rc.7-emitted contracts carry over unchanged: emitted artifacts do not embed the ORM version, and rc.8's changes over rc.7 are the engine pin and skill/docs fixes.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* Date the descriptor-narrowing notes instead of pinning them to rc.7

The pn-config comments read as if the rc.7 pin were still current. They describe behavior that arrived in orm-toolchain 8.0.0-rc.7 and persists in rc.8, so they now say "since 8.0.0-rc.7" and the cast label drops the version entirely — rewriting them to rc.8 would misstate when the API changed.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

---------

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Assets 2
Loading