From a4b83ce67536e85427fc44b36cbd7adc4c38c2d1 Mon Sep 17 00:00:00 2001
From: Altay <altay@hey.com>
Date: Sun, 25 Oct 2026 20:02:11 +0300
Subject: [PATCH] ci(renovate): move effect and @effect/* as one group

---
 README.md            | 2 ++
 renovate-config.json | 7 +++++++
 2 files changed, 9 insertions(+)

diff --git a/README.md b/README.md
index f68062c..6f75501 100644
--- a/README.md
+++ b/README.md
@@ -34,6 +34,8 @@ Renovate once every check on the PR passes; majors wait for approval on the
 Dependency Dashboard issue. `vite-plus`, `vitest`, and `@vitest/*` move in
 their own PR, since vite-plus pins an exact vitest. That PR takes the latest
 of every member at once and merges only after all of them clear release age.
+`effect` and `@effect/*` move the same way in one `effect` PR, since every
+member peers on the same `effect` version.
 
 ## frontend-release-npm.yml
 
diff --git a/renovate-config.json b/renovate-config.json
index a375572..21d305f 100644
--- a/renovate-config.json
+++ b/renovate-config.json
@@ -67,6 +67,13 @@
       "groupName": "vite-plus toolchain",
       "internalChecksFilter": "none"
     },
+    {
+      "description": "Effect packages ship together and peer on the same effect version, so they move as one PR. Each member keeps its own release-age clock, and strict filtering would merge the members that aged first. Filtering none takes the latest of every member and holds automerge until all of them age",
+      "matchPackageNames": ["effect", "@effect/*"],
+      "matchUpdateTypes": ["patch", "minor", "major"],
+      "groupName": "effect",
+      "internalChecksFilter": "none"
+    },
     {
       "description": "Pin Actions and images by digest on the initial run without waiting for release age",
       "matchUpdateTypes": ["pin", "pinDigest"],