diff --git a/.changeset/hungry-yaks-lay.md b/.changeset/hungry-yaks-lay.md
deleted file mode 100644
index f961c7c7..00000000
--- a/.changeset/hungry-yaks-lay.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-"@ducanh2912/next-pwa": major
-"@ducanh2912/next-sw": minor
----
-
-BREAKING CHANGE(next-pwa, next-sw): use next's swc bindings instead of swc/core
-
-What: From now on we will try to resolve `next/dist/build/swc` in `swc-loader` (needed to use `cacheOnFrontEndNav`, custom workers and offline fallbacks). If it can't be resolved, we will fallback to `@swc/core` (needed to be installed manually).
-
-Why: This is to save disk space (we don't need two `@swc/core`) and avoid exceeding Vercel's serverless size limit.
-
-Why use Next's `next/dist/build/swc`: it seems that `@next/mdx` is also doing the same for their `mdx` Rust compiler.
-
-How to upgrade: Usually you don't need to do anything. But if you see this line when you build your Next app: `Using @swc/core to compile next-pwa's features. Please install it if you haven't.`, please do as instructed.
diff --git a/.changeset/serious-dodos-complain.md b/.changeset/serious-dodos-complain.md
deleted file mode 100644
index 3a811017..00000000
--- a/.changeset/serious-dodos-complain.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-"@ducanh2912/next-pwa": major
----
-
-BREAKING CHANGE(requirements): bump minimum Next.js version to v11
-
-What: `next-pwa`'s minimum supported Next.js version is now 11.0.0.
-
-Why: I noticed that `workbox-webpack-plugin` no longer works with Next.js 9 and 10, so this bumps the minimum supported Next.js version to v11.
-
-How to upgrade: Bump `next` to at least 11.0.0.
diff --git a/.changeset/spotty-readers-attend.md b/.changeset/spotty-readers-attend.md
deleted file mode 100644
index a845151c..00000000
--- a/.changeset/spotty-readers-attend.md
+++ /dev/null
@@ -1,2 +0,0 @@
----
----
diff --git a/packages/next-pwa/CHANGELOG.md b/packages/next-pwa/CHANGELOG.md
index 92206dda..f1de7444 100644
--- a/packages/next-pwa/CHANGELOG.md
+++ b/packages/next-pwa/CHANGELOG.md
@@ -1,5 +1,27 @@
 # @ducanh2912/next-pwa
 
+## 9.0.0
+
+### Major Changes
+
+- [#38](https://github.com/DuCanhGH/next-pwa/pull/38) [`7bd3ba7`](https://github.com/DuCanhGH/next-pwa/commit/7bd3ba7023f5088a1e8bd7a8779cb99cd2bf369d) Thanks [@DuCanhGH](https://github.com/DuCanhGH)! - BREAKING CHANGE(next-pwa, next-sw): use next's swc bindings instead of swc/core
+
+  What: From now on we will try to resolve `next/dist/build/swc` in `swc-loader` (needed to use `cacheOnFrontEndNav`, custom workers and offline fallbacks). If it can't be resolved, we will fallback to `@swc/core` (needed to be installed manually).
+
+  Why: This is to save disk space (we don't need two `@swc/core`) and avoid exceeding Vercel's serverless size limit.
+
+  Why use Next's `next/dist/build/swc`: it seems that `@next/mdx` is also doing the same for their `mdx` Rust compiler.
+
+  How to upgrade: Usually you don't need to do anything. But if you see this line when you build your Next app: `Using @swc/core to compile next-pwa's features. Please install it if you haven't.`, please do as instructed.
+
+- [#38](https://github.com/DuCanhGH/next-pwa/pull/38) [`7bd3ba7`](https://github.com/DuCanhGH/next-pwa/commit/7bd3ba7023f5088a1e8bd7a8779cb99cd2bf369d) Thanks [@DuCanhGH](https://github.com/DuCanhGH)! - BREAKING CHANGE(requirements): bump minimum Next.js version to v11
+
+  What: `next-pwa`'s minimum supported Next.js version is now 11.0.0.
+
+  Why: I noticed that `workbox-webpack-plugin` no longer works with Next.js 9 and 10, so this bumps the minimum supported Next.js version to v11.
+
+  How to upgrade: Bump `next` to at least 11.0.0.
+
 ## 8.7.1
 
 ### Patch Changes
diff --git a/packages/next-pwa/package.json b/packages/next-pwa/package.json
index becb6ed3..bb2b71b3 100644
--- a/packages/next-pwa/package.json
+++ b/packages/next-pwa/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ducanh2912/next-pwa",
-  "version": "8.7.1",
+  "version": "9.0.0",
   "type": "module",
   "description": "PWA for Next.js, powered by Workbox.",
   "repository": "https://github.com/DuCanhGH/next-pwa",
diff --git a/packages/next-sw/CHANGELOG.md b/packages/next-sw/CHANGELOG.md
index 6ed9b9e2..8a04c7a7 100644
--- a/packages/next-sw/CHANGELOG.md
+++ b/packages/next-sw/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @ducanh2912/next-sw
 
+## 1.1.0
+
+### Minor Changes
+
+- [#38](https://github.com/DuCanhGH/next-pwa/pull/38) [`7bd3ba7`](https://github.com/DuCanhGH/next-pwa/commit/7bd3ba7023f5088a1e8bd7a8779cb99cd2bf369d) Thanks [@DuCanhGH](https://github.com/DuCanhGH)! - BREAKING CHANGE(next-pwa, next-sw): use next's swc bindings instead of swc/core
+
+  What: From now on we will try to resolve `next/dist/build/swc` in `swc-loader` (needed to use `cacheOnFrontEndNav`, custom workers and offline fallbacks). If it can't be resolved, we will fallback to `@swc/core` (needed to be installed manually).
+
+  Why: This is to save disk space (we don't need two `@swc/core`) and avoid exceeding Vercel's serverless size limit.
+
+  Why use Next's `next/dist/build/swc`: it seems that `@next/mdx` is also doing the same for their `mdx` Rust compiler.
+
+  How to upgrade: Usually you don't need to do anything. But if you see this line when you build your Next app: `Using @swc/core to compile next-pwa's features. Please install it if you haven't.`, please do as instructed.
+
 ## 1.0.0
 
 ### Patch Changes
diff --git a/packages/next-sw/package.json b/packages/next-sw/package.json
index ebc772c3..e6e7b086 100644
--- a/packages/next-sw/package.json
+++ b/packages/next-sw/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ducanh2912/next-sw",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "type": "module",
   "description": "PWA for Next.js, powered by pure ServiceWorker.",
   "repository": "https://github.com/DuCanhGH/next-pwa",