docs(agents): document community and docs-version validators#148
Draft
tembo[bot] wants to merge 1 commit into
Draft
docs(agents): document community and docs-version validators#148tembo[bot] wants to merge 1 commit into
tembo[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Requesting review from @leoisadev1 who has experience with the following files modified in this PR:
|
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
Adds two standalone commands to the Release Checks section of
AGENTS.md:bun run community:check— validate the community plugin registry (apps/fumadocs/content/community/plugins.json).bun run docs:versions:check— check thatapps/fumadocs/src/lib/versions.tsmatches the latest publishedpackages/email-sdkversion.Why
Both scripts already exist in the root
package.jsonand run as part ofbun run release:ci, but AGENTS.md only referenced them generically ("community registry + docs version validation"). They are useful to run in isolation when editing just their inputs, rather than the full release gate. Documenting them next to the existingrelease:cinote keeps the guidance minimal and grounded.Grounding / verification
Both commands were run from the repo root and pass cleanly:
Scope kept to the one section that already mentioned these validations; no unrelated or auto-generated files were touched.