Revert "docs: clarify release deployment process and enable manual deploy trigger"

This reverts commit c40374c280.

docs/guides/contributing/releasing.md

@@ -16,34 +16,10 @@ The release workflow will automatically:
 
 ## After Release
 
-The release workflow will automatically:
-- Build and publish Docker images:
+- Docker images will be available at:
   - `ghcr.io/modelcontextprotocol/registry:latest` - Latest stable release
   - `ghcr.io/modelcontextprotocol/registry:vX.Y.Z` - Specific release version
-- Binaries will be available on the GitHub release page
-
-**Important:** Creating a release does **not** automatically deploy to production. Production deployments are triggered by pushes to the `main` branch.
-
-## Deploying the Release to Production
-
-After creating a release, you need to ensure production pulls the new `:latest` Docker image. You have two options:
-
-1. **Recommended:** Merge a commit to `main` (e.g., a changelog update or version bump). This will trigger the deployment workflow which will:
-   - Build and push a new `:main` Docker image
-   - Deploy to staging
-   - Deploy to production (which uses `:latest` and will pull the new image)
-
-2. **Manual restart (requires kubectl access):**
-   ```bash
-   kubectl rollout restart deployment/mcp-registry -n default
-   ```
-
-## Verifying the Deployment
-
-After deployment completes, verify the changes are live:
-- Check the deployment workflow succeeded: https://github.com/modelcontextprotocol/registry/actions/workflows/deploy.yml
-- Test the API endpoint to confirm schema changes are applied
-- Check migrations ran successfully in the pod logs
+- Binaries can be downloaded from the GitHub release page
 
 ## Docker Image Tags