fix(ci): use commit-count versioning for dev builds and benchmarks by carlos-alm · Pull Request #173 · optave/ops-codegraph-tool

carlos-alm · 2026-02-28T08:36:51Z

Summary

Dev builds always produced 2.4.1-dev.<sha> because patch was hardcoded to PATCH + 1 from package.json. Now uses git rev-list to count commits since the release tag, giving monotonically increasing versions (2.4.1, 2.4.5, 2.4.15, etc.)
Benchmark scripts now use getBenchmarkVersion() (shared scripts/bench-version.js) which uses git describe to detect dev vs release state, preventing dev/dogfood benchmark runs from overwriting release data in historical reports
Added fetch-depth: 0 to the compute-version checkout so git history and tags are available

File	Change
`.github/workflows/publish.yml`	Replace `PATCH+1` with `git rev-list` commit counting, add `fetch-depth: 0`
`scripts/bench-version.js`	New shared helper — `getBenchmarkVersion(pkgVersion, cwd)`
`scripts/benchmark.js`	Use `benchVersion` instead of `pkg.version`
`scripts/incremental-benchmark.js`	Same
`scripts/query-benchmark.js`	Same
`scripts/embedding-benchmark.js`	Same
`scripts/token-benchmark.js`	Same

Verify node -e "import { getBenchmarkVersion } from './scripts/bench-version.js'; console.log(getBenchmarkVersion('2.4.0', '.'))" outputs 2.4.0-dev.N+hash (not 2.4.0)
Verify on a tagged commit it returns the clean version
Trigger a dev build via push to main and confirm version increments past .1