release: version packages

packages/next-app-dir-sample/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @logto/next-app-dir-sample
 
+## 2.1.17
+
+### Patch Changes
+
+- Updated dependencies [a40b28f]
+- Updated dependencies [ff8bcbb]
+  - @logto/next@3.4.0
+
 ## 2.1.16
 
 ### Patch Changes

packages/next-app-dir-sample/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@logto/next-app-dir-sample",
-  "version": "2.1.16",
+  "version": "2.1.17",
   "license": "MIT",
   "private": true,
   "scripts": {

packages/next-sample/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Change Log
 
+## 2.1.17
+
+### Patch Changes
+
+- Updated dependencies [a40b28f]
+- Updated dependencies [ff8bcbb]
+  - @logto/next@3.4.0
+
 ## 2.1.16
 
 ### Patch Changes

packages/next-sample/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@logto/next-sample",
-  "version": "2.1.16",
+  "version": "2.1.17",
   "license": "MIT",
   "private": true,
   "scripts": {

packages/next-server-actions-sample/CHANGELOG.md

@@ -1,5 +1,25 @@
 # next-server-actions-sample
 
+## 2.2.0
+
+### Minor Changes
+
+- a40b28f: add getAccessToken to the server actions package
+
+  Previously, in order to get access tokens (and organization tokens) in App Router, you'll use `getLogtoContext` with config `{ getAccessToken: true }`, this won't cache the token and will make a network request every time you call it. That is because Next.js does not allow to write cookies in the server side: HTTP does not allow setting cookies after streaming starts, so you must use .set() in a Server Action or Route Handler.
+
+  This change adds a new function `getAccessToken` for you to get the access token in a server action or a route handler. It will cache the token and only make a network request when the token is expired.
+
+  And also, this change adds a new function `getOrganizationToken` for you to get the organization token.
+
+  The original method is deprecated and will be removed in the future.
+
+### Patch Changes
+
+- Updated dependencies [a40b28f]
+- Updated dependencies [ff8bcbb]
+  - @logto/next@3.4.0
+
 ## 2.1.21
 
 ### Patch Changes

packages/next-server-actions-sample/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@logto/next-server-actions-sample",
-  "version": "2.1.21",
+  "version": "2.2.0",
   "license": "MIT",
   "private": true,
   "scripts": {

packages/next/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Change Log
 
+## 3.4.0
+
+### Minor Changes
+
+- a40b28f: add getAccessToken to the server actions package
+
+  Previously, in order to get access tokens (and organization tokens) in App Router, you'll use `getLogtoContext` with config `{ getAccessToken: true }`, this won't cache the token and will make a network request every time you call it. That is because Next.js does not allow to write cookies in the server side: HTTP does not allow setting cookies after streaming starts, so you must use .set() in a Server Action or Route Handler.
+
+  This change adds a new function `getAccessToken` for you to get the access token in a server action or a route handler. It will cache the token and only make a network request when the token is expired.
+
+  And also, this change adds a new function `getOrganizationToken` for you to get the organization token.
+
+  The original method is deprecated and will be removed in the future.
+
+- ff8bcbb: support custom error handler for all methods in pages router
+
 ## 3.3.4
 
 ### Patch Changes

packages/next/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@logto/next",
-  "version": "3.3.4",
+  "version": "3.4.0",
   "type": "module",
   "main": "./lib/src/index.cjs",
   "module": "./lib/src/index.js",

packages/nuxt/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @logto/nuxt
 
+## 0.3.3
+
+### Patch Changes
+
+- ea4555f: use warning to replace the error of empty configuration
+
 ## 0.3.2
 
 ### Patch Changes

packages/nuxt/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@logto/nuxt",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "type": "module",
   "exports": {
     ".": {