# prisma/release
Prisma v8.0.0-rc.6
importance: highbreakingmigrationfeatureprerelease
This release introduces breaking changes for PostgreSQL temporal columns and agent skills setup, while adding the prisma-8 skill to npm tarballs.
affected
Users of PostgreSQL temporal columns and those relying on `prisma orm init` for agent skills setup are affected.
action
Follow the migration recipe for PostgreSQL temporal columns and update to `@prisma/cli-engine@0.2.2`.
release_signals
-PostgreSQL temporal columns now use explicit `Temporal` or text representations instead of `Date`. Users must choose a representation per column and re-emit contracts.
-`prisma orm init` no longer installs agent skills; this functionality is moved to the family-level `prisma init` command.
-The engine peer dependency has been updated to `@prisma/cli-engine@0.2.2`, which includes fixes for pnpm symlink layouts and CI detection.
+The prisma-8 skill is now included in npm tarballs (`@prisma/orm-postgres`, `@prisma/orm-sqlite`, `@prisma/orm-mongo`), allowing `prisma skills sync` to detect staleness from installed packages.
migration_steps3 steps
- 01Choose a representation (`Temporal` or text) for each PostgreSQL temporal column and re-emit contracts.
- 02Update to `@prisma/cli-engine@0.2.2` if manually pinned.
- 03Use `prisma init` instead of `prisma orm init` for agent skills setup.
code_snippet
Before:
```prisma
occurredAt Timestamptz // read as Date
```
After (read as `Temporal.Instant`):
```prisma
occurredAt Timestamptz
```
Or, to keep PostgreSQL's text unchanged:
```prisma
occurredAt TimestamptzString
```# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.