Skip to content

Backlog 1130 (proposed): Context7 serves each package's current docs after every release - #71

Merged
lpalbou merged 1 commit into
mainfrom
docs/backlog-1130-context7
Nov 5, 2026
Merged

lpalbou merged 1 commit into
mainfrom
docs/backlog-1130-context7

Conversation

@lpalbou

@lpalbou lpalbou commented Nov 5, 2026

Copy link
Copy Markdown
Owner

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.txt and docs can be published to Context7 automatically. They
can, 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). A
context7.json at the repo root selects what is read: folders, excludeFolders, excludeFiles, projectTitle,
description, rules, previousVersions / branchVersions; the schema is at
https://context7.com/schema/context7.json. Claiming adds url + public_key to the same file, which unlocks the
admin 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"; a 429 comes with Retry-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 release
as an extra version. Older tags come from previousVersions or the admin panel.

Not possible as documented:

  • refreshing one specific tag;
  • an "indexing finished" signal;
  • published rate-limit numbers;
  • private repositories without a paid plan.

Current state. /lpalbou/abstractcore is indexed but "updated 1 year ago", so agents get year-old docs today.
AbstractRuntime and AbstractGateway are not indexed.

The item asks for:

  • one claimed context7.json per repo: docs/ and the root llms files, with the internal pages of the llms rule and
    CHANGELOG.md excluded;
  • a refresh after each publish, either as a release-workflow step or as a root script the abstract-release skill
    calls, 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.md gets 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 light on 0162bf4 merged into main 66628ab, alone on the Mac: 2 pass (Test and
build 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.

…after every release (context7.json per repo, claimed; refresh API after publish, key as a secret; what is not possible); overview row and counts
@lpalbou
lpalbou merged commit 1eff8df into main Nov 5, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant