pudo-code-system

Versioning Guide

This project follows Semantic Versioning 2.0.0 (SemVer). Managing versions correctly is critical to prevent breaking downstream AI workflows, tools, and integrations that rely on PUDO.

SemVer Overview

A version number is formatted as MAJOR.MINOR.PATCH (e.g., 1.2.0).


Evolving both Playbooks & MCP Server

Because this repository functions as both an AI Engineering Playbook and a publishable MCP Server package, version updates must account for both:

Patch Bumps (0.0.x)

Use for backward-compatible bug fixes and small documentation improvements:

Minor Bumps (0.x.0)

Use for backward-compatible additions or improvements:

Major Bumps (x.0.0)

Use for backward-incompatible (breaking) changes:


Keeping Versions in Sync

We maintain multiple files that reference the current version. During a release, all of the following files must be updated simultaneously:

  1. Root package.json: "version": "MAJOR.MINOR.PATCH"
  2. MCP Server package.json (packages/pudo-mcp-server/package.json): "version": "MAJOR.MINOR.PATCH"
  3. Changelog Header (CHANGELOG.md): ## [MAJOR.MINOR.PATCH] - YYYY-MM-DD

Run npm install after updating package versions to keep package-lock.json files synchronized.