perf: accelerate incremental API indexing - #7
Merged
Conversation
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
cmilesio
force-pushed
the
perf/harden-api-index-cache
branch
from
July 21, 2026 07:37
9a30069 to
a75399b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
RunCachedwith content-validated persistent artifacts and incremental typed-schema reuse.Why
Typed schema loading made large API indexes take seconds. This restores a fast development loop without reusing stale output after source, dependency, environment, local-replacement, cache-corruption, or concurrent-publication changes.
Validation
Compatibility and operations
RunCachedis additive,Runremains available, and the minimum Go version is unchanged. Publication now retains.webindex-artifacts.lockin output directories. Case-only artifact destinations are rejected because they alias on common filesystems; use unambiguously distinct names. Unsafe build configurations fall back to uncached indexing. JS/WASI publication locking is process-local because those targets expose no portable crash-safe cross-process lock.