venus
VENUS-245
Runtime/toolchain upgrade — Next stable, React 19.2.7, Node 24.x, pnpm 10 + staged compat bumps
Done high
cvcoder-venus-cc
Fleet-wide baseline upgrade (Elazar directive via pm-mars-cc/MARS-449), used as Enamel's build baseline. Bump Next to current stable, React/React-DOM 19.2.7, Node 24.x, pin Vercel-supported pnpm 10, then staged compatible bumps: Supabase JS/@supabase/ssr, pg, Tailwind, Base UI, Lucide, Sharp, Sass, etc. No blind pnpm update --latest. Isolate breaking majors (TS7, ESLint10, Nodemailer9, react-zoom-pan-pinch4) and test per-app. Class-A (touches @supabase/ssr auth + Nodemailer email versions) — audit-venus-ca pre-implementation design-ping required before landing. Coordinate breaking-major verdicts with mars/pluto on aro:evolutiva-management thread pm-mars-cc-mrljx8tnc2rq.
Questions
No questions.
Activity
-
3 staged pushes, all audit PASS: S1 143d562/v0.95.32 (Node24.x/pnpm10/next16.2.10/react19.2.7/supabase-js2.110.5/pg8.22/sharp0.35.3/lucide1.24), S2 9d82075/v0.95.33 (@supabase/ssr0.12.3), S3 55d757b/v0.95.34 (nodemailer9.0.3). All live-verified, 0 runtime errors. TS7 + ESLint10 parked upstream-blocked (typescript-eslint peer <6.1.0 / eslint-config-next lacks compatible peers) — not app code, revisit when upstream ships.
-
Follow-on regression (VENUS-258, fixed 36991ad/v0.97.1): the sharp ^0.35.3 bump landed by this WI (143d562) broke prod - sharp 0.35.x + Vercel/turbopack+pnpm serverless-trace regression (lovell/sharp#4567), libvips-cpp.so not traced into bundle, 500 on every práctica image-upload POST. Reverted to ^0.34.5 (last-known-good). CONSTRAINT for any future toolchain work: do not re-bump sharp to 0.35.x until the upstream Vercel-trace fix lands - verify via lovell/sharp#4567 status before attempting again.
venus
4w ago by wi-cli-venus
4w ago
2026-07-15 04:29