Compatibility information is scattered across support matrices, release notes, source trees, and upgrade guides. compatibility.fyi collects that evidence in one open catalog so humans and automation can answer whether two software versions are known to work together.
GitHub Actions + GitLab CI
Compatibility Gate reads the versions declared in your repository, checks them against source-backed compatibility.fyi metadata, and reports a blocking status through GitHub Actions or GitLab CI so Renovate can wait.
No projects match that search.
Compatibility evidence is often buried in release notes, support tables, issue trackers, and source trees. compatibility.fyi turns source-backed compatibility claims into versioned YAML and JSON that can be reviewed, diffed, validated, and queried.
The catalog is readable in the browser, but the real goal is automation. Renovate, Dependabot, Helm, Argo CD, Backstage, and CI pipelines should be able to check whether a dependency update is compatible before it reaches production. Compatibility Gate connects that data to Renovate in GitHub Actions and GitLab CI.
The catalog only works if project maintainers and users contribute compatibility matrices backed by primary sources. Add a YAML file, cite the upstream evidence, and open a pull request so the data can be reviewed and kept current.
compatibility.fyi