Skip to content

v1.52.0

Choose a tag to compare

View all tags
@tstirrat15 tstirrat15 released this 30 Apr 15:50
v1.52.0
76fc153
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's changed

Added

  • Added support for YAML-based validation files in DevContext (#3024)
  • Added support for YAML-based validation files in the Language Server (#3024)
  • Enable statistics-based optimizations when --experimental-query-plan is enabled. (#3052)
  • Added missing implementations of cursoring for LookupResource, LookupSubjects and ReadRelationships calls in FDW (#3016)
  • Add new gRPC Dispatch API and messages for dispatching query plans (#3072)
  • Support new withDebug flag in LookupResources calls to identify cycles (#3070)

Changed

  • Removed MySQL metrics prefixed with go_sql_stats_connections_* in favor of those prefixed with go_sql_* (#2980)
  • Removed support for Spanner flag value --datastore-spanner-metrics=deprecated-prometheus; please use values otel or native (#2980)
  • Reduced binary size (#3005)
  • Reduce memory consumption of Watch API (#2578)

Fixed

  • Improved error message when expiration is written before caveat in a relationship (#3071)
  • On a Postgres setup with read replicas, some requests may silently swallow errors of sort "revision not found in replica" (#2979)
  • Use cgroup-aware memory detection for cache and watch buffer sizing in containerized environments (#3000)
  • Upgraded the spanner client, which changed the internal implementation to not use a session pool. This means that the --datastore-spanner-max-sessions and --datastore-spanner-min-sessions flags are now deprecated and no-op. We also strongly recommend using Application Default Credentials in favor of a credentials file. (#3038)
  • Query Planner: error "ERROR: index \"pk_relation_tuple\" cannot be used for this query (SQLSTATE 42809)" returned when using wildcards (#3039)
  • Providing one of (--grpc-tls-cert-path, --grpc-tls-key-path) but not the other is now considered an error state, as both are necessary if you want to use TLS.
  • In a caveat context that uses nested lists of lists, the hashes generated for cache keys could collide because of an issue with the serialization logic. The serialization now uses deterministic protobuf serialization which avoids this issue (#3065)
Assets 16
Loading