release

remorses · Jan 26, 2025 · 4ef55fb · 4ef55fb
1 parent 54f1e70
commit 4ef55fb
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 7 deletions.
diff --git a/unframer/CHANGELOG.md b/unframer/CHANGELOG.md
@@ -1,5 +1,11 @@
 # unframer
 
+## 2.16.0
+
+### Minor Changes
+
+-   55ed540: Make variants prop in Responsive component optional, guess the variants breakpoints thanks to the plugin
+
 ## 2.15.1
 
 ### Patch Changes

diff --git a/unframer/README.md b/unframer/README.md
@@ -205,8 +205,6 @@ If you find any errors rendering your components:
 
 ## Known limitations:
 
--   Internationalization is not supported now
-
 -   You may face React warnings like:
     -   `Accessing element.ref was removed in React 19.` This warning appears because Framer still uses the old `element.ref` API which was removed in React 19. This warning is harmless and will be fixed when Framer updates their codebase to use the new React 19 APIs.
     -   `A tree hydrated but some attributes of the server rendered HTML didn't match the client properties.` This warning sometimes appears when using SWV icons, it should be harmless, it only happens in development mode.
@@ -220,7 +218,3 @@ For example in May 2024 Framer upgraded to React 19 and unframer broke, the reas
 ## Example
 
 Look at the [nextjs-app source code folder](./nextjs-app) for an example and [the deployed website here](https://unframer-nextjs-app.vercel.app/)
-
-```
-
-```
diff --git a/unframer/package.json b/unframer/package.json
@@ -1,6 +1,6 @@
 {
     "name": "unframer",
-    "version": "2.15.1",
+    "version": "2.16.0",
     "description": "Import Framer components directly in your React app, type safe and customizable",
     "sideEffects": false,
     "repository": "https://github.com/remorses/unframer",