liushuyu/version-sync — explained in plain English
Analysis updated 2026-07-06 · repo last pushed 2024-05-24
Catch outdated version numbers in your README before publishing a new release.
Verify documentation links point to the correct versioned pages.
Automatically verify version references during your standard Rust test workflow.
| liushuyu/version-sync | bakome-hub/bakome-crypto-quant-engine | caspermeijn/nmea-test-messages | |
|---|---|---|---|
| Stars | — | 0 | — |
| Language | Rust | Rust | Rust |
| Last pushed | 2024-05-24 | — | 2024-09-16 |
| Maintenance | Dormant | — | Stale |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 3/5 | 1/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Integrates directly into Rust's standard testing workflow as a dev-dependency.
If you've ever released a new version of your software and then realized your README still tells people to install the old version, version-sync is here to help. It's a tool for Rust developers that automatically checks whether references to your project's version number, like in your README or documentation links, match the actual version defined in your project's configuration file. Think of it as a safety net that catches the easy-to-miss details when you're rushing to ship a release. Here's how it works: when you run your project's tests, version-sync scans specific files for version numbers and compares them to the one in your main config. For example, if your README contains a code block showing how to install your library at version 0.1 but you just bumped the real version to 0.2, the test fails and points out exactly where the mismatch is. You can also check that documentation links point to the right versioned page. If you have a code block in your README that intentionally uses an old version number, you can tag it to be skipped during these checks. This tool is designed for Rust developers and library maintainers who publish packages publicly. Imagine you maintain a popular open-source library and you just released version 1.4. You changed the version number in your config, but forgot to update the install instructions in your README. Without this tool, your users might copy-paste outdated instructions and get confused when things don't work. With version-sync, your automated tests catch that mistake before anyone else does. The project is straightforward and focused on doing one job well. It integrates directly into Rust's standard testing workflow, so there's no separate step to remember, if your tests pass, your version references are consistent. The README notes that it can also search files using custom patterns, giving you flexibility beyond just README files.
A tool for Rust developers that automatically checks if version numbers mentioned in files like README match the actual version in the project config, preventing outdated documentation when releasing new versions.
Mainly Rust. The stack also includes Rust.
Dormant — no commits in 2+ years (last push 2024-05-24).
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.