v0.0.22

🌟 Release Highlights

This release improves log file accessibility, making it easier for monitoring tools and external processes to read MCP Gateway logs in real-time.

🐛 Bug Fixes & Improvements

• Enhanced Log Accessibility (#146): Removed file locking from gateway.log to enable concurrent read access by external processes
  • Immediate flushing: Log writes are now immediately visible to monitoring tools and tail commands
  • No lock contention: Eliminated syscall.Flock to prevent interference with log readers
  • Maintains permissions: Continues to use 0644 permissions for broad readability
  • Why it matters: Your monitoring dashboards, log aggregators, and tail -f commands can now read logs without delays or lock conflicts

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.22
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Remove file locking from gateway.log to enable concurrent read access by @Copilot in #146

Full Changelog: v0.0.21...v0.0.22

v0.0.21

🌟 Release Highlights

This maintenance release improves container version tagging and adds comprehensive HTTP backend testing to prepare for future HTTP transport support.

⚡ Improvements

• Container Version Tagging (#145): Docker images now correctly embed the release version (e.g., v0.0.21) instead of defaulting to "dev". When you run awmg --version in a release container, you'll see the actual release tag instead of generic "dev" output.

• HTTP Backend Testing (#144): Added integration test demonstrating HTTP MCP backend servers with authorization header validation. This lays the groundwork for future HTTP transport support, showing how backends can enforce spec-compliant authorization (plain API key format per MCP spec 7.1).

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.21
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

🔧 Technical Details

• Build system now passes VERSION build argument to embed git tags in compiled binaries
• Integration tests validate HTTP MCP servers with SSE (Server-Sent Events) protocol
• Authorization format follows MCP specification 7.1 (plain API key, not Bearer scheme)

---

For complete details, see the full release notes.

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Add integration test for HTTP MCP backend server with authorization headers by @Copilot in #144
• Add VERSION build arg to container builds for release tagging by @Copilot in #145

Full Changelog: v0.0.20...v0.0.21

v0.0.20

🌟 Release Highlights

This release enhances MCP Gateway's spec compliance with an improved health endpoint and authentication fixes.

✨ What's New

Spec-Compliant Health Endpoint (#140)
The /health endpoint now returns structured JSON with version information instead of plain text, making it easier to monitor gateway status and verify compatibility:

{
  "status": "ok",
  "protocolVersion": "2024-11-05",
  "version": "v0.0.20"
}

This change enables programmatic health checks and version verification for operational monitoring and CI/CD pipelines.

🐛 Bug Fixes & Improvements

API Key Authentication (#139)
Fixed authentication to use spec-compliant API key format. The gateway now correctly accepts Authorization: <apiKey> headers as defined in the MCP Gateway specification (section 7.1), removing the incorrect Bearer scheme requirement.

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.20
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

📚 Documentation

For configuration details and setup instructions, see:

• Configuration Specification
• README
• DIFC Integration Proposal

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Implement spec-compliant API key authentication (remove Bearer scheme) by @Copilot in #139
• Update /health endpoint to return JSON with protocol and gateway versions per MCP Gateway spec by @Copilot in #140

Full Changelog: v0.0.18...v0.0.20

v0.0.19

What's Changed

• Fix stdout sync error on pipes and character devices by @Copilot in #114
• Suppress CLI help on runtime errors by @Copilot in #117
• Log gateway version at startup by @Copilot in #116
• Add pipe-based gateway launch integration test by @Copilot in #115
• Add SECURITY policy file aligned with upstream guidance by @Copilot in #100
• Fix: Disable ANSI color codes in bash scripts when stderr is not a TTY by @Copilot in #123
• Add file locking to log file with shared read access by @Copilot in #125
• Add manual release workflow with admin role check by @Copilot in #127
• Add /close endpoint for graceful gateway shutdown by @Copilot in #126
• Delete manual-release.yml by @pelikhan in #130
• Add workflow_dispatch support to release workflow with automatic tag creation and validation by @Copilot in #131
• Recompile agentic workflows by @Copilot in #133
• Remove Windows, Darwin, FreeBSD from release builds by @Copilot in #134
• Fix agentics-maintenance workflow: install gh-aw instead of building from source by @Copilot in #135
• Remove Linux 386 builds from release pipeline by @Copilot in #138
• Add auth headers to MCP gateway stdout configuration output by @Copilot in #136
• Implement spec-compliant API key authentication (remove Bearer scheme) by @Copilot in #139

New Contributors

• @pelikhan made their first contribution in #130

Full Changelog: v0.0.13...v0.0.19

v0.0.18

🌟 Release Highlights

This release focuses on improving client integration and streamlining the build pipeline for better compatibility.

✨ What's New

• Auto-configured Authentication Headers: The MCP gateway now includes authentication headers in its stdout configuration output, eliminating the need for clients to manually add them. This aligns with the MCP specification and makes integration seamless—clients can now use the output configuration directly without modification.

🐛 Bug Fixes & Improvements

• Fixed Maintenance Workflow: Corrected the agentics-maintenance.yml workflow to properly install gh-aw instead of attempting to build from source, resolving build failures
• Streamlined Release Builds: Removed Linux 386 (32-bit x86) from the release pipeline to focus on modern platforms (amd64, arm, arm64)

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.18
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

For complete details, see the full release notes.

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Fix agentics-maintenance workflow: install gh-aw instead of building from source by @Copilot in #135
• Remove Linux 386 builds from release pipeline by @Copilot in #138
• Add auth headers to MCP gateway stdout configuration output by @Copilot in #136

Full Changelog: v0.0.17...v0.0.18

v0.0.17

🌟 Release Highlights

This release streamlines the MCP Gateway with operational improvements focused on reliability, usability, and simplified release management.

✨ What's New

• Manual Release Workflow - Trigger releases directly from GitHub Actions with automated tag creation and semantic versioning (#131, #127)

  • No command-line access needed - trigger via Actions tab with dropdown for patch/minor/major bumps
  • Automatic version calculation and validation ensures semver compliance
  • Admin role verification built-in for security

• Graceful Shutdown Endpoint - New /close endpoint for controlled gateway termination (#126)

  • Cleanly terminates all backend MCP servers before shutdown
  • Idempotent operation with proper HTTP status codes (200 OK → 410 Gone)
  • Authentication enforced when API key is configured

• Enhanced Log File Management - File locking for concurrent access and proper cleanup (#125)

  • Shared locks allow multiple processes to read logs while gateway writes
  • Automatic lock release on shutdown signals (SIGINT/SIGTERM)
  • Improves reliability for log monitoring and aggregation tools

🐛 Bug Fixes & Improvements

• Clean Terminal Output - ANSI color codes now disabled when stderr is not a TTY (#123)

  • Prevents raw escape codes in piped output and container logs
  • Respects NO_COLOR and DEBUG_COLORS environment variables
  • Aligned with Go logger behavior for consistent experience

• Streamlined Release Builds - Linux-only binaries reduce build time and release complexity (#134)

  • Produces 4 binaries (linux-386, linux-amd64, linux-arm, linux-arm64) instead of 12
  • Aligns with primary use case as a containerized service
  • Faster release pipeline and smaller artifacts

🔧 Internal Improvements

• Workflow Updates - Recompiled agentic workflows with enhanced GitHub MCP integration (#133)
  • Switched to native GitHub MCP tools for specification retrieval
  • Improved reliability by removing external web dependencies

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.17
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

Quick start:

docker run --rm -i \
  -e MCP_GATEWAY_PORT=8000 \
  -e MCP_GATEWAY_DOMAIN=localhost \
  -e MCP_GATEWAY_API_KEY=your-secret-key \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v $(pwd)/logs:/tmp/gh-aw/sandbox/mcp \
  -p 8000:8000 \
  ghcr.io/githubnext/gh-aw-mcpg:v0.0.17 < config.json

---

For complete details, see the full release notes.

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Remove Windows, Darwin, FreeBSD from release builds by @Copilot in #134

Full Changelog: v0.0.16...v0.0.17

v0.0.14

🌟 Release Highlights

This release focuses on improving reliability in containerized environments and enhancing the developer experience with better error handling and diagnostics.

✨ What's New

Pipe-Based Configuration Support (#115)

• MCP Gateway now supports launching via standard pipes and named FIFOs, ideal for containerized deployments
• Example: echo "$CONFIG_JSON" | awmg --config-stdin - perfect for Docker environments where file-based config isn't suitable
• Comprehensive integration tests ensure reliable stdin-based configuration

Version Logging at Startup (#116)

• Gateway version now logged on startup for easier operational troubleshooting
• Example: [INFO] [startup] MCPG Gateway version: v0.0.14
• Makes it simple to identify which version is running in production environments

Cleaner Error Messages (#117)

• Runtime errors now display without CLI help text clutter (4 lines instead of 27!)
• Error messages appear immediately and clearly - no more buried errors under usage text
• Flag parsing errors and --help still work normally

🐛 Bug Fixes & Improvements

Fixed Stdout Sync on Pipes (#114)

• Resolved sync /dev/stdout: invalid argument error in containerized environments
• Gateway now correctly detects pipes and character devices, avoiding unnecessary sync operations
• Added comprehensive test coverage for piped I/O scenarios

Enhanced JSON Schema Validation (#108)

• Improved schema validation with version information
• Disabled MCP input schema validation to prevent compatibility issues with MCP servers

Test Suite Improvements (#109, #103)

• Fixed Playwright integration test to use correct MCP image
• Cleaned up log message pollution in containerized runs
• More reliable test execution across environments

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.14
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

📚 Additional Resources

• Security Policy: Added SECURITY.md with disclosure guidelines (#100)
• SBOM Generation: Documentation for local SBOM generation using syft

---

For complete details, see the full changelog below.

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Fix log messages polluting command substitution in run_containerized.sh by @Copilot in #103
• Enhance JSON schema validation with version info and disable MCP input schema validation by @Copilot in #108
• Fix playwright integration test to use mcp/playwright image and verify tool registration by @Copilot in #109
• Fix stdout sync error on pipes and character devices by @Copilot in #114
• Suppress CLI help on runtime errors by @Copilot in #117
• Log gateway version at startup by @Copilot in #116
• Add pipe-based gateway launch integration test by @Copilot in #115

Full Changelog: v0.0.11...v0.0.14

v0.0.13

🌟 Release Highlights

This release enhances MCP Gateway's compatibility with diverse MCP servers and improves configuration validation feedback for developers.

✨ What's New

🔧 Multi-Version JSON Schema Support
MCP Gateway now gracefully handles backend MCP servers using different JSON Schema versions (draft-04, draft-07, etc.). Previously, servers like Playwright using draft-07 schemas could cause validation errors. The gateway now accepts tools from any compliant MCP server while maintaining strict validation for its own configuration files.

📋 Enhanced Configuration Error Messages
Configuration validation errors now include:

• Gateway version information for better issue reporting
• Hierarchical error display with clear context
• Specific suggestions for fixing each error type
• Direct links to the Configuration Specification and JSON Schema

This makes troubleshooting configuration issues significantly faster for developers.

🧪 Testing Improvements

• Added comprehensive integration tests for containerized Playwright MCP server
• Validates compatibility with real-world MCP servers using varied schema versions
• Improved test reliability with smarter Docker image handling

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.13
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

For complete details, see the full release notes.

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Enhance JSON schema validation with version info and disable MCP input schema validation by @Copilot in #108
• Fix playwright integration test to use mcp/playwright image and verify tool registration by @Copilot in #109

Full Changelog: v0.0.12...v0.0.13

v0.0.12

🌟 Release Highlights

This maintenance release fixes a critical bug in the containerized deployment scripts that prevented the gateway from starting properly.

🐛 Bug Fixes & Improvements

• Fixed command substitution capture issue (#103) - Resolved a problem where colored log messages were polluting command substitution in run_containerized.sh, causing the gateway to fail with unknown command errors. Log functions now properly write to stderr instead of stdout, ensuring clean separation between diagnostic output and program output.

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.12
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

For complete details, see the full release notes.

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Fix log messages polluting command substitution in run_containerized.sh by @Copilot in #103

Full Changelog: v0.0.11...v0.0.12

v0.0.11

🌟 Release Highlights

This release significantly improves MCP Gateway's reliability and compliance with enhanced validation, containerized execution support, and comprehensive testing infrastructure.

✨ What's New

Execution Environment Validation - MCP Gateway now validates its execution environment during startup, ensuring Docker daemon accessibility, required environment variables, and proper containerization setup. The new run_containerized.sh script provides specialized handling for containerized deployments with automatic validation of port mappings, stdin mode, and log directory mounts. PR #98

JSON Schema Validation - Configurations are now validated against the official MCP Gateway schema with regex constraints on all string fields. Invalid configurations fail fast with clear error messages and links to specification documentation. PR #94

Daily Compliance Checker - A new automated workflow continuously validates the implementation against the MCP Gateway specification, prioritizing recent changes and using cache memory to track validated aspects. Issues are created with detailed remediation suggestions and deep specification links. PR #93

⚡ Improvements

Split Test Suite - Tests are now organized into fast unit tests (no build required) and integration tests (binary required), enabling parallel CI execution and faster development feedback. New Makefile targets: test-unit, test-integration, and test-all. PR #82

Code Quality - Default values for command-line flags are now centralized as constants, improving maintainability and consistency throughout the codebase. PR #86

CI Alignment - Release workflow now uses standardized Makefile test targets (make test-unit, make test-integration) instead of raw go test commands, ensuring consistency across all workflows. PR #88

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.11
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

📚 Resources

• MCP Gateway Configuration Reference
• JSON Schema Specification
• Contributing Guide

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Constants for Default Values by @ppenna in #86
• Split test suite into unit and integration tests with separate CI jobs by @Copilot in #82
• Align release workflow with Makefile test targets by @Copilot in #88
• Validate JSON configuration against official MCP Gateway schema by @Copilot in #94
• Add daily compliance checker for MCP Gateway specification by @Copilot in #93
• Add execution environment validation for containerized MCP Gateway by @Copilot in #98

Full Changelog: v0.0.10...v0.0.11