ci: standardize docs workflow

[stefan-jansen]

Summary

• standardize the library docs deployment workflow on the shared website handoff pattern
• pin astral-sh/setup-uv to the official v8.1.0 commit from Astral's setup-uv documentation
• build docs with uv run mkdocs build and deploy site/ to website/static/docs/data/ when the deploy key is present

Notes

• preserves the existing website-side docs rendering and navbar injection contract
• keeps the deploy target and URL structure unchanged

[Copilot]

Pull request overview

Standardizes the docs CI workflow to match the shared “website handoff” deployment pattern, using uv to build MkDocs output and (optionally) pushing the built site/ to the website repository when a deploy key is available.

Changes:

• Pins astral-sh/setup-uv to a specific commit (v8.1.0) for more deterministic action behavior.
• Builds docs via uv run mkdocs build.
• Gates the deploy step so it only runs when DOCS_DEPLOY_KEY is present, and deploys site/ to website/static/docs/data/.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

cpina/github-action-push-to-another-repository@v1.7.2 is a third-party action referenced by a movable tag. Since this workflow uses an SSH deploy key, consider pinning this action to an exact commit SHA (and optionally documenting the corresponding version) to reduce supply-chain risk from tag retargeting.

[Copilot]

DOCS_DEPLOY_KEY is being exported at the job level, which makes the deploy key available to every step (including third-party actions like actions/checkout and astral-sh/setup-uv). To follow least-privilege, scope the secret to only the deploy step and use if: ${{ secrets.DOCS_DEPLOY_KEY != '' }} (or similar) instead of routing it through env at the job level.

[stefan-jansen]

Superseded by the later GitHub Actions/Dependabot maintenance PR that has already been merged to main.