v3.4.0

CHANGELOG.md

@@ -1,6 +1,12 @@
 All notable changes to this project will be documented in this file.
 We follow the [Semantic Versioning 2.0.0](http://semver.org/) format.
 
+### 3.4.0 - 2023-10-24
+
+### Added
+
+- Add support for strongly-typed response content-type headers.
+
 ### 3.3.0 - 2023-10-23
 
 ### Added

apps/example/public/openapi.json

@@ -3,7 +3,7 @@
   "info": {
     "title": "Next REST Framework",
     "description": "This is an autogenerated documentation by Next REST Framework.",
-    "version": "v3.3.0"
+    "version": "v3.4.0"
   },
   "paths": {
     "/api/api-routes/todos": {

docs/docs/getting-started.md

@@ -133,7 +133,7 @@ const handler = routeHandler({
 export { handler as GET, handler as POST };
 ```
 
-The `TypedNextResponse` ensures that the response status codes are type-checked. You can still use the regular `NextResponse` if you prefer to have less type-safety.
+The `TypedNextResponse` ensures that the response status codes and content-type headers are type-checked. You can still use the regular `NextResponse` if you prefer to have less type-safety.
 
 #### Pages Router:
 

packages/next-rest-framework/README.md

@@ -204,7 +204,7 @@ const handler = routeHandler({
 export { handler as GET, handler as POST };
 ```
 
-The `TypedNextResponse` ensures that the response status codes are type-checked. You can still use the regular `NextResponse` if you prefer to have less type-safety.
+The `TypedNextResponse` ensures that the response status codes and content-type headers are type-checked. You can still use the regular `NextResponse` if you prefer to have less type-safety.
 
 #### Pages Router:
 

packages/next-rest-framework/package.json

@@ -1,6 +1,6 @@
 {
   "name": "next-rest-framework",
-  "version": "3.3.0",
+  "version": "3.4.0",
   "description": "Next REST Framework - write type-safe, self-documenting REST APIs in Next.js",
   "keywords": [
     "nextjs",