ci: post-merge fixes — Vercel deploy cwd, try-runtime snapshots, gittensor indexer#2865
ci: post-merge fixes — Vercel deploy cwd, try-runtime snapshots, gittensor indexer#2865unarbos wants to merge 3 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5937706 to
647ca2b
Compare
The Vercel project root directory (website/apps/bittensor-website) is resolved against the CLI cwd, so running from website/ doubles the path and vercel build fails with ENOENT.
🛡️ AI Review — Skeptic (security review)VERDICT: SAFE MEDIUM scrutiny by account age, mitigated by repository write access and substantial contributions; no Gittensor association. CI/deployment hotfix targets main. Static review found the workflow-only changes consistent with the documented failures. Since the prior SAFE verdict, the only addition changes the indexer from Python 3.11 to the pinned Gittensor dependency’s required Python 3.12. No review-policy files, runtime code, dependencies, permissions, triggers, or secret handling are changed. FindingsNo findings. ConclusionThe patch remains small and mechanical, with no apparent security vulnerability or malicious behavior. 🔍 AI Review — Auditor (domain review)VERDICT: 👍 UNKNOWN Gittensor association; established high-volume contributor with repository write access and substantial merged work. This deployment-only CI hotfix appropriately targets The overlap with broad monorepo PR #2841 is incidental rather than duplicate work. Static inspection was sufficient; runtime code, dependencies, and FindingsNo findings. ConclusionThe changes are minimal, internally consistent, and match the reported CI failures. Ready to merge. |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
--uri is variadic in try-runtime-cli, so a trailing positional snapshot path is consumed as a second URI value and fails validation. All three try-runtime snapshot jobs failed this way on the first dispatch.
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
The pinned gittensor commit declares requires-python >=3.12, so every scheduled run fails at pip install under the 3.11 setup.
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
|
Consolidated into #2867 (same commits merged there); closing to keep a single next-PR into main. |
Summary
Consolidated fixes for the CI breakages surfaced by the first post-merge runs on main:
vercel buildran fromwebsite/, but the Vercel project's root directory (website/apps/bittensor-website) is resolved against the CLI's cwd, doubling the path. Droppedworking-directory: websitefrom the staging deploy (deploy-docs.yml) and the production promotion (watch-mainnet-release.yml).refresh-mainnet-snapshot.yml,create-snapshot --uri <ws> <name>.snapfails because--uriis variadic and swallows the trailing snapshot path ("not a valid WS(S) url"). Moved the positional path before--uri. (The mainnet clone snapshot job in the same workflow succeeded and already published its artifact.)requires-python >=3.12; bumped the job's Python from 3.11 to 3.12 (pin unchanged).Related cleanup handled outside this PR:
Test plan