Version Packages (#892)

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

Author: github-actions[bot]

.changeset/thirty-dogs-play.md

@@ -1,5 +1,13 @@
 # @vercel/edge-config
 
+## 1.4.3
+
+### Patch Changes
+
+- 1dee5ab: Support Next.js v16 Cache Components even within `proxy.ts` (fka `middleware.ts`) - see [#890](https://github.com/vercel/storage/pull/890)
+
+  The `@vercel/edge-config` v1.4.1 release added support for Next.js v16 `cacheComponents`, but did not support using `@vercel/edge-config` in Next.js's `proxy.ts` (fka `middleware.ts`) when the `cacheComponents` flag was enabled in `next.config.ts`. This releases fixes this issue so `@vercel/edge-config` can be used in any server side context in Next.js again.
+
 ## 1.4.2
 
 ### Patch Changes

packages/edge-config/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/edge-config",
-  "version": "1.4.2",
+  "version": "1.4.3",
   "description": "Ultra-low latency data at the edge",
   "homepage": "https://vercel.com",
   "repository": {

packages/edge-config/package.json

@@ -1,5 +1,12 @@
 # vercel-storage-integration-test-suite
 
+## 0.3.13
+
+### Patch Changes
+
+- Updated dependencies [1dee5ab]
+  - @vercel/edge-config@1.4.3
+
 ## 0.3.12
 
 ### Patch Changes

test/next/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "vercel-storage-integration-test-suite",
-  "version": "0.3.12",
+  "version": "0.3.13",
   "private": true,
   "scripts": {
     "build": "next build",