Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Releases: prisma/prisma1

Release 1.26.2 (2019-02-07)

07 Feb 09:28
Compare
Choose a tag to compare

Fixes

  • ff6ae93 fix(go-client): handle empty secret env interpolation #4013

Release 1.26.1 (2019-02-06)

06 Feb 15:44
e4f50c8
Compare
Choose a tag to compare

Fixes

  • 1d140f2 fix(go-client): do not call replaceEnv twice (#4009)

Release 1.26.0 (2019-02-05)

06 Feb 15:40
e4f50c8
Compare
Choose a tag to compare

Features

  • 7fb441c Isomorphic Introspection/Type and Field name Normalization
  • the executeRaw mutation now supports Postgres Arrays prisma/prisma#3930

Fixes

  • 703feb9 CLI/Generate Schema: Update client schema gen to 1.26-beta (#4001)
  • 7928f41 fix(deploy): check symmertric secret for non-public servers

Release 1.27.0-Beta (2019-02-05)

05 Feb 17:40
Compare
Choose a tag to compare
Pre-release

Changes

Fixes

  • Embedded types are now no longer part of the subscription schema. It was possible to define subscriptions on embedded types. These would then error at runtime since subscribing to them is not actually possible. This now errors at deploy time.
  • f3025ef The CLI introspection now works without a prisma.yml
  • a2aad8b Many Introspection improvements, we're now fully matching the actual Prisma datamodel of a service when reintrospecting that service
  • ae34b80 fix(cli): inform about legacy id column, add help for @unique -> @id
  • 1306da8 add support for Datamodel v1 to v1.1 changes
  • b0a3c63 fix(cli): deploy warnings

Release 1.25.7 (2019-02-02)

02 Feb 15:51
ee81b68
Compare
Choose a tag to compare

Fixes

  • Resolving embedded types could lead to an internal server error.
    #3981

Release 1.25.6 (2019-02-01)

01 Feb 15:47
831ff02
Compare
Choose a tag to compare

Fixes

  • Having two unnamed relations on different types whose autogenerated relation names are too long for the db could lead to an internal server error when the resulting shortened names were identical.
    #3971

Release 1.25.5 (2019-02-01)

01 Feb 14:20
821a92d
Compare
Choose a tag to compare

Fixes

  • The generated GraphQL schema was invalidated before the migration was actually applied. This validation used to happen when the migration was scheduled. This could lead to stale schemas in case of larger migrations. #3970
  • Renaming a type that has scalar list fields resulted in the underlying db table for the list field being moved instead of being renamed.
    #3952

Release 1.25.4 (2019-01-28)

28 Jan 12:56
Compare
Choose a tag to compare

Fixes

  • c3a7afe fix(client): do not apply non-scalar sub selection opinion to non object types #3941

Release 1.25.3 (2019-01-24)

24 Jan 12:54
Compare
Choose a tag to compare

Fixes

  • f33adaa fix(deploy): check migration steps for backward compatability #3923

Release 1.25.2 (2019-01-24)

24 Jan 10:25
Compare
Choose a tag to compare

Fixes