chore: update CHANGELOG and README for Riverpod 3 compatibility and breaking changes

Author: T-moz

CHANGELOG.md

@@ -1,7 +1,14 @@
 # 3.0.0
 
- - BREAKING: cacheDataFor cannot be use on FutureProvider. Instead use it on AsyncNotifier.
- - BREAKING: refreshWhenNetworkAvailable cannot be use on FutureProvider. Instead use it on AsyncNotifier.
+ - feat: Support for Riverpod 3!
+
+ - BREAKING: cacheDataFor cannot be used on FutureProvider. Instead use it on AsyncNotifier.
+ - BREAKING: refreshWhenNetworkAvailable cannot be used on FutureProvider. Instead use it on AsyncNotifier.
+
+ Some extensions that were previously available on FutureProvider are now only usable inside AsyncNotifier. This is due to the fact that `Ref` does not take a generic type parameter anymore.
+ See: 
+  - [One ref to rule them all](https://riverpod.dev/docs/whats_new#one-ref-to-rule-them-all)
+  - [Discussion](https://github.com/rrousselGit/riverpod/discussions/4305)
 
 # 2.0.0
 

README.md

@@ -12,8 +12,8 @@
 
 ## Riverpod Versions 🔖
 
-Riverpod Community Extensions version 2 is only compatible with riverpod 2.
-If you want to use riverpod 3, migrate to riverpod_community_extension v3.
+Riverpod Community Extensions version 3 is only compatible with riverpod 3.
+If you want to use riverpod 2, revert to riverpod_community_extension v2.
 
 ## Features 🚀