dependabot has no roadmap. it has a version, and the version is the market cap. a market cap is a number like 2,470,000. write it in scientific notation — 2.47 × 10⁶ — and you already have a semver: the exponent is the major, the whole mantissa is the minor, the tenths are the patch.
// the whole tokenomics
mcap = m.p × 10e → v(e − 3).m.p
$2,470,000 = 2.47 × 106 → v3.2.4
$10,000 = 1.0 × 104 → v1.1.0
$0 … $9,999 → v1.0.1 // floor: the initial release. the version never goes below the site.
reference implementation
worked examples
| market cap | scientific | version | bump from previous row |
|---|
live calculator
bump rules
patch · +0.1the tenths of the mantissa tick up: $2.4M → $2.5M. the smallest change dependabot opens a PR for. label semver-patch.
minor · next whole mantissa$2.x → $3.x. nine minors per major. label semver-minor.
major · 10×$1M → $10M. a major is a decade. dependabot never ignores a major. label semver-major.
edge cases, written down
- down moves. the market can go down. the version cannot.
dependabot.yml ignores version-update:semver-down; such PRs are opened and closed in the same tick, so the ledger still shows them.
- the floor. v1.0.1 is the site release. below $10K the version stays at 1.0.1 — the first real bump is v1.1.0 at $10,000.
- mcap vs FDV. dependabot reads
marketCap from DexScreener and falls back to fdv. with a fixed supply and no vesting they are the same number.
- boundaries. exactly $2,500,000 is v3.2.5, not v3.2.4 — floor with a 1e-9 guard against float noise.
- witnesses. PRs in the feed are the bumps this browser observed while open. the chain has the full history; the bot is a client, not an oracle.
on-chain mirror (next PR)