Today's Trends
minorInvestigatingPrismav8.0.0-rc.15

prisma/prisma v8.0.0-rc.15: breaking changes

  1. Investigating(current)
  2. Trending(upcoming)
  3. Workaround available(upcoming)
  4. Resolved(upcoming)

Executive summary

The upgrade recipes for prisma v8.0.0-rc.15 include breaking changes such as the removal of nativeType in favor of dataType for SQL column data types, affecting applications that use these recipes to migrate from previous versions.

No verified workaround yet

None of the linked reports describe a mitigation. Follow this incident to hear when one appears.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

3 reports · 3 GitHubShow
  1. [1]
    GitHub First report
    prisma/prisma v8.0.0-rc.15: breaking changes(opens GitHub issue in a new tab)

    The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change id to look for in them. Run the data-type-in-contract script (change contract-stores-data-type) before any other step that emits a contract again. Breaking changes A contract column stores its data type id, not its database type name. A SQL column in contract.json now stores dataType, for example pg/int4, where it stored nativeType, for example int4. A contract in the old…

    by github-actions[bot] 0upvotes 0comments

  2. [2]
    GitHub
    prisma/prisma v8.0.0-rc.16: breaking changes(opens GitHub issue in a new tab)

    The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change id to look for in them. Breaking changes The toolchain requires @prisma/cli-engine 0.6.3. A project or extension that pins @prisma/cli-engine itself must move the pin from 0.6.2 to 0.6.3. The engine's commands and output do not change: its only change is that it accepts ArkType ^2.2.7 instead of exactly 2.2.3. See engine-pin-moves-to-0-6-3 in the app recipe and the extension…

    by github-actions[bot] 0upvotes 0comments95% match

  3. [3]
    GitHub
    prisma/prisma v8.0.0-rc.17: breaking changes(opens GitHub issue in a new tab)

    The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them. Breaking changes --confirm no longer consents to data loss. prisma migration plan and prisma db update ask one question for each model, field or table a plan would lose data from, before they write or apply anything. Answer with --delete <subject> to let the data go, or --rename <old>:<new> to keep it. db update also asks before an operation that…

    by github-actions[bot] 0upvotes 0comments96% match

Timeline

  1. First report on GitHub issue

    prisma/prisma v8.0.0-rc.15: breaking changes

    Source