This article explains how to keep the Vibgrate CLI up to date. It is for developers who installed the CLI and want the latest scanners, fixes, and formats.
Overview
Vibgrate improves regularly: new language and ecosystem coverage, scanner refinements, and bug fixes. vg update checks for and installs CLI updates so you benefit from the latest work without manually tracking releases.
Check for and install updates
Run:
vg update
The command checks for a newer version and installs it when one is available.
Confirm your version
You can check which version you are running with the version flag:
vg --version
Knowing your version is useful when comparing behavior across machines or when reporting an issue.
Why staying current matters
- Newer releases broaden language and ecosystem coverage, improving scan accuracy.
- Scanner and output-format improvements can change findings, so align your team on a version.
- Fixes reduce false positives and keep CI gates trustworthy.
Updating in CI
For reproducible pipelines, prefer pinning a specific version rather than auto-updating mid-pipeline, so a new release never changes your gate unexpectedly. See the version-pinning guide for how to do this.
Related
See the version-pinning guide for CI stability and the CI integration guides for wiring scans into your pipeline.