From a6003e8abf5d7ad6bcca527230c58822d5b217e3 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 14 Aug 2026 03:41:19 +0000 Subject: [PATCH 1/2] chore(ci): expand dependabot ignores for docs Astro-ecosystem majors (refs #115) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The /apps/docs ignore block previously only silenced `astro` majors, but the Starlight/Tailwind coordinated migration tracked in #115 also subsumes @astrojs/starlight, @astrojs/starlight-tailwind, @astrojs/react, @astrojs/tailwind, tailwindcss, and zod (v3→v4 transitively via astro:content). Today's Dependabot run (2026-08-13) filed six of those as separate PRs (#126, #128, #130, #131, #133, #134) and they will keep recurring weekly until the migration lands. Extend the ignore list to cover each peer, mirroring the existing comment's "remove once the migration lands" pattern. No workspace-root changes; the vitest ignore under `bun/` is untouched. --- .github/dependabot.yml | 30 +++++++++++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index fe91f80..516cdf2 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -38,12 +38,36 @@ updates: - patch - minor ignore: - # Astro majors are blocked on the Starlight/Tailwind coordinated - # migration tracked in #115. Remove this entry once that migration - # lands so Dependabot can resume bumping astro majors. + # The Astro/Starlight/Tailwind/Zod coordinated migration is tracked + # in #115. Every major listed below has to land as part of that + # migration — Starlight 0.41.x peer-deps `astro: ^7`, `@astrojs/tailwind` + # is being dropped for the Vite `@tailwindcss/vite` plugin path, + # `@astrojs/starlight-tailwind@^5` requires Tailwind v4, and Astro 7 + # brings the `zod@^4` bump transitively via `astro:content`. Keeping + # them each as drive-by Dependabot PRs just burns cycles (see the + # 2026-08-13 flood: #126, #128, #130, #131, #133, #134). Remove the + # matching entry as each dep lands during the #115 migration. - dependency-name: astro update-types: - version-update:semver-major + - dependency-name: "@astrojs/starlight" + update-types: + - version-update:semver-major + - dependency-name: "@astrojs/starlight-tailwind" + update-types: + - version-update:semver-major + - dependency-name: "@astrojs/react" + update-types: + - version-update:semver-major + - dependency-name: "@astrojs/tailwind" + update-types: + - version-update:semver-major + - dependency-name: tailwindcss + update-types: + - version-update:semver-major + - dependency-name: zod + update-types: + - version-update:semver-major # Bun workspace root — resolves the transitive graph for every # packages/*, integrations/*, tooling/*, and apps/* manifest via the From 0e4b54455acd14fe5375d1c0d8696f8eb32056bf Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 15 Aug 2026 03:43:29 +0000 Subject: [PATCH 2/2] =?UTF-8?q?chore(ci):=20address=20review=20=E2=80=94?= =?UTF-8?q?=20starlight=200.x=20semver,=20bun=20mirror,=20evergreen=20word?= =?UTF-8?q?ing?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Three fixes from Copilot + CodeRabbit review of #137: 1. `@astrojs/starlight` ships on a 0.x cadence, so Dependabot classifies 0.33.x -> 0.41.x as `semver-minor`, not `semver-major`. The previous `semver-major`-only ignore did not catch #126 — the grouped minor PR would keep re-opening. Add `version-update:semver-minor` to the Starlight entry (both scopes) so 0.x breaking releases are held with everything else in the #115 migration. 2. The expanded ignore list was only under the `/apps/docs` (npm) entry, but #131 was `@astrojs/starlight-tailwind` at the workspace root via `dependabot/bun/*`. Mirror the ignore block under the `bun` ecosystem entry at `/` so the coordinated migration blocks both scopes (root + docs) rather than leaking through one. 3. The original comment hardcoded "Astro 7" while #115's title still reads "Astro 6 upgrade tracker" — a mismatch that ages badly if the ecosystem shifts. Reword to keep the concrete ecosystem grounding ("the current 0.41.x line peer-deps the current astro major") without pinning the config to a specific major, and enumerate which PR each ignore entry blocks so future readers see the mapping. No behavior change to the vitest ignore under `bun/` (still tracks #120). --- .github/dependabot.yml | 51 +++++++++++++++++++++++++++++++++++------- 1 file changed, 43 insertions(+), 8 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 516cdf2..7c0051a 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -39,20 +39,28 @@ updates: - minor ignore: # The Astro/Starlight/Tailwind/Zod coordinated migration is tracked - # in #115. Every major listed below has to land as part of that - # migration — Starlight 0.41.x peer-deps `astro: ^7`, `@astrojs/tailwind` - # is being dropped for the Vite `@tailwindcss/vite` plugin path, - # `@astrojs/starlight-tailwind@^5` requires Tailwind v4, and Astro 7 - # brings the `zod@^4` bump transitively via `astro:content`. Keeping - # them each as drive-by Dependabot PRs just burns cycles (see the - # 2026-08-13 flood: #126, #128, #130, #131, #133, #134). Remove the - # matching entry as each dep lands during the #115 migration. + # in #115. Every entry below is blocked because the target release + # can't land solo — a Starlight minor bump requires an aligned astro + # major (the current 0.41.x line peer-deps the current astro major); + # `@astrojs/tailwind` is being dropped for the Vite + # `@tailwindcss/vite` plugin path; `@astrojs/starlight-tailwind@^5` + # requires Tailwind v4; and the matching astro major transitively + # pulls `zod@^4` via `astro:content`. Keeping them as drive-by + # Dependabot PRs just burns cycles — see the 2026-08-13 flood: #126 + # (starlight), #128 (zod), #130 (starlight-tailwind, apps/docs), + # #131 (starlight-tailwind, root), #133 (astrojs/react), #134 + # (tailwindcss). Remove the matching entry as each dep lands during + # the #115 migration. - dependency-name: astro update-types: - version-update:semver-major + # @astrojs/starlight ships on a 0.x cadence, so Dependabot classifies + # its breaking releases as semver-minor rather than semver-major. + # Ignore both to keep the grouped minor PR from re-surfacing #126. - dependency-name: "@astrojs/starlight" update-types: - version-update:semver-major + - version-update:semver-minor - dependency-name: "@astrojs/starlight-tailwind" update-types: - version-update:semver-major @@ -105,3 +113,30 @@ updates: - dependency-name: "@cloudflare/workers-types" update-types: - version-update:semver-major + # The docs Astro-ecosystem majors tracked in #115 also surface here + # via the shared root `bun.lock` (e.g. #131 was + # `@astrojs/starlight-tailwind` at root, not /apps/docs). Mirror the + # /apps/docs ignore list so the same coordinated migration blocks + # both scopes. Remove each entry as its dep lands during #115. + - dependency-name: astro + update-types: + - version-update:semver-major + - dependency-name: "@astrojs/starlight" + update-types: + - version-update:semver-major + - version-update:semver-minor + - dependency-name: "@astrojs/starlight-tailwind" + update-types: + - version-update:semver-major + - dependency-name: "@astrojs/react" + update-types: + - version-update:semver-major + - dependency-name: "@astrojs/tailwind" + update-types: + - version-update:semver-major + - dependency-name: tailwindcss + update-types: + - version-update:semver-major + - dependency-name: zod + update-types: + - version-update:semver-major