What problem does it solve?
Deployments in Golem need a human-meaningful version label to compare environments, track what changed, and enable rollbacks, but computing that label consistently from git tags, commit hashes, or environment variables is error-prone without clear configuration guidance.
Core Features & Use Cases
- Version Source Configuration: Set the
version: field in golem.yaml as a literal string, an environment variable, or a git-derived value using tag mode or hash-only mode.
- Git Version Tuning: Control
tagPattern, commitInfo, hashFallback, allowDirty, and staticFallback to handle untagged repos, dirty working trees, and non-git checkouts.
- Per-Environment Overrides & Uniqueness: Layer environment-specific version overrides and enforce
versionCheck so re-deploying an existing version is rejected.
- Use Case: A team tags releases as
v1.2.3, deploys to a cloud environment with versionCheck: true to prevent accidental re-deploys, while allowing dirty local deploys during development.
Quick Start
Ask the AI to configure the version field in your golem.yaml so deployments derive their version from git tags matching v* with a static fallback.