PPowerduckOct 6 · 6 min readREST API versioning in 2026: paths vs headers, additive changes, and OpenAPI diffs in CITeams argue for weeks about where a version number should live and spend almost no time on the two questions that actually protect consumers: which changes are genuinely breaking, and how an old versiblogs.powerduck.com
PPowerduckOct 5 · 5 min readVersioning MCP Tools Without Breaking the Agents That Call ThemTraditional API versioning assumes the caller is code someone wrote against a fixed contract, tested once, and deployed deliberately. MCP breaks that assumption on both ends: the caller is an agent thblogs.powerduck.com
MMithilesh GauriharSep 30 · 10 min readHow Do I Version and Roll Back an AI Pipeline in Production?By Mithilesh Gaurihar. Last verified: September 2026. Quick Answer Versioning an AI pipeline in production means splitting one release into two separate acts: building an immutable numbered version (vjoshuarocket.hashnode.dev
DDbVisualizerJul 6 · 2 min readUsing Git to Version Database Schemas and SQL QueriesGit is widely used for application code, but database teams can benefit from the same workflows. Versioning SQL files and schema updates creates a reliable record of database changes while improving cthetable.hashnode.dev
HHossein EsmatiJun 26 · 3 min readApproach to Versioning REST APIs in .NET CoreApproach to Versioning REST APIs Core principles Stability first: once released, don’t break clients. Favor additive, backward-compatible changes. Predictable versioning: expose a clear, discoverablnova-globen.hashnode.dev
HHossein EsmatiJun 26 · 13 min readContract Stability and Versioning in .NET and AzureThis article is part of the Comprehensive Guide to Microservices Architecture in .NET Core, Cloud and Azure series. This article explores proven approaches to API versioning in .NET, consumer-driven cnova-globen.hashnode.dev
SSAI PRANEETH BHATTUMay 26 · 17 min readBeyond the Bucket: A Guide to S3 Versioning, Storage & LifecycleS3 Versioning: Your Backup Strategy in AWS What Is Versioning? Let us start with a simple question. You have an index.html file. You upload it to S3. Then someone on your team modifies it and uploads 1saipraneethbhattu.hashnode.dev
KKunal GautamApr 27 · 3 min readShipping a Component Library That Doesn't Break ProductionShipping a Component Library That Doesn't Break Production A component library sounds simple: extract common UI into a package, publish to npm, everyone wins. Spoiler: it's 10x harder than it sounds. Here's what I learned maintaining one across 12 pr...kgautam.hashnode.dev
RRahul SehrawatApr 13 · 10 min readPrompts Are Code, Not ConfigThere are two phases every team building with LLMs goes through. Phase one: prompts live as string literals inside the file where they're used. A constant at the top of a module. A hardcoded f-string. A snippet pasted into a Slack thread six weeks ag...ai-zero-to-hero.hashnode.dev
NNguyễn Việt TùngApr 8 · 15 min readDesigning the BFF Contract: Request Aggregation & Client-Specific ShapingIn the previous article, we established when a BFF earns its overhead. This article assumes you have made that decision and are now facing the harder question: how do you actually design the thing wel174LAdevpath-traveler.nguyenviettung.id.vn
