🚀 Release apps

apps/avatax/CHANGELOG.md

@@ -1,5 +1,12 @@
 # saleor-app-avatax
 
+## 1.22.8
+
+### Patch Changes
+
+- 9265c47: Fixed Client Logs date filter showing an opaque error when the "From" date was after the "To" date. Before, the request was sent and DynamoDB rejected it with a generic validation error. Now the form skips the request and shows a clear inline message, and the API rejects inverted ranges with a 400 response.
+- 4af78c1: Failed JWT verification in tRPC procedures no longer reports to Sentry as an error. Before, an expired or invalid token raised a 500 (or 403) and produced an error in monitoring even though it was a normal client-side auth failure. Now it logs a warning and returns 401, so dashboards stay clean and the client can react to the auth state correctly.
+
 ## 1.22.7
 
 ### Patch Changes

apps/avatax/package.json

@@ -1,6 +1,6 @@
 {
   "name": "saleor-app-avatax",
-  "version": "1.22.7",
+  "version": "1.22.8",
   "private": true,
   "type": "module",
   "scripts": {

apps/cms/CHANGELOG.md

@@ -1,5 +1,11 @@
 # saleor-app-cms
 
+## 2.15.6
+
+### Patch Changes
+
+- 4af78c1: Failed JWT verification in tRPC procedures no longer reports to Sentry as an error. Before, an expired or invalid token raised a 500 (or 403) and produced an error in monitoring even though it was a normal client-side auth failure. Now it logs a warning and returns 401, so dashboards stay clean and the client can react to the auth state correctly.
+
 ## 2.15.5
 
 ### Patch Changes

apps/cms/package.json

@@ -1,6 +1,6 @@
 {
   "name": "saleor-app-cms",
-  "version": "2.15.5",
+  "version": "2.15.6",
   "private": true,
   "type": "module",
   "scripts": {

apps/np-atobarai/CHANGELOG.md

@@ -1,5 +1,11 @@
 # saleor-app-payment-np-atobarai
 
+## 1.4.8
+
+### Patch Changes
+
+- 4af78c1: Failed JWT verification in tRPC procedures no longer reports to Sentry as an error. Before, an expired or invalid token raised a 500 (or 403) and produced an error in monitoring even though it was a normal client-side auth failure. Now it logs a warning and returns 401, so dashboards stay clean and the client can react to the auth state correctly.
+
 ## 1.4.7
 
 ### Patch Changes

apps/np-atobarai/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "saleor-app-payment-np-atobarai",
-  "version": "1.4.7",
+  "version": "1.4.8",
   "private": true,
   "type": "module",
   "scripts": {

apps/products-feed/CHANGELOG.md

@@ -1,5 +1,11 @@
 # saleor-app-products-feed
 
+## 3.0.6
+
+### Patch Changes
+
+- 4af78c1: Failed JWT verification in tRPC procedures no longer reports to Sentry as an error. Before, an expired or invalid token raised a 500 (or 403) and produced an error in monitoring even though it was a normal client-side auth failure. Now it logs a warning and returns 401, so dashboards stay clean and the client can react to the auth state correctly.
+
 ## 3.0.5
 
 ### Patch Changes

apps/products-feed/package.json

@@ -1,6 +1,6 @@
 {
   "name": "saleor-app-products-feed",
-  "version": "3.0.5",
+  "version": "3.0.6",
   "private": true,
   "type": "module",
   "scripts": {

apps/search/CHANGELOG.md

@@ -1,5 +1,11 @@
 # saleor-app-search
 
+## 1.29.3
+
+### Patch Changes
+
+- 4af78c1: Failed JWT verification in tRPC procedures no longer reports to Sentry as an error. Before, an expired or invalid token raised a 500 (or 403) and produced an error in monitoring even though it was a normal client-side auth failure. Now it logs a warning and returns 401, so dashboards stay clean and the client can react to the auth state correctly.
+
 ## 1.29.2
 
 ### Patch Changes

apps/search/package.json

@@ -1,6 +1,6 @@
 {
   "name": "saleor-app-search",
-  "version": "1.29.2",
+  "version": "1.29.3",
   "private": true,
   "type": "module",
   "scripts": {

apps/segment/CHANGELOG.md

@@ -1,5 +1,11 @@
 # saleor-app-segment
 
+## 2.3.6
+
+### Patch Changes
+
+- 4af78c1: Failed JWT verification in tRPC procedures no longer reports to Sentry as an error. Before, an expired or invalid token raised a 500 (or 403) and produced an error in monitoring even though it was a normal client-side auth failure. Now it logs a warning and returns 401, so dashboards stay clean and the client can react to the auth state correctly.
+
 ## 2.3.5
 
 ### Patch Changes

apps/segment/package.json

@@ -1,6 +1,6 @@
 {
   "name": "saleor-app-segment",
-  "version": "2.3.5",
+  "version": "2.3.6",
   "private": true,
   "type": "module",
   "scripts": {

apps/smtp/CHANGELOG.md

@@ -1,5 +1,11 @@
 # saleor-app-smtp
 
+## 2.3.3
+
+### Patch Changes
+
+- 4af78c1: Failed JWT verification in tRPC procedures no longer reports to Sentry as an error. Before, an expired or invalid token raised a 500 (or 403) and produced an error in monitoring even though it was a normal client-side auth failure. Now it logs a warning and returns 401, so dashboards stay clean and the client can react to the auth state correctly.
+
 ## 2.3.2
 
 ### Patch Changes

apps/smtp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "saleor-app-smtp",
-  "version": "2.3.2",
+  "version": "2.3.3",
   "private": true,
   "type": "module",
   "scripts": {

apps/stripe/CHANGELOG.md

@@ -1,5 +1,11 @@
 # saleor-app-payment-stripe
 
+## 2.6.6
+
+### Patch Changes
+
+- 4af78c1: Failed JWT verification in tRPC procedures no longer reports to Sentry as an error. Before, an expired or invalid token raised a 500 (or 403) and produced an error in monitoring even though it was a normal client-side auth failure. Now it logs a warning and returns 401, so dashboards stay clean and the client can react to the auth state correctly.
+
 ## 2.6.5
 
 ### Patch Changes

apps/stripe/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "saleor-app-payment-stripe",
-  "version": "2.6.5",
+  "version": "2.6.6",
   "private": true,
   "type": "module",
   "scripts": {