Usage
Output
- Version: Rampart version (e.g.,
v0.7.0) - Commit: Git commit hash (short, 8 chars)
- Build time: UTC timestamp when binary was compiled
- Go version: Go compiler version
Examples
Check version
Development build
dev indicates a local build from source.
Extract version (scripts)
Version in CI
Use cases
Verify installation
Check for updates
Bug reports
When reporting bugs, include version output:CI logs
Compatibility checks
Version scheme
Rampart follows Semantic Versioning:v0.7.0— Minor release (new features)v0.7.1— Patch release (bug fixes)v1.0.0— Major release (breaking changes)
Breaking changes
Major version bumps (e.g.,v1.0.0 → v2.0.0) indicate breaking changes:
- Policy format changes
- CLI flag changes
- API changes
Feature releases
Minor version bumps (e.g.,v0.7.0 → v0.8.0) add new features:
- New commands
- New policy features
- New agent integrations
Bug fixes
Patch version bumps (e.g.,v0.7.0 → v0.7.1) fix bugs:
- Security patches
- Bug fixes
- Performance improvements
Development builds
Building from source producesdev versions:
- Use
devinstead of version number - Show
uncommittedif there are uncommitted changes - Include local build timestamp
Troubleshooting
Command not found
Old version
Version mismatch
If you have multiple Rampart binaries:See also
- rampart upgrade - Upgrade to latest version
- rampart doctor - Health check (includes version check)