versioning

Dogma: Version Sync

Universal version file discovery and sync. Works with any project structure.

Step 0: Check for pending changes requiring version bump

git status --porcelain

If uncommitted changes exist:

1. Load versioning rules (try in order, use first that exists):

   • CLAUDE/CLAUDE.versioning.md
   • CLAUDE.versioning.md
   • .claude/CLAUDE.versioning.md
   • Fallback: patch for bugfixes/features, minor for breaking changes, major for rewrites

2. Identify affected components and bump versions BEFORE syncing

If no pending changes: Continue to Step 1.

Step 1: Discover ALL version files

CRITICAL: Find EVERY file that could contain a version. Do NOT skip files.

# Find ALL potential version files (respects .gitignore)
git ls-files --cached --others --exclude-standard 2>/dev/null | \
  grep -E '(package\.json|plugin\.json|plugin\.ya?ml|marketplace\.json|pyproject\.toml|setup\.(py|cfg)|Cargo\.toml|version\.(txt|json)|VERSION|manifest\.json|composer\.json|build\.gradle|pom\.xml|\.gemspec|mix\.exs)$' | \
  sort

# Fallback if not a git repo:
# find . -type f \( -name "package.json" ... \) | grep -v node_modules | sort

List ALL files found. Do not filter or assume.

Step 1b: Discover ADDITIONAL files containing version strings

Search for files that might contain versions but don't match known filenames:

# Find files containing "version" that weren't caught by Step 1 (respects .gitignore)
git ls-files --cached --others --exclude-standard 2>/dev/null | \
  grep -E '\.(json|ya?ml|toml|xml|md)$' | \
  xargs grep -l -E '"version"|'\''version'\''|version:' 2>/dev/null | \
  sort

For each file found that wasn't in Step 1:

1. Quick assessment: Read the file and check if the version field is:

   • A project/package version (RELEVANT)
   • A dependency version (NOT relevant - managed separately)
   • A schema/spec version (NOT relevant)
   • An API version in documentation (NOT relevant)

2. Present to user with recommendation: