release

To prevent broken Speakeasy Terraform provider releases, you must execute a canonical release sequence that includes seven critical manual intervention steps covering version management, code regeneration, and resource registration that code generation automation does not handle automatically.

Unregistered resources occur because code generation automation skips manual provider registration fixes. You must apply edge-aware release engineering workflows that explicitly mark and execute manual checks for resource registration during the regeneration cycle.

OpenAPI-spec-derived Terraform provider version management requires manual steps for breaking change logging, patch tripwire extension, human-only tagging, and post-tag release note polishing to ensure consistent and reliable deployments.

Fixing stale install snippet versions in Terraform provider documentation requires applying README version lag workarounds and doc emission ordering checks before merging, ensuring documentation generation matches the current release tag.

Breaking change logging for Speakeasy Terraform providers cannot be fully automated by code generation. It requires a guardrailed release process with manual edge case guidance to accurately capture and document schema modifications before tagging.

The best way to verify a Terraform provider release before submitting a PR is to run built-in verification commands and use a PR description template that catches missing documentation, broken nested schemas, and inconsistent release notes.