---
title: "#versioning articles | Hashnode"
description: "Explore 151 articles tagged #versioning on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/versioning"
---

Tag

# #versioning

151 posts · 5 followers

[Vrushika D](https://hashnode.com/@vrushika) · [Nov 3](https://hashnode.com/posts/qr-code-versioning-managing-changes-without-losing-history/6ae9a49304ec58d23bd2fbfa)

### [QR Code Versioning: Managing Changes Without Losing History](https://digitalqr.hashnode.dev/qr-code-versioning-managing-changes-without-losing-history?utm_source=hashnode&utm_medium=feed)

QR codes are often treated as static assets. Generate a code, download it, print it, and use it wherever required. But what happens when the destination URL changes? What if a business updates its lan

7 min read · [digitalqr.hashnode.dev](https://digitalqr.hashnode.dev/qr-code-versioning-managing-changes-without-losing-history?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 6](https://hashnode.com/posts/rest-api-versioning-strategy-2026/6aca07fd46cca2a7ecaa905f)

### [REST API versioning in 2026: paths vs headers, additive changes, and OpenAPI diffs in CI](https://blogs.powerduck.com/rest-api-versioning-strategy-2026?utm_source=hashnode&utm_medium=feed)

Versioning is less about where the number goes than about knowing what actually breaks a client and communicating the sunset. Here is the honest tradeoff between path and header versioning, a breaking-change checklist, and how to enforce it with OpenAPI diffs in CI.

6 min read · [blogs.powerduck.com](https://blogs.powerduck.com/rest-api-versioning-strategy-2026?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 5](https://hashnode.com/posts/versioning-mcp-tools-without-breaking-agents/6aca080a2050f8f21aae910f)

### [Versioning MCP Tools Without Breaking the Agents That Call Them](https://blogs.powerduck.com/versioning-mcp-tools-without-breaking-agents?utm_source=hashnode&utm_medium=feed)

Agents discover MCP tools at runtime and learn names and parameters from descriptions, so a renamed tool is a silent production break. Here is how to evolve a tool catalog: additive changes, deprecation windows, versioned names as a last resort, and CI diffs from the source spec.

5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/versioning-mcp-tools-without-breaking-agents?utm_source=hashnode&utm_medium=feed)

[Mithilesh Gaurihar](https://hashnode.com/@mithileshgaurihar) · [Sep 30](https://hashnode.com/posts/how-do-i-version-and-roll-back-an-ai-pipeline-in-production/6abd3e607ab7cf8219701616)

### [How Do I Version and Roll Back an AI Pipeline in Production?](https://joshuarocket.hashnode.dev/how-do-i-version-and-roll-back-an-ai-pipeline-in-production?utm_source=hashnode&utm_medium=feed)

Model versioning restores the weights, not the pipeline they ran inside. Deploy builds an immutable version, publish points an audience at one, and rollback becomes a pointer move.

10 min read · [joshuarocket.hashnode.dev](https://joshuarocket.hashnode.dev/how-do-i-version-and-roll-back-an-ai-pipeline-in-production?utm_source=hashnode&utm_medium=feed)

[DbVisualizer](https://hashnode.com/@dbvisualizer) · [Jul 6](https://hashnode.com/posts/using-git-to-version-database-schemas-and-sql-queries/6a4b52b2aca3bf88fa5972f6)

### [Using Git to Version Database Schemas and SQL Queries](https://thetable.hashnode.dev/using-git-to-version-database-schemas-and-sql-queries?utm_source=hashnode&utm_medium=feed)

Discover how Git can help manage SQL queries, database schemas, migrations, and team collaboration.

2 min read · [thetable.hashnode.dev](https://thetable.hashnode.dev/using-git-to-version-database-schemas-and-sql-queries?utm_source=hashnode&utm_medium=feed)

[Hossein Esmati](https://hashnode.com/@desmati) · [Jun 26](https://hashnode.com/posts/approach-to-versioning-rest-apis-in-net-core/6a3e61907e0675c43648b7a1)

### [Approach to Versioning REST APIs in .NET Core](https://nova-globen.hashnode.dev/approach-to-versioning-rest-apis-in-net-core?utm_source=hashnode&utm_medium=feed)

Approach to Versioning REST APIs Core principles Stability first: once released, don’t break clients. Favor additive, backward-compatible changes. Predictable versioning: expose a clear, discoverabl

3 min read · [nova-globen.hashnode.dev](https://nova-globen.hashnode.dev/approach-to-versioning-rest-apis-in-net-core?utm_source=hashnode&utm_medium=feed)

[Hossein Esmati](https://hashnode.com/@desmati) · [Jun 26](https://hashnode.com/posts/contract-stability-and-versioning-in-net-and-azure/6a3e64e85e70fa891ee59e7f)

### [Contract Stability and Versioning in .NET and Azure](https://nova-globen.hashnode.dev/contract-stability-and-versioning-in-net-and-azure?utm_source=hashnode&utm_medium=feed)

This 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 c

13 min read · [nova-globen.hashnode.dev](https://nova-globen.hashnode.dev/contract-stability-and-versioning-in-net-and-azure?utm_source=hashnode&utm_medium=feed)

[SAI PRANEETH BHATTU](https://hashnode.com/@saipraneethbhattu) · [May 26](https://hashnode.com/posts/beyond-the-bucket-a-guide-to-s3-versioning-storage-lifecycle/6a15dbe0da253d50d4d3ef02)

### [Beyond the Bucket: A Guide to S3 Versioning, Storage & Lifecycle](https://saipraneethbhattu.hashnode.dev/beyond-the-bucket-a-guide-to-s3-versioning-storage-lifecycle?utm_source=hashnode&utm_medium=feed)

If you have ever worked with AWS S3 and felt like there was a lot happening under the hood that nobody properly explained, you are in the right place. S3 is not just a bucket where you dump files. It has a rich set of features around versioning, storage tiers, lifecycle rules, replication, access logs, and encryption, and understanding each one of them properly makes a real difference.

17 min read · [saipraneethbhattu.hashnode.dev](https://saipraneethbhattu.hashnode.dev/beyond-the-bucket-a-guide-to-s3-versioning-storage-lifecycle?utm_source=hashnode&utm_medium=feed)

[Kunal Gautam](https://hashnode.com/@kgautam) · [Apr 27](https://hashnode.com/posts/shipping-a-component-library-that-doesnt-break-production/69efd12431d603f6ee083549)

### [Shipping a Component Library That Doesn't Break Production](https://kgautam.hashnode.dev/shipping-a-component-library-that-doesnt-break-production?utm_source=hashnode&utm_medium=feed)

Lessons from publishing and maintaining a shared React component library across 12 teams.

3 min read · [kgautam.hashnode.dev](https://kgautam.hashnode.dev/shipping-a-component-library-that-doesnt-break-production?utm_source=hashnode&utm_medium=feed)

[Rahul Sehrawat](https://hashnode.com/@rahulseh1998) · [Apr 13](https://hashnode.com/posts/prompts-as-code-not-config/69dc3d2615d49c020a921db9)

### [Prompts Are Code, Not Config](https://ai-zero-to-hero.hashnode.dev/prompts-as-code-not-config?utm_source=hashnode&utm_medium=feed)

Most teams treat prompts like magic strings. Then they wake up to a regression nobody can explain. Here is how to treat prompts like code — versioned, templated, tested — without making a career of it.

10 min read · [ai-zero-to-hero.hashnode.dev](https://ai-zero-to-hero.hashnode.dev/prompts-as-code-not-config?utm_source=hashnode&utm_medium=feed)
