Repository navigation
Backlog 1130 (proposed): Context7 serves each package's current docs after every release - #71
Merged
Merged
Conversation
…after every release (context7.json per repo, claimed; refresh API after publish, key as a secret; what is not possible); overview row and counts
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.
Backlog 1130 (proposed): Context7 serves each package's current docs after every release
Test tier: light (documentation only).
The operator asked whether our
llms.txt/llms-full.txtand docs can be published to Context7 automatically. Theycan, through Context7's documented refresh API. This proposed item (
> Package: abstractframework (release), every package repo) records how, from Context7's docs read on 2026-11-05.Registration. Each public repository is one library (
/lpalbou/<Repo>, 23 repositories, all public). Acontext7.jsonat the repo root selects what is read:folders,excludeFolders,excludeFiles,projectTitle,description,rules,previousVersions/branchVersions; the schema is athttps://context7.com/schema/context7.json. Claiming addsurl+public_keyto the same file, which unlocks theadmin panel and higher refresh limits.
Refresh.
POST https://context7.com/api/v1/refresh,Authorization: Bearer <CONTEXT7_API_KEY>, body{"libraryName": "/owner/repo"}. It answers "Refresh started"; a429comes withRetry-After. Context7's own"GitHub Actions" setup is this call as a step, with the key in a repository secret. There is no packaged action.
Versions. A refresh re-parses a branch. A new major (on
0.x, a new minor) keeps the previous one's last releaseas an extra version. Older tags come from
previousVersionsor the admin panel.Not possible as documented:
Current state.
/lpalbou/abstractcoreis indexed but "updated 1 year ago", so agents get year-old docs today.AbstractRuntime and AbstractGateway are not indexed.
The item asks for:
context7.jsonper repo:docs/and the root llms files, with the internal pages of the llms rule andCHANGELOG.mdexcluded;abstract-releaseskillcalls, with the key kept as a secret and never in docs.
Acceptance: within N minutes of a release, a Context7 MCP query returns text that exists only in the new version, and
a failed refresh is never silent.
overview.mdgets a row, and the counts are recounted with the file's own method: Proposed 94 (83) / 91 (80).Local CI (ADR 0050)
scripts/ci_local.sh <wt> --jobs 4 --tier lighton 0162bf4 merged into main 66628ab, alone on the Mac: 2 pass (Test andbuild package, Bootstrap smoke ubuntu-latest). The light tier left out the macOS smoke test; the Windows one was skipped
(GitHub runs it). Log:
untracked/release-2026-11-03/w3/gate-root-1130-0162bf4-light.log.