ci(release): point the docs branch at every published release

[jdchawla29]

docs.hud.ai builds its SDK tab from the docs branch: normally the latest release, optionally plus docs-only commits shipped between releases. The release workflow force-pushes the released commit to docs after publishing to PyPI, so the pointer needs no manual maintenance; docs-only commits on the branch are contained in the released main by construction.

---

Note

Low Risk
CI-only change to a release workflow; the force-push to docs is intentional and scoped to the release commit SHA.

Overview
After each published release, the Release workflow now updates the docs branch so docs.hud.ai’s SDK tab builds from the same commit that was shipped to PyPI.

The deploy job gains contents: write permissions and a new step Point docs at this release that runs git push --force origin "${GITHUB_SHA}:refs/heads/docs" after uv publish. PyPI publishing is unchanged.

^{Reviewed by Cursor Bugbot for commit 616f90b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 35b55c8d2e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".