Fetch tags in registry publish workflow

[MattBabbage]

This pull request introduces automated publishing to the MCP Registry and adds a new server.json manifest describing the server and its package configuration. The main changes are the addition of a GitHub Actions workflow for publishing and the creation of a detailed MCP server manifest.

[Copilot]

Pull Request Overview

This PR introduces automated publishing to the MCP Registry by adding a GitHub Actions workflow and server manifest configuration. The changes enable the GitHub MCP server to be automatically published to the registry when version tags are created.

• Adds MCP Registry publishing workflow triggered by version tags
• Creates server.json manifest with package and environment configuration
• Configures OCI container registry integration for Docker-based distribution

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
server.json	New MCP server manifest defining package configuration, runtime arguments, and environment variables
.github/workflows/registry-releaser.yml	GitHub Actions workflow for automated registry publishing with version management

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The hardcoded version '0.0.0' should be dynamically updated. Consider using a placeholder or template variable that gets replaced during the build process to avoid manual version updates.

Suggested change

	"version": "0.0.0",
	"packages": [
	{
	"registryType": "oci",
	"registryBaseUrl": "https://ghcr.io",
	"identifier": "ghcr.io/github/github-mcp-server",
	"version": "0.0.0",
	"version": "${VERSION}",
	"packages": [
	{
	"registryType": "oci",
	"registryBaseUrl": "https://ghcr.io",
	"identifier": "ghcr.io/github/github-mcp-server",
	"version": "${VERSION}",

[Copilot]

This hardcoded version should match the root version field and be dynamically managed. Having multiple hardcoded version fields creates maintenance overhead and potential inconsistencies.

Suggested change

"version": "0.0.0",