[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.14.3

Patch Changes

• #191 db1d384 Thanks @lucasbraum! - The ai pack now reports AI SDK 7 renames in tests that vi.mock('ai') or jest.mock('ai') without importing it: the mock factory's stepCountIs key, and onFinish and the other renamed options read by fakes of ai calls such as toUIMessageStreamResponse.

• #196 fa6f788 Thanks @lucasbraum! - fix no longer runs out of memory type-checking monorepos whose root tsconfig includes every package: each workspace's program holds only the files that workspace owns, and the baseline check releases one workspace's program before building the next. When the analysis thread does run out of memory, fix says the repository is too large for analysis instead of crashing, and its temporary clone is removed on every exit path, a crashed or out-of-memory analysis thread included.

• #190 cdf7f69 Thanks @lucasbraum! - check <pkg> no longer returns nothing for an outdated dependency used only through config files (typescript through tsconfig): it is always reported, with the reason, including when its workspace's analysis fails or the time budget runs out. Analysis no longer fails with ENAMETOOLONG on a package that links itself (Yarn link:.).

• #186 5e01ef3 Thanks @lucasbraum! - Keep the migration's starting branch and commit in reports and diff hints, including after re-verification. Default hints to npx uptide, use uptide only when the command on PATH resolves to the running binary, keep shared reports portable, and preserve explicit flags accepted by suggested commands, including peer retry budgets and workspace-root retries.

• #197 b51ca9b Thanks @lucasbraum! - Suggested commands no longer print uptide when the launcher found is a project-local node_modules/.bin entry (as under pnpm run/pnpm exec or npm scripts); only a real global install does, otherwise npx uptide.

• #187 6fe81b4 Thanks @lucasbraum! - Prevent fix from failing with spawnSync git ENOBUFS when Git output exceeds 1 MiB in large repositories. Raise the buffered output limit to 256 MiB for shared Git operations and source-version status checks.

• #185 98a3119 Thanks @lucasbraum! - Detect removed Zod error members on local results of schemas imported through repository modules, including awaited safeParseAsync calls, so their .errors reads can migrate to .issues.

• #193 a68fea3 Thanks @lucasbraum! - fix no longer refuses on lockfile changes the upgrade didn't cause. When the install guard finds resolutions outside the upgrade's subtree, it runs the same install at the parent commit and judges the upgrade against that lockfile. Churn the parent install already produces is listed as "Lockfile churn the parent commit already has" and never blocks; changes only the upgrade makes are still refused, or listed for review in agent-led runs.

• #180 549edc3 Thanks @lucasbraum! - Update conflicting root pins automatically when preparing draft PRs, including App/Action runs, and list the changes at the top of the PR under "Root pins changed: review". Add updatePins: false in uptide.yml to opt out. Local runs still require explicit --update-pins consent.

• #188 69b1c88 Thanks @lucasbraum! - Continue fix as an agent-led draft instead of exiting 2 when a preflight refusal has an assisting agent: peer blockers that need a major run as the plan's suggested command, root pins without consent are updated (an explicit updatePins: false still refuses), companions that cannot move together leave the lead alone, and the install check reports out-of-scope resolutions for review. The reason heads the PR body and the terminal summary, next to feedback rounds and spend. Without an agent, with --no-llm, or on a downgrade, fix still refuses.

• #188 69b1c88 Thanks @lucasbraum! - fix makes the no-pack stop (no agent, or a major for a PR) before cloning or installing. When the check returns nothing to analyze for an outdated package, fix now says so instead of "has no upgrade", and an agent continues as a draft. Lockfile resolutions an agent-led install changed outside the upgrade are listed for review in the PR body and the terminal summary. Downgrades, key-like settings in uptide.config.json, credentials in OPENAI_BASE_URL and unsafe run reports throw SafetyRefusal, which no fallback continues past.

• #194 7dd3259 Thanks @lucasbraum! - Stop fix in preflight on npm when a package that moves, or a peer npm installs for it, rejects a package that stays installed: vitest 5 peers on vite, and vite 8 rejects the repository's esbuild 0.25. Before, npm refused the install after the clone. The row names the chain, and --allow-peer writes the override.

• 4c3dc23 Thanks @lucasbraum! - uptide pack test now prints the precision of every rule with a rewrite, breaking or not, and warns when one is below 80%. It is a warning only: no pack's status and no rule's run mode changes. The compatibility matrix lists each rewrite's precision.

• #179 9112f2b Thanks @lucasbraum! - Add fix --update-pins to explicitly approve updates to conflicting root Yarn resolutions and npm/pnpm overrides for the target and its companions. Preserve unrelated pins, update root declarations and pnpm catalogs together, report pin changes, and reject ambiguous selectors before installation.

• #192 3f81193 Thanks @lucasbraum! - The @sentry/browser 10 to 11 pack is verified again: 5 public upgrades, 22 real breaking sites, breaking precision 100% and recall 50%. @sentry/react stays a candidate: its ground truth grew to 14 public upgrades and 29 breaking sites, with 3 false positives among its breaking findings.

• #202 51a6f70 Thanks @lucasbraum! - The Sentry packs now read JavaScript files that only require another Sentry package (@sentry/core, a sibling SDK of the same release), which the TypeScript compile scope skipped. @sentry/browser breaking recall on public ground truth goes from 50% to 82% with no false positives.

• #199 08da2a7 Thanks @lucasbraum! - The Sentry 10 to 11 pack no longer reports beforeSendTransaction or ignoreTransactions in a Sentry.init that sets traceLifecycle: the option keeps transactions, so they still work.

• #189 5d1d350 Thanks @lucasbraum! - Avoid shared registry-cache write races during parallel checks, publish complete package extractions atomically, and print package failure reasons on stderr when check exits 2.

• #195 15b3b3e Thanks @lucasbraum! - The vitest pack now reads vite.config.* and vitest.config.* files and jest-dom setup files that never import vitest (a config that takes defineConfig from a shared file, a setup file that only does import '@testing-library/jest-dom/vitest'), so it reports their bare-directory coverage patterns and jest-dom registrations.