[release] Release Highlights: v0.3.19
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- documentation, release
Research direction
This is a generated release-highlights issue for v0.3.19, not an implementation task, and it names no source file or test. Start with the release entry and its linked full release notes; the referenced pull requests provide the source for each highlight. Done means the published highlights accurately reflect the release.
Written by the indexing model from the issue text.
Description
Release highlights generated for v0.3.19 of MCP Gateway.
🌟 Release Highlights
This release focuses on security hardening, observability improvements, and documentation clarity — keeping MCP Gateway reliable and easier to operate.
✨ What's New
-
Improved DIFC security coverage — Closed GitHub guard gaps for
search_commitsand the feature-flaggedlist_issuesvariant, ensuring consistent information flow control across more MCP tools. (#6432) -
Standardized JSONL telemetry — Gateway RPC log records now include
eventand_schemafields with millisecond-precision timestamps, making structured log analysis and tooling integrations more reliable. (#6485) -
Rust guard integrity constants — Magic integrity strings in the Rust guard are replaced with named constants, reducing the risk of misconfiguration and improving maintainability. (#6470)
🐛 Bug Fixes & Improvements
- OpenTelemetry tracing fix — The
OTEL_SERVICE_NAMEenvironment variable now correctly overrides the tracing service name at runtime, ensuring traces are attributed to the right service. (#6344)
📚 Documentation
- Config examples are now directly linked from the Quick Start guide and configuration reference, making it easier to get started. (#6431)
- Guard-policy tag usage and stdin config behavior are clarified in the Quick Start. (#6434)
🐳 Docker Image
The Docker image for this release is available at:
docker pull ghcr.io/github/gh-aw-mcpg:v0.3.19
# or
docker pull ghcr.io/github/gh-aw-mcpg:latest
Supported platforms: linux/amd64, linux/arm64
For complete details, see the full release notes.
Generated by the release highlights workflow for v0.3.19. Workflow run: 26415884188.
- Dominant language
- Go
- Stars
- 181
- Forks
- 53
- Avg merge
- 7h 18m
- Merged PRs (30d)
- 206
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/gh-aw-mcpg
-
Difficulty 1/5 Under an hour Newbie friendliness 8/100
github/gh-aw-mcpg#14908 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 5/100
github/gh-aw-mcpg#14909 ·
Maintainers usually reply within 1 day
-
automation mcp-gateway test
Difficulty 1/5 Under an hour Newbie friendliness 5/100
github/gh-aw-mcpg#14907 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 4/5 1-2 days Newbie friendliness 15/100
github/gh-aw-mcpg#14890 ·
Maintainers usually reply within 1 day
-
[rust-guard] Rust Guard: dedupe issue_read sub-method skip conditionPossibly taken @lpcox claimed this today. Openrefactor rust-guard
github/gh-aw-mcpg#14878 · 1 reaction · 2 assignees ·
Maintainers usually reply within 1 day
All issues in github/gh-aw-mcpg
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[Bug]: Bedrock invoke-with-response-stream reports `stop_reason: "end_turn"` for tool-use turnsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
oalders/clodhopper#162 ·
Maintainers usually reply within 1 day
-
component/server severity/minor type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day