fix: alias staging docs via the deployments API

[unarbos]

Summary

• Every Deploy Docs run on main has failed at the final step with Error: You don't have access to the domain staging.bittensor.com under rao-foundation, because vercel alias set only accepts domains in the team-level domain registry while staging.bittensor.com is attached (and verified) at the project level.
• Replace the CLI alias with the Vercel deployments API (GET /v13/deployments/<url> to resolve the id, POST /v2/deployments/<id>/aliases), which honors project domains. curl -sf fails the step on any HTTP error.

Test plan

• Ran the exact resolve-and-alias pipeline locally against the latest deployment with the same token scope; the alias was applied and https://staging.bittensor.com serves it.
• After merge, confirm the Deploy Docs run goes green and staging.bittensor.com picks up the new deployment.

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
subtensor	Ready	Preview, Comment	Jul 13, 2026 9:09pm

[github-actions]

🛡️ AI Review — Skeptic (security review)

VERDICT: SAFE

BASELINE scrutiny: author has repository write access and substantial merged contribution history; no Gittensor association found. Branch fix-staging-alias → main.

Static analysis found the workflow change narrowly scoped to resolving the Vercel deployment ID and assigning the existing staging alias. Inputs interpolated into the requests come from trusted secrets, repository variables, or Vercel’s deployment response; no credential-exposure or command-injection path was introduced.

Findings

No findings.

Conclusion

The API-based alias operation preserves the workflow’s existing trust boundary and fails on HTTP or parsing errors. No security vulnerability or malicious behavior found.

---

🔍 AI Review — Auditor (domain review)

VERDICT: 👍

Gittensor association: UNKNOWN; established contributor with repository write access and substantial prior contributions.

The implementation matches the PR description: staging deployments now resolve the Vercel deployment ID and assign the project-level alias through the deployments API, while the production path remains unchanged. HTTP and response-parsing failures correctly fail the workflow step. No overlapping PRs were identified, and no runtime/spec-version change is involved.

Findings

No findings.

Conclusion

This is a focused, well-explained workflow fix with an appropriate test account and no substantive correctness issues found.

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍

[IntiTechnologies]

Superseded by #2898 (v431 release): these changes were reviewed and integrated there.