Releases: tarantool/tuple-merger
Releases · tarantool/tuple-merger
0.0.5
Overview
This release adds handling of the MP_TUPLE
msgpack extension in the buffer source to be in-sync with upcoming Tarantool 3.0 release.
See tarantool/tarantool#8147 for details.
Breaking changes
This release should not break existing code.
Features
- Support
MP_TUPLE
extension (PR #36)
Infrastructure
0.0.4
Overview
This release adds a small convenience feature:
tarantool> merger = require('tuple.merger')
tarantool> merger._VERSION
---
- 0.0.4
...
The _VERSION
field now shows the version of the module.
Breaking changes
This release should not break existing code.
Features
- Added the
_VERSION
field with the version of the module (PR #35).
Bugfixes
- Fixed signed integer overflow (PR #32).
Infrastructure
- Workaround setup-tarantool problem with Ubuntu Jammy (PR #34).
0.0.3
0.0.2
Overview
The main change offered by this release is the working hot reload scenario:
require('tuple.merger')
package.loaded['tuple.merger'] = nil
require('tuple.merger')
Breaking changes
The module is not exposed as _G.tuple.merger
anymore. Use the return value of
require('tuple.merger')
or package.loaded['tuple.merger']
.
Aside of this, this release should not break existing code.
Bugfixes
- Fixed NULL dereference when passing an unsuitable key_def (#13, PR #14).
- Fixed NULL dereference at OOM when creating a merge source (#13, PR #25).
- Fixed reloading of the module (#21, PR #22).
- [Breaking change] Don't spoil
_G.tuple
global variable (PR #22).