YOJ 2.3.0 (Delete repository-ydb-v1, Native mapping for UUID)

⚠️ Breaking changes

• yoj-repository-ydb-v1 module is no more. Please use yoj-repository-ydb-v2 which is mostly source code compatible, except for minor changes in YdbConfig and different YDB SDK imports in custom YqlStatements
• tech.ydb.yoj.databind.expression.FieldValue.Tuple API has changed, and is subject to change in subsequent versions of YOJ. This type is not directly used by end-user code, as far as we know

---

• #71 Native mapping for java.util.UUID
• #74 Delete deprecated yoj-repository-ydb-v1 module

YOJ 2.2.19 (less radical deprecation warnings #2)

• #70: Less radical deprecation warnings for Id.resolve()

YOJ 2.2.15-2 (backport less radical deprecation warnings no. 2)

• Backport less radical deprecation warnings for Id.resolve() (#70)

YOJ 2.2.15-1 (backport less loud deprecation warnings)

Backport to 2.2.15 (w/older Jackson dependency):

• Show warnings about @Deprecated(forRemoval=true) methods only once per JVM invocation, and only using WARN log level

YOJ 2.2.18 (less radical deprecation warnings)

• Show warnings about @Deprecated(forRemoval=true) methods only once per JVM invocation, and only using WARN log level

YOJ 2.2.17 (Jackson update)

Please use this release instead of 2.2.16.

• Update Jackson to 2.17.1 which has important KotlinModule fixes

YOJ 2.2.16 (dependency updates)

⚠️ Not recommended for Kotlin users! Jackson 2.17.0 has serious regressions in its KotlinModule. This module is not enabled in JacksonJsonConverter.getDefault() but is typically enabled by Kotlin users of YOJ.

Please use version 2.2.17 instead.

• Bump Jackson 2.16.1->2.17.0 and AssertJ 3.25.1->3.25.3 (081ec6b)

YOJ 2.2.15 (API fix)

• #64: API FIX: Reinstate FieldValue.of{Str,Num,Timestamp, ...} methods as public.
  These methods offer explicit typing of FieldValues, in contrast to the loosely typed FieldValue.ofObj(Object, JavaField).
  In contrast, FieldValue.ofObj() assumes that the value supplied is a valid field value, and applies the JavaField's custom value type ValueConverter to it, if it is defined. Some ValueConverters, most notably StringValueConverter, accept any Object when converting Java value to DB column value; this coerces user-supplied value to a String even if it was not intended to be used in that way.

YOJ 2.2.14 (more minor fixes)

• 92f99af - ydb-repository-v2: Don't use Guava Suppliers.memoize() in YdbRepository. Also, don't reference Guava Supplier interface in yoj-util

YOJ 2.2.13 (bugfix and dependency update)

• #60 - FIX: TableQueryBuilder.where() now adds conditions using AND, previously it replaced the whole query
• 2e55e78 - Update Google Guava dependency to 33.0.0-jre