Skip to content

feat(http): implement HeaderAllowedFeatureFlags for X-MCP-Features header validation #3277

feat(http): implement HeaderAllowedFeatureFlags for X-MCP-Features header validation

feat(http): implement HeaderAllowedFeatureFlags for X-MCP-Features header validation #3277

Triggered via pull request April 15, 2026 11:58
Status Failure
Total duration 37s
Artifacts

docs-check.yml

on: pull_request
docs-check
33s
docs-check
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
docs-check
Process completed with exit code 1.
docs-check: pkg/http/server.go#L241
cannot range over knownFeatureFlags (variable of type func() []string): func must be func(yield func(...) bool): wrong argument count
docs-check: pkg/http/server.go#L240
invalid argument: knownFeatureFlags (variable of type func() []string) for built-in len
docs-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/