chore: add context7.json to claim the Context7 library - #70
Open
kuzdogan wants to merge 1 commit into
Open
Conversation
Context7 verifies ownership of the sourcify_dev library by fetching a JSON file with a public key from a URL under https://docs.sourcify.dev/docs. The file is placed in static/docs/, so Docusaurus copies it to build/docs/context7.json and it is served at https://docs.sourcify.dev/docs/context7.json. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying docs with
|
| Latest commit: |
99ad3f6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8ea1b25f.docs-8pb.pages.dev |
| Branch Preview URL: | https://chore-context7-claim.docs-8pb.pages.dev |
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
1 participant
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.
Adds
static/docs/context7.jsonso we can claim admin rights for the sourcify_dev library on Context7.Why
Context7 verifies that we own the docs site before it gives us admin rights over the library. The check is: host a JSON file with a public key that Context7 generated, at a URL under
https://docs.sourcify.dev/docs. Context7 then fetches that URL and compares the key.What changes
New file
static/docs/context7.json:{ "url": "https://context7.com/websites/sourcify_dev", "public_key": "pk_HiiA9OlLy1Bd0QgaG7iO0" }Docusaurus copies everything under
static/to the build output as-is. So this file becomesbuild/docs/context7.jsonand is served at:https://docs.sourcify.dev/docs/context7.json
I ran
npm run buildlocally and confirmed the file lands atbuild/docs/context7.jsonwith the correct content. It does not collide with any generated docs page, because the docs pages are directories with anindex.htmlinside.After merge
Once
maindeploys, enterhttps://docs.sourcify.dev/docs/context7.jsonin the "Claim Library" dialog on Context7 and click Claim Library.The
public_keyis a public value, meant to be published. It is not a secret.🤖 Generated with Claude Code