From 9aca62c7cbfc7efaf2095003ffb48a10ce0e2d08 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 10 Sep 2026 08:38:55 +0000
Subject: [PATCH] Version Packages (next)

---
 .changeset/pre.json | 1 +
 CHANGELOG.md        | 6 ++++++
 package.json        | 2 +-
 3 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/.changeset/pre.json b/.changeset/pre.json
index cd20526..e660e3e 100644
--- a/.changeset/pre.json
+++ b/.changeset/pre.json
@@ -57,6 +57,7 @@
     "http-bridge-h2-tls-abort",
     "id-hash-second-segment",
     "inject-deployment-secret",
+    "jest-dom-v7-next",
     "lazy-entry-eliminated-importers",
     "lazy-entry-rolldown-reclassify",
     "lazy-load-native-compiler",
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3e56676..ceb3ea7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # Changelog
 
+## 3.0.0-next.42
+
+### Patch Changes
+
+- ed9b798: Allow `@testing-library/jest-dom` v7 in the optional peer dependency range (ports #287 from `main`). The Solid 2.0 templates pin `@testing-library/jest-dom@^7.0.0`, and npm 7+ enforces peer ranges, so a clean `npm install` of a freshly created project failed with `ERESOLVE` against the `^6.*` range (solidjs/solid#3341). v7 keeps the `@testing-library/jest-dom/vitest` subpath the plugin auto-injects into `test.setupFiles`, so only the range changes.
+
 ## 3.0.0-next.41
 
 ### Patch Changes
diff --git a/package.json b/package.json
index 1cf0200..133a57f 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/vite-plugin",
-  "version": "3.0.0-next.41",
+  "version": "3.0.0-next.42",
   "description": "solid-js integration plugin for Vite",
   "type": "module",
   "engines": {