Migration

Zod v4 is a major overhaul of the most popular TypeScript schema validation library — delivering 14x faster string parsing, a 57% smaller core bundle, and a completely reworked API for format validation. Most codebases can migrate in under a day using the official codemod, but there are real breaking changes that will catch you off guard if you skip the changelog. What Is Zod v4 and Why the Major Version Bump? Zod v4 is a ground-up rewrite of Zod’s internal architecture, released by Colin McDonnell in mid-2025 after two years of development driven by feedback from Zod v3’s performance and bundle size limitations. With over 42,835 GitHub stars and 102 million weekly npm downloads, Zod is the de facto TypeScript runtime validation standard — and v4 is the release that finally addresses the criticisms Valibot raised in 2023. The major version bump is justified: v4 ships real breaking changes to string format methods, object strictness options, and error handling. But beyond compatibility breaks, v4 introduces architectural changes — a new zod/v4/core sub-package, the @zod/mini tree-shakable distribution, a metadata registry system, and first-class JSON Schema conversion — that change what you can build with Zod. This isn’t just a performance patch; it’s a new foundation for the library’s next five years. ...

OpenTofu is the Linux Foundation fork of Terraform, created after HashiCorp switched Terraform’s license from MPL 2.0 to the Business Source License (BSL) in August 2023. As of 2026, OpenTofu has 12% adoption among IaC practitioners, 140+ corporate backers, and 13,000+ GitHub stars — making it the leading open-source alternative to Terraform’s 76% market-share incumbent. Why Teams Are Migrating from Terraform to OpenTofu in 2026 The Infrastructure-as-Code market hit $2.1 billion in 2026 with 28.2% annual growth, driven by platform engineering adoption reaching 80% of large enterprises. Within that market, Terraform’s BSL license change triggered a migration wave that continues in 2026. The practical driver is not ideological: teams building SaaS platforms, internal developer portals, or tooling that competes with HashiCorp products face real legal exposure under BSL. The restriction prohibits using Terraform to build products that compete with HashiCorp offerings — a definition that is broadly interpreted enough to create compliance risk for many commercial applications. Enterprise adopters of OpenTofu include Boeing, Capital One, and AMD, driven primarily by license compliance requirements and OpenTofu’s native state encryption feature that regulated industries need. OpenTofu has 12% adoption among IaC practitioners as of April 2026, with 27% of teams planning to evaluate or expand its use in the next 12 months. For teams whose legal counsel flags BSL risk, or who need features like native state encryption that Terraform still lacks, migration to OpenTofu is increasingly the straightforward compliance decision. ...

Claude Opus 4.7 is Anthropic’s most capable model as of April 2026, scoring 87.6% on SWE-bench Verified and introducing a redesigned thinking system that replaces manual budget_tokens with effort-based adaptive thinking. If you’re upgrading from Opus 4.6, four breaking API changes require code updates before your apps will run. What’s New in Claude Opus 4.7 Claude Opus 4.7, released April 16, 2026, represents a step-change in both coding capability and agentic architecture. The headline benchmark is SWE-bench Verified at 87.6% — up from 80.8% on Opus 4.6 — and SWE-bench Pro at 64.3% (up from 53.4%). On CursorBench, the real-world coding benchmark, Opus 4.7 scores 70% versus 58% for Opus 4.6. These gains come primarily from architectural improvements to multi-step reasoning: the model now plans across more steps before committing to an action, which matters most for complex debugging and refactoring tasks. Vision capability received an equally dramatic upgrade — visual acuity improved from 54.5% to 98.5%, and the model now supports 3.75MP images, three times the resolution of Opus 4.6. For computer use, Opus 4.7 scores 78.0% on OSWorld-Verified, the leading score among currently available models. Pricing stayed flat at $5/M input and $25/M output tokens, but a new tokenizer encodes the same text using up to 35% more tokens — so your actual bills will increase even without code changes. ...

Claude Opus 4.7, released April 16, 2026, silently removed budget_tokens from its extended thinking API. Any code that passes budget_tokens to Opus 4.7 receives an immediate 400 Bad Request error. The fix is a four-step migration: switch to adaptive thinking type, replace budget_tokens with the effort parameter, update agentic loops to use task_budget, and strip temperature, top_p, and top_k. This guide walks through each step with exact before/after code. What Changed in Claude Opus 4.7: budget_tokens Is Gone Claude Opus 4.7 removed budget_tokens entirely from the extended thinking configuration, replacing it with an adaptive thinking system that automatically allocates reasoning compute based on task complexity. The change affects every application that previously used thinking: { type: "enabled", budget_tokens: N } to control how much the model “thinks” before responding. Released April 16, 2026, Opus 4.7 also removes temperature, top_p, and top_k parameters — three additional fields that silently accepted values in 4.6 but now return 400 errors in 4.7. Pricing remains unchanged at $5/M input tokens and $25/M output tokens, and the model shows a 13% coding benchmark lift over Opus 4.6 on Anthropic’s internal 93-task evaluation. For teams upgrading by changing only the model string, these breaking changes arrive without warning in production — there is no deprecation header or soft-failure mode in the API response before the hard 400 begins. ...