Skip to content

fix: resolve stale wasm golden files and missing serena.md test fixture #29370

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 2 commits into from
Apr 30, 2026
+12 −0
Merged

fix: resolve stale wasm golden files and missing serena.md test fixture #29370

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
139a050
Initial plan
Copilot Apr 30, 2026
d61b745
fix: verify CI failure resolution - wasm golden tests and missing ser…
Copilot Apr 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/src/content/docs/reference/frontmatter-full.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1682,6 +1682,18 @@ engine:
# (optional)
bare: true

# Engine-level MCP gateway configuration. Settings here apply to the MCP gateway
# used by this engine.
# (optional)
mcp:
# Session timeout for MCP gateway sessions as a Go duration string (e.g. "30m",
# "4h", "24h"). Must be at least 5m (no upper bound). Omitted or empty uses the
# effective gateway default (precedence: this field > MCP_GATEWAY_SESSION_TIMEOUT
# env var > built-in default 6h). Longer timeouts benefit multi-hour workflows
# such as large-scale migrations; shorter values free gateway resources sooner.
# (optional)
session-timeout: "example-value"

# Option 3: Inline engine definition: specifies a runtime adapter and optional
# provider settings directly in the workflow frontmatter, without requiring a
# named catalog entry
Expand Down
Loading