Update docs workflow for new docs monorepo

[stevep0z]

Context / Motivation

The docs site has migrated from Antora (docs.openzeppelin.com) to Fumadocs (OpenZeppelin/docs). The current docs.yml workflow pushes to docs-v* branches for the retired Antora site and is no longer serving the production docs.

Proposal

Replace the existing docs workflow with a trigger that calls the new docs monorepo's receiver workflow. The docs monorepo handles template injection, docgen, link validation, and PR creation.

The new workflow:

• Triggers on release tags (v*) and supports manual dispatch
• Calls generate-api-docs-contracts.yml in OpenZeppelin/docs via gh workflow run
• Requires a DOCS_REPO_TOKEN secret (GitHub PAT with repo + workflow scopes)

Draft implementation: https://github.com/stevep0z/openzeppelin-contracts/tree/feat/docs-trigger-workflow

Related docs monorepo draft PR: OpenZeppelin/docs#140

[ernestognw]

Hey @stevep0z, thanks for opening this.

A few things to keep in mind about how the current workflow operates and what the new one should preserve:

Current behavior:

• The docs.yml workflow triggers on pushes to release-v* branches (not on tags).
• The update-docs-branch.js script has version-guarding logic: it refuses to update docs for non-major prereleases and checks that we're not overwriting docs from a newer minor version.
• PR previews are handled via Netlify deploy hooks (no workflow involved), so the new workflow only needs to cover the "push to production docs" path imo

For the new workflow:

• The trigger should remain on push to release-v* branches rather than on release tags, since that's how our release process works. The release branch is where the final state of the code lives when docs should be updated.
• The version-guarding logic from update-docs-branch.js (refusing non-major prereleases, refusing to overwrite newer versions) should either be preserved in the new trigger workflow or handled on the docs repo receiver side. We don't want a patch backport on release-v5.2 to overwrite docs generated from release-v5.4.
• The workflow should pass the branch/ref and version information to the docs receiver so it can determine the correct output path (e.g., content/contracts/5.x/api/).

Could you update the draft implementation to trigger on push to release-v* instead of tags, and clarify how the version guards will be handled? Happy to review once that's in place.