Repository navigation
Conversation
This is my attempt to build an agent skill that cross-references - The versions of all dependencies we actually use in CI (by checking the workflow logs), across all tests - The range we claim to support and test as documented in INSTALL.md - The minimum versions we accept, enforced in externalpackages.cmake - The actual latest versions available (as near as we can determine, looking at those projects' release tags in their own repos) and reconciles any differences, for example: bump the "latest" CI jobs to new versions of deps that have come out, ensure INSTALL reflects the actual range that we support and test, etc. It writes a report summarizing all the findings, and makes suggestions for what to adjust in the project. I've been testing this for a while and it works great and saves me a lot of tedious checking of different dependency projects, and ensures that the various files listed above aren't drifting away from each other. This is something I need to do as the project maintainer frequently, at least monthly so that the patch releases are tested on the real latest. I want to check it into the repo both so that it can be versioned and always lives with the project, but also so that people other than me can also perform these checks. Assisted-by: Claude Code / Sonnet 5 Signed-off-by: Larry Gritz <lg@larrygritz.com>
|
Here's an example of the report it generates: Dependency audit, 2026-10-17Run
Local build (dist/bin/oiiotool, 2026-10-16 21:09, OIIO 3.3.0.0dev)Apple clang 21.0 C++17, CMake 4.4.4, Python3 3.14.8, NumPy 2.5.4 (system python3 A. TableBold min/max = not matched by CI; bold Latest = newer than CI tests.
Notes: libheif INSTALL 1.23.5 is above CI's 1.23.4. OpenVDB INSTALL 13.1 is above B. Oldest / hobbled vs INSTALL minimumNot at minimum in
C.
|
This is my attempt to build an agent skill that cross-references
and reconciles any differences, for example: bump the "latest" CI jobs to new versions of deps that have come out, ensure INSTALL reflects the actual range that we support and test, etc. It writes a report summarizing all the findings, and makes suggestions for what to adjust in the project.
I've been testing this for a while and it works great and saves me a lot of tedious checking of different dependency projects, and ensures that the various files listed above aren't drifting away from each other. This is something I need to do as the project maintainer frequently, at least monthly so that the patch releases are tested on the real latest.
I want to check it into the repo both so that it can be versioned and always lives with the project, but also so that people other than me can also perform these checks.
Assisted-by: Claude Code / Sonnet 5