This guide helps you migrate from legacy dependency update tools to omnibump.
Your existing gobump configuration files work directly with omnibump:
# Your gobump-deps.yaml works directly
omnibump --deps gobump-deps.yaml --tidy
# Optional: Rename to new standard
mv gobump-deps.yaml deps.yaml
mv gobump-replaces.yaml replaces.yamlNo changes needed to configuration format. The same YAML structure works:
# Works with both gobump and omnibump
packages:
- name: golang.org/x/sys
version: v0.28.0| gobump | omnibump |
|---|---|
gobump --deps deps.yaml |
omnibump --deps deps.yaml |
gobump --tidy |
omnibump --tidy |
gobump --dry-run |
omnibump --dry-run |
Your existing cargobump configuration files work directly with omnibump:
# Your cargobump-deps.yaml works directly
omnibump --deps cargobump-deps.yaml
# Optional: Rename to new standard
mv cargobump-deps.yaml deps.yamlNo changes needed to configuration format:
# Works with both cargobump and omnibump
packages:
- name: tokio
version: 1.42.0| cargobump | omnibump |
|---|---|
cargobump --deps deps.yaml |
omnibump --deps deps.yaml |
cargobump --dry-run |
omnibump --dry-run |
Your existing pombump configuration files work directly with omnibump:
# Your pombump files work directly
omnibump --deps pombump-deps.yaml --properties pombump-properties.yaml
# Optional: Rename to new standard
mv pombump-deps.yaml deps.yaml
mv pombump-properties.yaml properties.yamlNo changes needed to configuration format:
# Works with both pombump and omnibump
packages:
- groupId: io.netty
artifactId: netty-codec-http
version: 4.1.94.Final| pombump | omnibump |
|---|---|
pombump --deps deps.yaml |
omnibump --deps deps.yaml |
pombump --properties props.yaml |
omnibump --properties props.yaml |
pombump --dry-run |
omnibump --dry-run |
One of omnibump's advantages is support for a unified configuration format across all languages:
# Different configuration files for different languages
gobump --deps gobump-deps.yaml # Go projects
cargobump --deps cargobump-deps.yaml # Rust projects
pombump --deps pombump-deps.yaml # Java projects# Same tool and format for all projects
omnibump --deps deps.yaml # Auto-detects language# language field is optional - will auto-detect
packages:
# Works for Go, Rust, and Maven
- name: package-name
version: 1.2.3
# Maven-specific format also supported
- groupId: com.example
artifactId: library
version: 1.0.0- Install omnibump
- Test with existing configuration files (no changes needed)
- Verify updates work correctly with
--dry-run - Optionally rename configuration files to standard names
- Update CI/CD pipelines to use omnibump
- Update documentation and scripts
- Remove old tools (gobump, cargobump, pombump)
You can migrate gradually:
- Install omnibump alongside existing tools
- Test omnibump with existing configuration files
- Migrate one project at a time
- Update automation last
- Remove old tools when comfortable
- One tool to learn and maintain
- Consistent commands across projects
- Unified documentation
- No need to specify language explicitly
- Works seamlessly across project types
- Reduces configuration
- Better error messages
- Enhanced validation
- Improved performance
- Active development and support
If you encounter issues during migration:
- Check the troubleshooting guide
- Compare behavior with
--dry-run - Open an issue with details about your use case