version: 2.1

Author: osipxd

CHANGELOG.md

@@ -1,5 +1,7 @@
 ## [Unreleased]
 
+## [2.1] (2023-05-06)
+
 ### Reusable properties
 
 Reusable properties introduced to address the problem described in issue #14
@@ -209,7 +211,8 @@ You should use `mutableMap` and `mutableList` for mutable versions of collection
 
 Public release
 
-[unreleased]: https://github.com/RedMadRobot/mapmemory/compare/v2.0...main
+[unreleased]: https://github.com/RedMadRobot/mapmemory/compare/v2.1...main
+[2.1]: https://github.com/RedMadRobot/mapmemory/compare/v2.0...v2.1
 [2.0]: https://github.com/RedMadRobot/mapmemory/compare/v2.0-rc1..v2.0
 [2.0-rc1]: https://github.com/RedMadRobot/mapmemory/compare/v1.1...v2.0-rc1
 [1.1]: https://github.com/RedMadRobot/mapmemory/compare/v1.0...v1.1

README.md

@@ -37,15 +37,15 @@ repositories {
 }
 
 dependencies {
-    implementation("com.redmadrobot.mapmemory:mapmemory:2.0")
+    implementation("com.redmadrobot.mapmemory:mapmemory:2.1")
 
-    // or if you want to work with memory in reactive style, add one of
-    implementation("com.redmadrobot.mapmemory:mapmemory-coroutines:2.0")
-    implementation("com.redmadrobot.mapmemory:mapmemory-rxjava2:2.0")
-    implementation("com.redmadrobot.mapmemory:mapmemory-rxjava3:2.0")
+    // or if you want to work with MapMemory in reactive style, add one of
+    implementation("com.redmadrobot.mapmemory:mapmemory-coroutines:2.1")
+    implementation("com.redmadrobot.mapmemory:mapmemory-rxjava2:2.1")
+    implementation("com.redmadrobot.mapmemory:mapmemory-rxjava3:2.1")
 
     // if you want to test code that uses MapMemory
-    testImplementation("com.redmadrobot.mapmemory:mapmemory-test:2.0")
+    testImplementation("com.redmadrobot.mapmemory:mapmemory-test:2.1")
 }
 ```
 
@@ -319,6 +319,9 @@ Keep in mind that you should manually clear `SessionMemory` on logout.
 
 #### KAPT: 'IllegalStateException: Couldn't find declaration file' on delegate with inline getValue operator
 
+> **Note**  
+> This bug was fixed in Kotlin 1.8.20. Consider to update Kotlin.
+
 There is the bug in Kotlin Compiler that affects MapMemory if you create subclasses - [KT-46317](https://youtrack.jetbrains.com/issue/KT-46317).
 You can use module `mapmemory-kapt-bug-workaround` as a workaround:
 

build.gradle.kts

@@ -37,7 +37,7 @@ repositories {
 
 subprojects {
     group = "com.redmadrobot.mapmemory"
-    version = "2.1-SNAPSHOT"
+    version = "2.1"
 
     apply(plugin = "maven-publish")
     apply(plugin = "io.gitlab.arturbosch.detekt")