Move releases.md and update the deployment image reference from latest to main (#369)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following PR addresses the feedback comments from #366 

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->
No
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [x] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

deploy/pkg/k8s/registry.go

@@ -83,7 +83,7 @@ func DeployMCPRegistry(ctx *pulumi.Context, cluster *providers.ProviderInfo, env
 					Containers: corev1.ContainerArray{
 						&corev1.ContainerArgs{
 							Name:            pulumi.String("mcp-registry"),
-							Image:           pulumi.String("ghcr.io/modelcontextprotocol/registry:latest"),
+							Image:           pulumi.String("ghcr.io/modelcontextprotocol/registry:main"),
 							ImagePullPolicy: pulumi.String("Always"),
 							Ports: corev1.ContainerPortArray{
 								&corev1.ContainerPortArgs{

docs/guides/contributing/releasing.md

@@ -0,0 +1,38 @@
+# Release Guide
+
+## Creating a Release
+
+1. **Go to GitHub**: Navigate to https://github.com/modelcontextprotocol/registry/releases
+2. **Click "Draft a new release"**
+3. **Choose a tag**: Click "Choose a tag" and type a new semantic version that follows the last one available (e.g., `v1.0.0`)
+5. **Generate notes**: Click "Generate release notes" to auto-populate the name and description
+6. **Publish**: Click "Publish release"
+
+The release workflow will automatically:
+- Build binaries for 6 platforms (Linux, macOS, Windows × amd64, arm64)
+- Create and push Docker images with `:latest` and `:vX.Y.Z` tags
+- Attach all artifacts to the GitHub release
+- Generate checksums and signatures
+
+## After Release
+
+- 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 can be downloaded from the GitHub release page
+
+## Docker Image Tags
+
+The registry publishes different Docker image tags for different use cases:
+
+- **`:latest`** - Latest stable release (updated only on releases)
+- **`:vX.Y.Z`** - Specific release versions (e.g., `:v1.0.0`)
+- **`:main`** - Rolling tag updated on every push to main branch (continuous deployment)
+- **`:main-YYYYMMDD-sha`** - Specific development builds from main branch
+
+## Versioning
+
+We use semantic versioning (SemVer):
+- `v1.0.0` - Major release with breaking changes
+- `v1.1.0` - Minor release with new features
+- `v1.0.1` - Patch release with bug fixes