release-runbook

Multi-language software release automation detects project types and version files across Python, Go, Node.js, Rust, and others, then coordinates version bumps, tests, git tagging, and GitHub releases. It applies workflows based on detected languages.

Coordinating version bumps in a polyglot codebase is handled by synchronizing version files across detected languages. The workflow reads project metadata, applies increments across all components, and ensures consistent tagging before pushing changes.

You need Git and GitHub CLI (gh) to automate git tagging and GitHub releases. Optional jq provides enhanced JSON handling for parsing project metadata and release payloads during the orchestration process.

Release orchestration detects project type and version files by reading project metadata across Python, Go, Node.js, Rust, Java, .NET, Ruby, and PHP repositories. It uses the detected languages to apply appropriate versioning and testing workflows.

Yes, the release workflow runs tests before creating git tags and publishing GitHub releases. It orchestrates the end-to-end process by executing test suites detected for the project type, ensuring code validation prior to version tagging and pushing.

Automating releases for single-language versus multi-language repos has no inherent limitations; the workflow handles both contexts. For polyglot codebases, it coordinates version synchronization across all detected languages, whereas single-language repos require less version file synchronization.