note: la síntesis y las notas de la versión están en inglés
note: sin síntesis para esta release más antigua
Sintetizamos las releases recientes. Las notas de la versión originales de esta versión están aquí abajo.
release-notesgithub.com/prisma/orm · 34 líneas
- # v8.0.0-rc.6
- PostgreSQL temporal columns move from `Date` to explicit `Temporal`-or-text representations, the prisma-8 agent skill ships inside the ORM packages a project installs, `prisma orm init` hands agent-skills setup to the family-level `prisma init`, and the toolchain releases against `@prisma/cli-engine@0.2.2` — the engine that evaluates `prisma.config.ts` correctly under pnpm symlink layouts.
- The upgrade recipe for this hop: the [user recipe](https://github.com/prisma/prisma/tree/v8.0.0-rc.6/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.5-to-8.0.0-rc.6/).
- ## Breaking changes
- - **PostgreSQL temporal columns read as `Temporal` values or text, never `Date`** — each of `date`, `timestamp(p)`, `timestamptz(p)` and `time(p)` now has two representation-explicit codecs: a `Temporal`-backed one (the bare PSL spellings `Date`, `Timestamp`, `Timestamptz`, `Time` select it) and a text one (`DateString`, `TimestampString`, `TimestamptzString`, `TimeString`). The previous codecs (`pg/date@1`, `pg/timestamp@1`, `pg/timestamptz@1`, `pg/time@1`, `sql/timestamp@1` / `field.timestamp()`) are removed with no aliases. Pick a representation per column, re-emit every contract, and provide a global `Temporal` implementation (e.g. `import 'temporal-polyfill/full/global'`) wherever a Temporal-backed column is read. See the [migration recipe](https://github.com/prisma/prisma/tree/v8.0.0-rc.6/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.5-to-8.0.0-rc.6/). ([#30073](https://github.com/prisma/prisma/pull/30073))
- 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
- ```
- - **`prisma orm init` no longer installs agent skills** — the GitHub fetch (`npx skills add`) is removed and nothing replaces it inside `orm init`: agent-skills setup belongs to the family-level `prisma init` command, which init's next-steps now point to. The `--skip-skills` flag is removed with the behavior it opted out of, and the skill-install failure exit (code 6) is retired. Scaffolding is otherwise unchanged. ([#30097](https://github.com/prisma/prisma/pull/30097))
- - **The engine peer moves to `@prisma/cli-engine@0.2.2`** — `@prisma/orm-toolchain` declares the unified CLI's engine as an exact peer, and this release peers 0.2.2 (up from 0.2.0). Installs assembled by the unified `prisma` CLI resolve one engine as before; a host that pins the engine itself must move to 0.2.2. The new engine evaluates `prisma.config.ts` through pnpm symlink layouts that are not realpath'd ([prisma/prisma-cli#222](https://github.com/prisma/prisma-cli/pull/222)) and exports its CI detector ([prisma/prisma-cli#224](https://github.com/prisma/prisma-cli/pull/224)).
- ## Features
- - **The prisma-8 skill travels in the npm tarballs** — `skills/prisma-8/` ships inside `@prisma/orm-postgres`, `@prisma/orm-sqlite`, and `@prisma/orm-mongo`, stamped with the package name and version so `prisma skills sync` can copy it into agent harness directories and detect staleness from the installed packages rather than fetching from GitHub. The two upgrade skills fold into the prisma-8 router as its "upgrading" branch. ([#30096](https://github.com/prisma/prisma/pull/30096))