Version Packages (#54)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: github-actions[bot]

.changeset/silent-wasps-wait.md

@@ -1,5 +1,12 @@
 # example
 
+## 0.1.6
+
+### Patch Changes
+
+- Updated dependencies [e473304]
+  - @happykit/flags@3.2.0
+
 ## 0.1.5
 
 ### Patch Changes

example/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "example",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "private": true,
   "scripts": {
     "dev": "next dev",

example/package.json

@@ -1,5 +1,13 @@
 # @happykit/flags
 
+## 3.2.0
+
+### Minor Changes
+
+- e473304: add Next.js [App Router](https://nextjs.org/blog/next-13-4#nextjs-app-router) support
+
+  HappyKit has a feature called `visitorKey`, you can learn more about it [here](https://flags.happykit.dev/demo/targeting-by-visitor-key). If you want to use this feature with App Router you need to set the cookie from middleware using the `ensureVisitorKeyCookie` from `@happykit/flags/edge`. See the `example/middleware.ts` file in this repository for an example of how to do this. This is necessary as App Router pages can not set any cookies when they render, so we have to fall back to setting the cookie from middleware instead. If you do not need the `visitorKey` for your custom evaluation rules or rollouts then you do not need to set the cookie from middleware.
+
 ## 3.1.3
 
 ### Patch Changes

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@happykit/flags",
-  "version": "3.1.3",
+  "version": "3.2.0",
   "description": "Feature Flags for Next.js",
   "author": "Dominik Ferber <dominik.ferber+npm@gmail.com> (http://dferber.de/)",
   "license": "MIT",