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

1.1.2 (2018-01-30)

Compare
Choose a tag to compare
@timsuchanek timsuchanek released this 30 Jan 16:48
· 9295 commits to master since this release

Prisma 1.1.2 (2018-01-30)

CLI

  • 04c3252 fix(docker-compose): Add ENABLE_METRICS & JAVA_OPTS env vars. Setting JAVA_OPTS to -Xmx1G limits the memory usage of the prisma container to 1GB. If you host Prisma on your own, you need to adjust the docker-compose file like in the commit.
    ENABLE_METRICS enables/disables statsd metrics.
  • 544e053 fix(docker): Make cluster version dynamic
  • e2381ef fix(playground): The playground now uses graphql playground under the hood, to provide a nice experience, even if you don't have the GraphQL Playground App installed
  • 1fdb10f fix(import): Replaced the unzip library with a modern one
  • 4dd0398 fix(import): Fix import of Json fields
  • e8b9b82 feat(auth): Added PRISMA_CLOUD_SESSION_KEY env var support - can be used for auth, useful in CI environments
  • cf084f2 feat(import): Allow import of directories
  • f000309 fix(list): List runs without being logged in, though shows note that you can log in to see all services
  • 037e74a fix(local): Better handling when 3306 is already in use
  • dacac2c feat(deploy): Better .graphqlconfig resolution - now also searches in parent dir
  • 5b8cc06 fix(login): Fix --key parameter

Server

  • We fixed an issue where setting ScalarListValues within nested mutations was not always properly executed. While doing this we also discovered and fixed an issue with the Float datatype on ScalarListValues.
  • We improved the validation of relations employed in the new and more expressive nested mutations. Connecting, disconnecting, deleting or creating a node using a nested mutation should now always properly reject changes that would violate the integrity of the schema and automatically disconnect other relations where necessary and possible.
  • Self-relations are now properly supported, as discussed in this issue.