# 1.5.2

## Overview

  This release fixes the bug that was discovered while working with
  `tt crud export` and `tt crud import` tools.

## Fixed
  * `insert_many`, `insert_object_many`, `replace_many`,
    `replace_object_many`, `upsert_many`, `upsert_object_many`
    operations no longer fail with `ShardingHashMismatchError` if
    a space has custom sharding info and every tuple/object
    in the request has `bucket_id` set (#437).

# 1.5.1

## Overview

  This release clarifies license in the rockspec.

## Added
* Clarify license in the rockspec (#434).

# 1.5.0

## Overview

This release introduces roles for Tarantool 3 configuration (supported
for versions 3.0.2, 3.1.0 and newer).

## Added
* Asynchronous bootstrap support for storages (#412).
* Tarantool 3 roles for setting up crud routers and storages (#415).
* Ability to configure crud through Tarantool 3 roles
  configuration (#415).

## Changed
* Explicitly forbid datetime interval conditions (#373).
* Storage initialization is now asynchronous by default for
  Tarantool 3.0+ (#412).
* Additionally check backoff error on storage info fetch (#427).

## Fixed
* Working with datetime conditions in case of non-indexed fields or
  non-iterating indexes (#373).
* Precision loss for decimal conditions in case of non-indexed fields or
  non-iterating indexes (#373).
* Passing errors from storages for merger operations (`crud.select`,
  `crud.pairs`, `readview:select`, `readview:pairs`) (#423).
* Working with `nil` operand conditions in case of non-indexed fields or
  non-iterating indexes (#422).

# 1.4.3

### Overview

This release introduces compatibility with several
Tarantool 3 + vshard 0.1.25 features, as well as critical scan fix.

### Fixed
* Compatibility with vshard configuration if UUIDs are omitted (#407).
* Compatibility with automatic master discovery in vshard (#409).
* Secondary conditions for index operands with operations `>=`, `<=`,
  `>`, `<` no longer cause missing part of the actual result for scan
  operations (`crud.select`, `crud.pairs`, `crud.count`,
  `readview:select`, `readview:pairs`) (#418).

# 1.4.2

## Overview

This release introduces compatibility with vshard 0.1.25 `name_as_key`
identification mode, as well as several minor fixes and tests
stabilization.

## Added
* `mode` option for `crud.min` and `crud.max` (#404).

## Fixed
* Compatibility with vshard 0.1.25 `name_as_key` identification mode
  for Tarantool 3.0 (#403).
* Propagating `noreturn` and `fetch_latest_metadata` options in case
  of intermediate nullable fields update for Tarantool 2.7 and
  older (#404).

## Infrastructure
* Fix flaky update unflatten test case (#404).
* Do not rely on replication in read test cases (#404).

# 1.4.1

## Overview

This release introduces various fixes for future Tarantool 3 patches
related to tuples over network.

## Changes

* Dropped external tuple merger and tuple keydef modules installation
  from the package build (#390).

## Fixes
* Compatibility with Tarantool 3.0 binary protocol change (#390).
* Compatibility with Tarantool 3.0 tuple objects (#390).

# 1.4.0

## Overview

This release improves experience for VShard clusters users and
Tarantool 3 users. It also introduces schema introspection API.

## New features

* Space schema introspection API `crud.schema` (#380).

## Bugfixes

* Return explicit error for `*_many` call with
  no tuples/objects (#377).
* `crud.readview` resource cleanup on garbage collect (#379).
* VShard storage user have not execution rights for
  internal functions (#366).
* Compatibility with Tarantool 3.0 tuple objects (#387).

## Infrastructure

* `deps.sh` installs the `vshard` instead of the `cartridge`
  by default (#364). You could to specify an environment variable
  `CARTIRDGE_VERSION` to install the `cartridge` and run tests cases
  with it.
* `doc/playground.lua` does not work with Tarantool 3 (#371).
* Tests with Tarantool 3 (#364).
* Quickstart section in the README.md focuses on usage with `vshard`
  instead of `Cartridge` (#366).

# 1.3.0

## Overview

This release introduces read view support for select and pairs.
A read view is an in-memory snapshot of data on instance that isn't
affected by future data modifications. For a sharded cluster, we open
a read view on each storage when one is requested from the router.
Read views are supported for Tarantool Enterprise since 2.11.

## New features
* Read view support for select and pairs (#343).

# 1.2.0

## Overview

This release adds two new flags: `noreturn` to ignore return values
excessive transfer and encoding/decoding for insert/replace/etc
(performance improvement up to 10% for batch requests) and
`fetch_latest_metadata` to force fetching latest space format metadata
right after a live migration (performance overhead may be up to 15%).

## New features

* Add `noreturn` option for operations:
  `insert`, `insert_object`, `insert_many`, `insert_object_many`,
  `replace`, `replace_object`, `replace_many`, `insert_object_many`,
  `upsert`, `upsert_object`, `upsert_many`, `upsert_object_many`,
  `update`, `delete` (#267).

## Bugfixes

* Crud DML operations returning stale schema for metadata generation.
  Now you may use `fetch_latest_metadata` flag to work with latest
  schema (#236).

# 1.1.1

## Overview

This release fixes a critical bug that resulted in 100% storage CPU load and fixes a couple of issues related to the development pipeline.

## Changes
* Rename `DEV` environment variable to `TARANTOOL_CRUD_ENABLE_INTERNAL_CHECKS` (#250).

## Bugfixes
* Yield on select/pairs storage tuple lookup (#312).
* Fix loaded functions misleading coverage (#249).