Repository navigation
v2 dev docs: an explicit cache directory from the binding's own option also gets the v2-dev subroot, not only CHTYPES_CACHE #527
Description
Activity
- added a commit that references this issue
on Oct 7, 2026 Landed on
v2in #546 (merge deee6f2), and ships in the next2.0.0-devpre-release.r5's "explicit cache" rule in
spec/abi-v2/docs.mdnow says thev2-devsubroot applies to any explicit cache directory, not onlyCHTYPES_CACHE. That coversCHTYPES_CACHEand the binding's own cache-directory option (GoFetchOptions.CacheDirand its counterparts) alike. All four bindings do this, and the shared cache-roots fixture holds them to it. The cache-roots API ported in the same PR (#530) returns the path with the subroot. The ABI fingerprint is unchanged.
Reported by a downstream consumer trying Go
v2.0.0-dev.0(measuredby them; the behaviour is deliberate, per spec rule r5).The dev SDK puts its layout under
<dir>/v2-dev/for EVERY explicit cache directory:CHTYPES_CACHE, and also the binding's own option (GoFetchOptions.CacheDir, and its counterparts in the other bindings once they convert). A 1.x consumer treats that option as the layout directory itself, so code that inspects or pre-populates it will look in the wrong place.Fix (docs only):
spec/abi-v2/docs.mdr5 should say "any explicit cache directory, from the environment or the binding's option", where today it names only `CHTYPES_CACHE".Lands on the
v2branch.