bring in changelog from 2.0 branch

square · Jan 8, 2024 · 7860820 · 7860820
1 parent 150a375
commit 7860820
Showing 1 changed file with 10 additions and 7 deletions.
diff --git a/docs/changelog.md b/docs/changelog.md
@@ -3,19 +3,22 @@
 
 Please thank our [contributors](https://github.com/square/leakcanary/graphs/contributors) 🙏 🙏 🙏.
 
-## Version 3.0 (TBD)
+I've started working on LeakCanary 3.0 so new 2.x releases only contain bug fixes and new known leak patterns.
 
-### Bumped dependencies
+## Version 2.13 (2024-01-03)
 
-* Kotlin: updated to 1.8.21
+* 🐛 [#2565](https://github.com/square/leakcanary/issues/2565) Fix AndroidX Fragments incorrectly marked as leaking if detached but not destroyed.
+* 💥 [#2568](https://github.com/square/leakcanary/issues/2568) Fixed missing `RECEIVER_EXPORTED` flag when calling `registerReceiver()` on API 34+.
+* 🔨 [#2555](https://github.com/square/leakcanary/issues/2555) Binder stubs are now called out in leak traces.
+* 🐤 [#2601](https://github.com/square/leakcanary/pull/2601) Added several known manufacturer & framework leaks.
 
-### Other changes
+## Version 2.12 (2023-06-29)
 
-* Dropped support for detecting support fragment leaks: apps should all have migrated to Android X by now, and if not they can easily add this.
+* 💥 [#2527](https://github.com/square/leakcanary/issues/2527) `LifecycleRegistry` in `androidx.lifecycle:lifecycle-runtime` was migrated to kotlin and its `mState` field name changed to `state` which broke LeakCanary expectations.
+* 🐤 [#2545](https://github.com/square/leakcanary/pull/2545) Added several known manufacturer & framework leaks.
 
-## Version 2.11 (2023-05-17)
 
-This is most likely the last release before the work starts on LeakCanary 3.0.
+## Version 2.11 (2023-05-17)
 
 * 🐛 [#1764](https://github.com/square/leakcanary/issues/1764) Ignore phantom classes that were unloaded than reloaded (long time LeakCanary bug).
 * 🐛 [#2471](https://github.com/square/leakcanary/issues/2471) Fix LeakCanary introducing a weird leak in Google's CI infra.