[ephbaum]

📝 What's This PR About?

Type of Change:

• 🔧 Maintenance - Bug fixes, dependency updates, refactoring

📋 Description

Consolidates all 13 open Dependabot PRs into one branch so a single build gates
the lot. Two of them were red on their own; neither failure was real, and both
are explained below.

For Technical Changes:

• What changed: 13 dependency bumps in 3 commits, plus a CLAUDE.md note.
• Why: 13 PRs, 13 CI runs, and two permanently-red ones that each needed
  diagnosing before they could be judged.
• Impact: Lockfile and package.json only, except the third commit, which
  reformats 11 .astro files.

d8945d0 — 11 bumps whose CI was already green

Package	From	To	Was
zod	4.4.3	4.6.5	#77
vite	8.2.1	8.3.0	#73
@iconify-json/logos	1.2.12	1.2.14	#71
globals	17.11.0	17.12.0	#69
@typescript-eslint/parser	8.67.0	8.70.0	#68
@astrojs/sitemap	3.7.3	3.7.4	#66
sharp	0.35.3	0.35.4	#63
satori	0.29.0	0.33.4	#60
typescript	5.9.3	6.0.3	#57
@eslint/js	9.8.0	9.39.5	#46
unocss + @unocss/astro + @unocss/reset	66.7.5	66.10.2	#74

Dependabot raised only @unocss/reset; the three unocss packages share a
release train, so the other two move with it.

ea73b6d — astro 7.2.1 → 7.3.2 (was #76)

Red on its own with 20 astro check errors, every post.data access reported as
unknown. The cause is zod, not Astro: 7.3 infers a collection's data type
through the schema's .transform() in src/content.config.ts, and zod 4.4.3's
output types defeat that inference. Reproduced on a bare main, then bumped zod
alone on top — zero errors. Which is why it rides along here rather than
standing alone. The range resolves to 7.3.3.

ec72aed — prettier-plugin-astro 0.14.1 → 1.0.0 (was #75)

Red on its own because 1.0.x breaks JSX-ish expressions differently, leaving 11
files failing format:check. This commit carries the reformat. The ^1.0.0
range resolves to 1.0.1.

Two things found while verifying it, both upstream bugs rather than anything
wrong here:

1. It is not idempotent. One pnpm run format emits a BaseHead.astro that
   fails format:check; a second pass converges. Minimal repro is a
   self-closing <script /> inside a {cond && …} expression long enough to
   wrap — all three conditions required. Writing the explicit </script>
   sidesteps it, which is what the tree now does.
2. A worse sibling, #487,
   which we are not exposed to but easily could be. Multi-line /* … */
   comments in a <style> block gain two spaces of indentation every run and
   never converge, so format:check could never pass. Confirmed against our
   install (7 → 9 → 11 → 13 spaces). None of the three <style> blocks here
   carries a comment today, which is the only reason CI is green.

7206ab8 + c1e9129 record both in CLAUDE.md, since the symptom —
check:fix leaving CI red on a file it just rewrote — reads like a stale cache.

🖼️ Visual Changes

• Visual changes described in comments

One, from the reformat. <Button>&larr; Back to blog</Button> in
BlogContent.astro now breaks across lines, which adds collapsing whitespace
either side of the label inside the anchor.

Established by diffing all 215 built pages against a 7.3.3 build of the previous
formatting, normalising out the per-build random font-fallback ids and
brutal-ui colours. That anchor is the only difference. Separately confirmed the
Umami <script> tag emits byte-identically with PUBLIC_UMAMI_WEBSITE_ID set,
since that branch is env-gated and absent from the page diff.

If zero output change is preferred, ec72aed is the only commit that causes any
and reverts cleanly on its own — at the cost of leaving #75 red.

🧪 Testing

• Tested locally with pnpm run dev
• Built successfully with pnpm run build
• Preview deployment looks good
• No console errors
• Mobile responsive (if UI changes)

pnpm run lint, pnpm run format:check and pnpm run build all clean at each
of the three dependency commits, not just at the tip — 215 pages, astro check
reporting zero errors under TypeScript 6.

The unchecked boxes are genuinely unverified rather than assumed: the dev server
was not exercised, and the Vercel preview and mobile rendering want eyes on the
one whitespace change above. Nothing here touches layout or components beyond
formatting.

📚 Documentation

• New features documented

CLAUDE.md gains a Working conventions entry on the two prettier-plugin-astro
1.0.x bugs. No README change needed.

🔗 Related

• Supersedes: chore(deps): bump zod from 4.4.3 to 4.6.5 #77, chore(deps): bump astro from 7.2.1 to 7.3.2 #76, chore(deps-dev): bump prettier-plugin-astro from 0.14.1 to 1.0.0 #75, chore(deps-dev): bump @unocss/reset from 66.7.5 to 66.10.2 #74, chore(deps-dev): bump vite from 8.2.1 to 8.3.0 #73, chore(deps-dev): bump @iconify-json/logos from 1.2.12 to 1.2.14 #71, chore(deps-dev): bump globals from 17.11.0 to 17.12.0 #69, chore(deps-dev): bump @typescript-eslint/parser from 8.67.0 to 8.70.0 #68, chore(deps): bump @astrojs/sitemap from 3.7.3 to 3.7.4 #66, chore(deps-dev): bump sharp from 0.35.3 to 0.35.4 #63, chore(deps): bump satori from 0.29.0 to 0.33.4 #60, chore(deps): bump typescript from 5.9.3 to 6.0.3 #57, chore(deps-dev): bump @eslint/js from 9.8.0 to 9.39.5 #46 —
  all 13 open Dependabot PRs. Dependabot should close most of them itself once
  these versions land in main.
• Upstream: withastro/prettier-plugin-astro#487
  (open) is the <style> comment bug. The self-closing <script /> case is
  distinct from both #487 and the already-fixed
  #481, and is
  not yet filed.

✅ Checklist

• Code follows project conventions
• No linting errors
• Preview deployment works correctly
• Ready for review

Preview deployment left unchecked until Vercel reports on this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_01G214G6mJBeVBZ3CbukkNRu

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
ephbaumdotdev	Ready	Preview	Sep 21, 2026 12:07am UTC