The value of the Free Dev Docs Library is that it matches the versions you actually depend on. That alignment is not static — your lockfile changes as you upgrade. This guide explains how the library stays current and what to do as your dependencies move.
It is for developers who upgrade dependencies regularly and want their AI docs to keep up.
Overview
The library resolves documentation against your lockfile. When you upgrade a dependency, the version it should serve docs for changes too. Keeping the library current means keeping that resolution accurate.
Check what is resolved now
vg lib
This lists the libraries available and reflects the versions resolved from your current lockfile. Run it after an upgrade to confirm the library now points at the new version.
Two sources, two refresh paths
- Hosted catalog. Popular libraries are kept current in the catalog; resolving against your lockfile picks the matching version.
- Local ingestion. For libraries not in the catalog, Vibgrate ingests docs from the copy installed in your project. After you upgrade and reinstall, local ingestion reflects the new installed version.
After an upgrade
When you bump a dependency:
- Update your lockfile (install the new version).
- Run
vg libto confirm the resolved version moved. - If the server was running, the served docs follow the new resolution.
Drift and docs together
Keeping the library current pairs naturally with watching drift. A scan shows how far behind you are:
vg scan
When DriftScore tells you a dependency is behind and you upgrade it, refreshing the library means your assistant immediately has docs for the new version.
Troubleshooting
- Docs still show the old version. Confirm the upgrade landed in your lockfile and that the package is reinstalled; the library resolves from the lockfile.
- Library missing after an upgrade. Reinstall so the new version is present for local ingestion.
Related
- Listing libraries with
vg lib - Getting version-correct docs for a dependency
- Why version-correct docs matter for AI