Fix website monorepo cleanup regressions#2840
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
docs/**to the staging docs deploy trigger because the website docs source reads from the repository-leveldocsdirectory.next lint, avoiding the incompatible Turbo ESLint config path, and making the app ESLint config self-contained.@raofoundation/apiworkspace package so the website app only exposes the Fumadocs search API route.Production deployment note
Production website deployment in
watch-mainnet-release.ymlis intentionally not changed here. The Vercel/GitHub integration must be finished and validated before relying on that production release path.Validation
cd website && yarn install --immutablepassed.cd website && yarn turbo run build --filter=@raofoundation/bittensor-website... --forcepassed. The build route table showsƒ /api/searchas the only/apiroute.cd website && yarn workspace @raofoundation/bittensor-website run lintpassed with warnings only.find website/apps/bittensor-website/src/app -path "*api*" -type f | sortreturns onlywebsite/apps/bittensor-website/src/app/api/search/route.ts.rg "@raofoundation/api|workspace:packages/api|packages/api|/api/public/total_issuance|api/stats|CHAIN_STATS_ENDPOINT" website -g "!**/.next/**" -g "!**/node_modules/**"returned no matches.git diff --checkandgit diff --cached --checkpassed.