Lockstep versioning

[koxudaxi]

Summary by CodeRabbit

• Chores
  • Added automated semantic versioning validation to release workflows for Python and Rust packages
  • Implemented version consistency checks to ensure synchronized versions across all build stages
  • Enhanced release automation with improved version management throughout the publishing process

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

This PR introduces a centralized version management system for the monorepo. A new Python script (scripts/manage_versions.py) synchronizes versions across configuration files, while GitHub workflow files are updated to enforce version consistency by integrating resolve-version and version-check jobs into build and release pipelines.

Changes

Cohort / File(s)	Summary
Python Publish Workflow .github/workflows/publish-python.yml	Added resolve-version job to derive release version from inputs or tags, and version-check job to validate lockstep versions. Updated build-package, build-bindings-wheels, and build-bindings-sdist jobs to depend on these new jobs and sync versions via manage_versions.py set.
Rust Publish Workflow .github/workflows/publish-rust.yml	Added version-check job for validating lockstep versions. Extended package-check and all publish jobs (publish-syntax, publish-json, publish-toml, publish-yaml) to depend on version-check and synchronize versions via the management script.
Release Check Workflow .github/workflows/release-check.yml	Introduced version-check job to validate lockstep package versions. Updated verify-package-distributions and verify-bindings-wheels jobs to depend on version-check.
Version Management Script scripts/manage_versions.py	New utility script providing Rule-based version extraction and replacement across multiple project files. Exposes CLI commands: check (with optional --tag validation) and set (to synchronize versions). Includes normalize_tag() for semantic version validation and comprehensive RULES configuration for Python and Rust project files.

Sequence Diagram(s)

sequenceDiagram
    actor Dev as Developer
    participant GHA as GitHub Actions
    participant RV as resolve-version Job
    participant VC as version-check Job
    participant MV as manage_versions.py
    participant BP as build-package Job
    
    Dev->>GHA: Trigger publish workflow (tag or input version)
    GHA->>RV: Run resolve-version job
    RV->>MV: normalize_tag() — parse & validate version
    MV-->>RV: Return normalized version
    RV-->>GHA: Expose version output
    
    GHA->>VC: Run version-check (depends on resolve-version)
    VC->>MV: manage_versions.py check --tag <version>
    MV->>MV: extract_all() — verify consistency across files
    MV-->>VC: Validation result
    VC-->>GHA: Pass/Fail version validation
    
    GHA->>BP: Run build-package (depends on version-check)
    BP->>MV: manage_versions.py set <version>
    MV->>MV: replace() — sync all version references
    MV-->>BP: Report total updates
    BP-->>GHA: Build with synchronized versions

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Poem

🐰 Hop hop, versions align so bright,
From Python to Rust, they're locked tight!
A script to synchronize, jobs to verify,
Lockstep harmony—no more versions awry! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Lockstep versioning' clearly and directly describes the main objective of the pull request, which introduces comprehensive lockstep version management across the monorepo.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch lockstep-versioning

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Breaking Change Analysis

Result: No breaking changes detected

Reasoning: PR #21 contains only CI/CD workflow changes and an internal version management script. No changes affect template string parsing, generated output, Python APIs, Rust bindings, default behaviors, or runtime support. These are purely release automation improvements that ensure version consistency across the monorepo during publishing - they have no impact on end users.

---

This analysis was performed by Claude Code Action