[uptide-release]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

uptide@0.15.0

Minor Changes

• #203 19dd649 Thanks @lucasbraum! - fix estimates what the agent's sites will cost and prints the estimate before its first call. When the estimate is above the limit (--max-cost, default $1), it stops before spending anything and exits 2: estimated $3.00 for 50 sites; limit $1.00. Run again with --max-cost 3.00. Action and App runs never stop on the estimate: they work within maxCost, and the summary and the pull request name the sites left and the maxCost in uptide.yml that finishes them. When the agent stops at the limit, the summary and the pull request name the estimate and the limit that continues. The summary (Phases), the pull request's run details and report.json (phases) give wall time and agent spend per phase.

• #207 4a90e9f Thanks @lucasbraum! - fix names the first major of a peer blocker that accepts the target (no 1.x accepts react 19; 2.2.0 does) and suggests adding it to the command instead of --allow-peer. When a verified pack covers that major, the blocker moves as a companion and its pack runs in the same fix: its rules, its detect-based findings and its inventory, each at the companion's own versions. When no pack covers it, the PR says the major needs its own migration and the risk is High. --allow-peer stays the suggestion only when no release accepts the target. A group member that the target's own range already accepts (@casl/ability under @casl/react 5) is no longer reported as a conflict.

Patch Changes

• #208 5fdb60e Thanks @lucasbraum! - The express pack reports the const { id } = req.params line as a site when the compiler reports a string | string[] error on one of its names, because that line is where the guide types the values once.

• #211 213e1a5 Thanks @lucasbraum! - fix runs prisma generate / graphql-codegen in its verification clone before the baseline and after the upgrade; check names the missing generator step

• #204 65b7edb Thanks @lucasbraum! - check and fix now measure how many of the files that use the upgraded package the repository actually type-checks (TypeScript, plus JavaScript under checkJs or // @ts-check). When that is under half, the summaries say types cover N of M affected files and no longer present a clean compile as proof: fix passes only when a test run or a build passed, and says the verdict rests on them.

• #205 c0332eb Thanks @lucasbraum! - fix no longer fails on npm repositories whose lockfile carries optional platform packages such as sharp's @emnapi/*. npm 11.6 drops them on the first lock-only install and writes a lockfile its own npm ci rejects; fix now runs the lock-only install twice, at the upgrade and at the parent commit alike, so the lockfile it validates is one npm ci accepts.

• #201 4550da5 Thanks @lucasbraum! - The react pack now reports RefObject<HTMLElement> annotations that need | null at the declaration, including in files that type a prop with the global React.RefObject and never import react. The compiler reports these where a ref is passed in, so the declaration to edit was missed.

• #216 95a3bf5 Thanks @lucasbraum! - setup PRs pin Action v0.14.3

• #209 48df030 Thanks @lucasbraum! - The zod pack reports .refine(check, { message }), the type names zod 4 marks deprecated (ZodTypeAny, ZodIssue, ZodSchema, ZodErrorMap and the others, including import('zod').ZodTypeAny) and errorMap options with ctx.defaultError, as deprecated findings.

• #200 4e4cc3e Thanks @lucasbraum! - The zod pack reports names zod 3 exported from its root and zod 4 exports only from zod/v3 (SafeParseReturnType, ZodTypeDef, ZodEffects, the Zod*Def interfaces), which the surface diff counted as unchanged, and fix now rewrites z.string().uuid() to z.guid() instead of z.uuid(), so ids that zod 3 accepted still validate.