version-management

Git tag-driven versioning uses Git tags as the single source of truth to derive version numbers, eliminating drift between code and releases. The technology-agnostic core parses tags, bumps semantic versions, and plugs in adapters to update language-specific files.

You can automate multi-repo version synchronization by tagging releases and using adapters to propagate version updates to language-specific files like version.properties or package.json. This keeps all artifacts across repositories in sync without manual drift.

This approach requires Git as a dependency to function, because it uses Git tags as the single source of truth for versioning. You need an existing Git repository to parse tags, bump semantic versions, and apply updates to language-specific files.

Unlike manual version tracking, this approach uses a technology-agnostic core to parse Git tags and bump semantic versions automatically. It eliminates the drift common in manual methods by driving all release tooling and language-specific file updates from a single source.

Yes, this approach works without manual version file updates by using platform-specific adapters. Once a Git tag is advanced, the adapters automatically generate and apply the new semantic version to the appropriate build files like build.gradle or package.json.