Repository navigation
Conversation
- Update OpenWA image to 0.25.0 - Add 75s stop grace period for the longer bounded teardown
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
- Add mcp_enabled and mcp_readonly template variables - Pass MCP_ENABLED and MCP_READONLY to the container - Keep the read-only tool tier as the safe default
Add an enable_swagger variable, wired to ENABLE_SWAGGER, so /api/docs is served despite the upstream production default.
duducp
force-pushed
the
feat/openwa-0.25.0
branch
from
October 28, 2026 23:58
2afb307 to
6b4d613
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the OpenWA blueprint from 0.24.0 to 0.25.0, enables the MCP server by default, and keeps Swagger UI available.
Changes
ghcr.io/rmyndharis/openwato0.25.0stop_grace_period: 75sto match the upstream production teardown budget introduced in 0.25.0MCP_ENABLED=trueand expose themcp_enabledvariableMCP_READONLY=true), exposed asmcp_readonlyENABLE_SWAGGER=true, exposed asenable_swaggerThe hardened runtime settings are otherwise unchanged: the required
KILLcapability is already present, and the new optional variables in 0.25.0 (MESSAGE_INLINE_MEDIA,WEBHOOK_FAILURE_PAYLOAD_RETENTION_HOURS,STORAGE_IMPORT_MAX_TOTAL_BYTES) keep their upstream defaults.MCP
After deployment the server is reachable at
https://<domain>/mcp. MCP clients authenticate with an OpenWA API key.mcp_readonly = "true"(default): 25 read toolsmcp_readonly = "false": all 51 tools, including sends and mutationsThe docs recommend keeping
/mcpoff the public internet unless it is fronted by an authentication proxy, and using a dedicated, session-scoped operator key.Swagger
Swagger UI is reachable at
https://<domain>/api/docs. The template runs withNODE_ENV=production, where upstream disables Swagger by default, so the template explicitly setsENABLE_SWAGGER=true.The Swagger mount is not behind the API-key guard, so it exposes the API schema and the running version to anyone who can reach the instance. Set
enable_swagger = "false"to turn it off.Highlights in 0.25.0
PORTValidation
bun build-scripts/generate-meta.js --check: 586 templates validateddocker compose config -q: passesghcr.io/rmyndharis/openwa:0.25.0exists