Add comprehensive documentation for the release process including version bumping, changelog generation, and deployment steps.
1.1 KiB
1.1 KiB
Releases
Creating a Release
- Create a new release on GitHub with a semver tag (e.g.,
v1.3.9) - This triggers the release workflow which:
- Builds
registryandmcp-publisherbinaries for all platforms using GoReleaser - Signs artifacts with cosign
- Generates SBOMs
- Builds and pushes container images to
ghcr.io/modelcontextprotocol/registry
- Builds
Deploying to Production
- Update
deploy/Pulumi.gcpProd.yaml(e.g., through a PR or by pushing directly to main):mcp-registry:imageTag: 1.3.9 - The deploy-production workflow automatically deploys
Staging
Staging auto-deploys from main via deploy-staging.yml. It always runs the latest main branch code.
Rollback
To rollback production, update deploy/Pulumi.gcpProd.yaml to the previous version and push.
Note: Rollbacks may not work as expected if the release included database migrations, since migrations are not automatically reversed.