v2.2.6
This release includes 76 updates covering feature enhancements, bug fixes, performance optimizations, and more.
- New Features: 2
- Bug Fixes: 49
- Refactoring & Optimizations: 8
- Documentation Updates: 10
- Test Improvements: 7
-
Related PR: #5328
Contributor: @higress-release-automation[bot]
Change Log: This PR prepares the plugin snapshot v2.2.6 release by introducing three JSON manifest files—evidence,plans, andsnapshots—to record version hashes, source commits, baseline commits, and plugin dependency relationships. It also updates theai-agentandai-cacheplugin versions to2.0.4.
Feature Value: Ensures traceability and verifiability of the plugin release process, improving version consistency and supply-chain security; users can reliably deploy specific plugin versions based on authoritative snapshots, reducing runtime anomalies caused by version mismatches. -
Related PR: #5263
Contributor: @sunxia0
Change Log: Introduces theserver.passthroughInstructionsconfiguration option, enabling optional passthrough of upstreaminstructionsstrings in MCP proxy discovery responses. It reuses existingRouteCalland authentication policies, safely extracting and injecting only valid instructions; excessively long or invalid values are automatically omitted from the field.
Feature Value: Enables the MCP gateway to flexibly preserve upstream services’ original instruction descriptions, enhancing completeness and traceability of tool discovery information; users may enable it on demand to avoid client behavioral deviations due to lost instructions, without disrupting existing authentication, routing, or error-handling semantics.
-
Related PR: #5323
Contributor: @johnlanni
Change Log: Upgrades the Istio submodule to commit383f79d, integrating an SRDS gateway cache fix: route caching now depends solely on the actually selected HTTP/HTTP3 gateways; modifications to unselected gateways precisely invalidate only corresponding host cache entries, eliminating O(n²)-complexity cache invalidation overhead.
Feature Value: Significantly improves configuration propagation speed and control-plane responsiveness under large-scale Ingress scenarios, avoiding latency jitter caused by global cache refreshes and enhancing gateway service stability and scalability; users experience faster application of route changes. -
Related PR: #5321
Contributor: @johnlanni
Change Log: Fixes a path traversal vulnerability arising from unescaped path parameters in REST-to-MCP request URLs. Addsurl.PathEscapefor path-segment escaping, multi-layer encoding validation (e.g.,%2e%2e), explicit enable/disable switches for unsafe path parameters, and supporting template functions—enhancing Nacos/registry configuration passthrough capabilities.
Feature Value: Prevents maliciously crafted path parameters from bypassing interface boundaries to access backend sensitive endpoints, improving MCP gateway security; default blocking of dangerous path patterns post-upgrade reduces risks of privilege escalation due to misconfigured templates, while providing secure migration options to ensure compatibility. -
Related PR: #5317
Contributor: @johnlanni
Change Log: Fixes an issue where requests may stall indefinitely causing503errors whenglobal_inflight_enabledis enabled. Changes the return value of the asynchronous scheduling path toHeaderStopAllIterationAndWatermark, ensuring callbacks correctly resume request processing.
Feature Value: Prevents users from encountering persistent503 cluster_not_founderrors after enabling global concurrency limiting, enhancing the stability and availability of the AI load balancer under high-concurrency scenarios and ensuring service continuity. -
Related PR: #5316
Contributor: @johnlanni
Change Log: Fixes a signature verification security vulnerability in thehmac-auth-apisixplugin by adoptingcrypto/subtle.ConstantTimeComparefor constant-time signature comparison and removing signature logging to prevent side-channel attacks and sensitive information leakage.
Feature Value: Enhances API authentication security by mitigating timing-attack risks that could allow signature bypass; simultaneously eliminates plaintext signature logs, satisfying security compliance requirements and protecting users’ keys and credentials from accidental exposure. -
Related PR: #5315
Contributor: @johnlanni
Change Log: Fixes strictness issues in the AI data sanitization plugin’s parsing of the OpenAIcontentfield. ModelscontentasOption<MessageContent>to support either string or content fragment arrays; mapsnull/missing values toNone, and rejects malformed structures with fail-closed behavior.
Feature Value: Improves plugin robustness and security, preventing silent parsing failures due to invalid OpenAI message bodies and ensuring malformed requests are explicitly intercepted with appropriate error responses—strengthening the API gateway’s ability to validate AI service protocol conformance. -
Related PR: #5311
Contributor: @zhihao-yuan
Change Log: Fixes ID confusion and incorrect usage statistics in Claude streaming responses caused by shared state across multiple concurrent requests. Moves state fields (messageId,usage,serviceTier) from provider-level to per-requestHttpContext, ensuring isolation of streaming responses.
Feature Value: Prevents users from receiving incorrect response IDs or mixed token usage data during concurrent Claude service calls, enhancing AI proxy service stability and billing accuracy, and ensuring reliability of streaming experiences in multi-user/multi-session contexts. -
Related PR: #5309
Contributor: @sunxia0
Change Log: Fixes MCP server SSE response parsing logic to prioritize standard'data: {...}'format matching; if no match occurs, the first whitespace-freedataline is cached as a fallback, preventing early whitespace-free notifications from overwriting subsequent valid-format responses.
Feature Value: Resolves backend compatibility issues, ensuring MCP services with varying SSE formats initialize and extract responses correctly; improves system robustness and cross-platform compatibility, reducing connection failures or data loss caused by format discrepancies. -
Related PR: #5305
Contributor: @sunxia0
Change Log: Fixes missing support for the2025-11-25MCP protocol version in the MCP server, extending initialization handshake logic to recognize and respond correctly to this version, while retaining the2025-06-18fallback mechanism and enforcing strict rejection of unknown versions.
Feature Value: Allows MCP clients to successfully complete initialization negotiation using the2025-11-25protocol version, improving protocol compatibility and service stability; avoids handshake failures due to unregistered versions, ensuring smooth coexistence and evolution of legacy and new tool clients. -
Related PR: #5294
Contributor: @johnlanni
Change Log: Fixes MCP user-level access control logic by binding user identity to the authenticated consumer, verifying consistency between the URL pathuidand the actual authenticated subject, strengthening401/403error responses, and refactoring Redis key generation logic to be based on(serverName, consumer)for user-level configuration and rate limiting management.
Feature Value: Strengthens MCP service security and permission isolation, preventing unauthorized access to user-specific services; users gain more precise personalized configurations, rate limits, and allowlist controls when enablinguser-level-server, avoiding privilege bypass risks due to path spoofing. -
Related PR: #5293
Contributor: @johnlanni
Change Log: Removes the dangerousx-higress-mcpserver-configrequest header during theDecodeHeadersphase at the Ingress layer and in MCP-related routing configurations, preventing its malicious construction and impact on dynamic user-level MCP server configuration—including coverage of custom VirtualService and controller-generated routes.
Feature Value: Enhances system security and configuration isolation by preventing clients from forging configuration headers that cause the server to misapply unintended MCP service configurations, ensuring reliable and independent MCP session configurations for each tenant in multi-tenant environments and lowering potential security and runtime anomaly risks. -
Related PR: #5292
Contributor: @johnlanni
Change Log: Fixes multi-tenancy data isolation issues in the AI cache plugin by incorporating consumer identity (x-mse-consumer) into SHA256 hash computation to construct versioned cache keys (v2:prefix+hex(consumer\0rawKey)), ensuring full isolation of cached data across authenticated consumers, with legacy unversioned keys automatically invalidated.
Feature Value: Prevents cross-user cache pollution or unauthorized access, improving AI service multi-tenancy security and reliability; cold starts triggered post-upgrade are expected behavior; English and Chinese READMEs have been updated synchronously with migration notes to reduce operational risk. -
Related PR: #5291
Contributor: @johnlanni
Change Log: Fixes a plugin request body validation defect by integratingwasm-go v1.2.0’sRequireRequestBody()API, ensuringext-authandhmac-auth-apisixplugins force-read and pass raw request bodies for binary, gRPC, and encoding-oriented Content-Types (e.g.,application/octet-stream) whenwith_request_bodyis enabled—avoiding body skipping due to type recognition mismatches.
Feature Value: Improves reliability and consistency of request-body–dependent authorization plugins, guaranteeing stable triggering of authorization calls regardless of requestContent-Typewhenwith_request_body:trueis configured—preventing authorization omissions or logic anomalies caused by undelivered bodies and strengthening API security protection. -
Related PR: #5289
Contributor: @johnlanni
Change Log: Fixes JSON Schema validation of request bodies supporting onlyobjecttype by adopting a defensive decoder directly handling raw byte streams, enabling validation of all top-level JSON types (array,string,number,boolean, and malformed JSON), thus avoiding validation skip due to deserialization failure.
Feature Value: Enhances robustness and security of API gateway request-body validation, ensuring non-object JSON (e.g., arrays, strings) is validated correctly and preventing illegitimate or unexpected JSON formats from bypassing validation logic—improving server-side data consistency and defensive capability. -
Related PR: #5288
Contributor: @johnlanni
Change Log: Fixes the default behavior ofsigned_headersin thehmac-auth-apisixplugin: when not explicitly configured, it now defaults to signing thedateheader, binding the request signature to a timestamp and enablingclock_skewvalidation; previously, omission resulted in staticstring-to-signcontaining only the key ID, completely losing replay protection and timeliness guarantees.
Feature Value: Enhances HMAC authentication security and compatibility, aligning plugin behavior with Apache APISIX semantics; users obtain date-based clock skew validation out-of-the-box without additional configuration, effectively defending against replay attacks and reducing security risks from missing critical signed headers. -
Related PR: #5287
Contributor: @johnlanni
Change Log: Adds configurable Redis failure handling modes (fail_open/fail_closed) to thecluster-key-rate-limitandreplay-protectionplugins, uniformly handling all Redis exception types, and ensuringfail_closedreturns a fixed503without emitting theX-RateLimitheader to distinguish infrastructure failures from business rate limiting.
Feature Value: Enhances plugin reliability and observability when Redis is unavailable; users can select degradation strategies according to business tolerance:fail_openensures service availability, whilefail_closedstrictly blocks requests and clearly signals infrastructure failure, aiding rapid root-cause diagnosis by operations teams. -
Related PR: #5283
Contributor: @lxcxjxhx
Change Log: Fixes a header-skip order bug in the canary feature: the original logic skipped header checks before evaluatingrewrite.host, causing non-HTML requests that should have been skipped still injectedx-higress-tagand rewrote:authority.
Feature Value: Ensures requests matchingskippedByHeadersconfigurations (e.g., API requests) are correctly skipped from canary processing, avoiding unnecessary header injection and host rewriting—improving routing accuracy and service stability, which is critical for users relying on headers to control canary behavior. -
Related PR: #5282
Contributor: @sunxia0
Change Log: Fixes compatibility issues between Modern and Legacy business logic in the MCP server: unifies request budgeting, tool execution sharing, and descriptor handling, removes redundant schema preparation logic, and ensures HTTP error responses correctly retain historicalRetry-After/WWW-Authenticateheaders.
Feature Value: Improves MCP service stability and consistency in hybrid deployment scenarios, preventing request failures or authentication anomalies due to split business policies and ensuring seamless user migration during upgrades—lowering operational complexity and compatibility risk. -
Related PR: #5277
Contributor: @qinfeng0214
Change Log: Fixes token usage undercounting in streaming SSE responses caused byusagefield fragmentation across chunks, introducingsseFramerfor unified frame parsing and performing deferred parsing of incomplete tail segments atendOfStream, ensuring accurate counting of everyusageevent.
Feature Value: Resolves token usage undercounting in AI services’ streaming-response scenarios, safeguarding quota control and rate-limiting accuracy—preventing users from being erroneously rate-limited or overspending, thereby enhancing billing and resource-management reliability. -
Related PR: #5273
Contributor: @qinfeng0214
Change Log: FixesoutputParserpanics caused by slice-out-of-bounds errors when encountering single code fences or nonstandard model outputs, enhances boundary-checking logic, and adds comprehensive unit tests covering various anomalous response scenarios.
Feature Value: Improves AI proxy robustness and stability, preventing service crashes due to minor model output formatting deviations and ensuring reliable and available AI capability invocation for users in real-world scenarios. -
Related PR: #5270
Contributor: @qinfeng0214
Change Log: Fixes erroneous acceptance of negativekv_cache_usage_percsamples in KV cache utilization metrics by adding validation for negative values inParseCompactVLLMMetrics, preventing incorrect mapping to1.0(maximum score) viatransformOneMinus, which would reverse routing logic.
Feature Value: Prevents AI endpoint misrouting due to metric anomalies, ensuring overloaded endpoints are not mistakenly deemed idle—improving service routing accuracy and system stability and guaranteeing users’ requests are correctly distributed to genuinely available inference nodes. -
Related PR: #5260
Contributor: @Metastarx
Change Log: Fixes potential overriding of user-managed Secrets during automatic HTTPS certificate renewal by adding Secret annotation validation logic: only Secrets managed by Higress are allowed for update, and domain matching is enforced, alongside improved error log handling.
Feature Value: Prevents accidental overwriting of user-defined TLS certificates, enhancing system security and stability; users can confidently manage their own Secrets without risking service disruption or credential loss due to certificate updates, strengthening production environment reliability. -
Related PR: #5242
Contributor: @dxz0069
Change Log: FixesMessageWindow::pop()panic caused by unchecked length in non-UTF-8 streaming response bodies, adding an early-return guard (len <= byte_window_size) in the non-UTF-8 branch to prevent mid-response crashes.
Feature Value: Improves stability and robustness of the AI data sanitization plugin when processing abnormally encoded streaming responses, preventing service interruption due to invalid byte streams—ensuring continuity and reliability of user API calls. -
Related PR: #5224
Contributor: @lljjcc426
Change Log: Fixes incorrect UTF-8 multibyte character truncation in thetruncateStringfunction of thejsonrpc-converterplugin by locating the nearest rune start position (utf8.RuneStart) to ensure prefixes and suffixes are valid UTF-8 strings—avoiding invalid UTF-8 sequences in header values.
Feature Value: Prevents invalid UTF-8 sequences in HTTP headers resulting from truncation, avoiding downstream service parsing failures or security-triggered blocks; improves internationalization compatibility and stability of JSON-RPC and MCP protocols, ensuring proper passthrough of Unicode-character–containing request headers (e.g., Chinese). -
Related PR: #5219
Contributor: @zhaohai666
Change Log: Adds strict validation of themodeparameter in thecluster_metricsload-balancing strategy, accepting only four legal values (LeastBusy,LeastFirstTokenLatency,LeastTotalLatency,Adaptive); illegal values trigger immediate errors and initialization rejection to prevent silent fallback to uniform random routing.
Feature Value: Prevents undetected load-balancing strategy failures caused by typos, case mismatches, or missingmodevalues, improving configuration reliability and operational observability—ensuring AI traffic distribution adheres to intended policies and avoiding potential performance degradation. -
Related PR: #5216
Contributor: @qinfeng0214
Change Log: Fixes incorrect host counter rollback in theglobal_least_requestload-balancing strategy: when RedisEVALreturns an exception orSetUpstreamOverrideHostfails, already-incremented host counters were not reverted, causing subsequent requests to incorrectly avoid that host.
Feature Value: Improves accuracy and stability of the AI load balancer, preventing traffic distribution skew and prolonged erroneous host exclusion caused by inaccurate counters—ensuring high service availability and optimal resource utilization. -
Related PR: #5209
Contributor: @zhihao-yuan
Change Log: Refactors streaming response handling logic, separating text-content and protocol-event processing; adds full support fortool call,role,refusal, unknown fields, and error events; optimizes end-frame and empty-frame handling to prevent tool-call content loss and premature consumption of[DONE].
Feature Value: Fixes loss of tool-call names and parameters in streaming responses within the AI data sanitization plugin, ensuring agents correctly receive and execute tool calls—significantly improving Higress’s stability and compatibility as an AI gateway in complex agent scenarios. -
Related PR: #5208
Contributor: @BenRobinson-hub
Change Log: Fixes request hanging in the OPA plugin upon synchronousDispatchHttpCallfailure by modifying theopaCallfunction to send503responses instead of indefinite suspension on synchronous errors—avoiding downstream client timeouts—and adds unit test coverage for synchronous call errors.
Feature Value: Enhances reliability and observability of the OPA policy decision service, preventing indefinite Envoy proxy request hangs due to upstream OPA service unavailability—ensuring rapid failure and clear error responses for user requests and reducing cascading failure risk. -
Related PR: #5205
Contributor: @Metastarx
Change Log: Adds read-write mutual exclusion locks to the Nacos MCP registry, encapsulating access to shared data structures—tool descriptors, RPC contexts, service sets, and listeners—within lock-protected helper functions to avoid fatal errors from concurrent reads/writes.
Feature Value: Fixes gateway crashes under high concurrency due to race conditions, significantly improving service stability and reliability—ensuring the Nacos registry operates normally during continuous refreshes and multi-request access, lowering production environment failure risk. -
Related PR: #5204
Contributor: @tju-yxq
Change Log: Fixes connection leakage in the Eureka HTTP client caused by un-closed response bodies and correctsRetryDelayTimeunits to milliseconds to ensure retry delay configuration takes effect properly; adds comprehensive unit tests covering related logic.
Feature Value: Avoids resource exhaustion and memory leaks caused by unclosed HTTP connections, improving long-term stability of the service registry; correct retry delay time interpretation makes fault recovery behavior more predictable and enhances system resilience during Eureka outages. -
Related PR: #5199
Contributor: @lizexinxin
Change Log: Fixes incorrect application of SSL redirect annotations to MCP server Ingress resources by adding MCP server Ingress detection and skipping logic in the redirect parsing routine, supplemented with corresponding unit tests to verify correctness.
Feature Value: Prevents unintended redirection of MCP server traffic, ensuring HTTP/TLS listeners correctly point to target clusters—improving accuracy and stability of multi-cluster service routing and guaranteeing control-plane communication reliability. -
Related PR: #5145
Contributor: @NUAAwqy
Change Log: Fixes the ignored--agentrunflag in thehgctl agent deploycommand: declares thecloudvariable earlier indeploy.goand passes it correctly toDeployHandler, and correctsgetAgentTypelogic to avoid overwriting user-specified deployment types.
Feature Value: Users can now truly control agent deployment targets (local vs. cloud) via the--agentrunflag, resolving the prior issue where this parameter was effectively inert—enhancing CLI tool reliability and documentation trustworthiness, ensuring automation workflows execute as intended. -
Related PR: #5144
Contributor: @yx9o
Change Log: Fixes HTTP500errors in the AI JSON Response plugin when no JSON schema is provided, caused by attempting to compile an empty schema. Adds conditional logic to enable compilation and validation only whenjsonSchemais present, preventing nil-map-to-null conversion exceptions.
Feature Value: Users no longer encounter unexpected500errors when invoking AI APIs in schema-free mode—significantly improving service stability; retains existing schema-based functionality and error-code semantics (e.g.,1001remains unchanged), ensuring backward compatibility and observability. -
Related PR: #5126
Contributor: @Metastarx
Change Log: Fixes panics in theai-ragplugin caused by unvalidated empty embedding arrays in embedding interface responses, adding status-code checks, JSON deserialization error handling, and explicit rejection logic for empty embedding arrays—enhancing robustness.
Feature Value: Prevents plugin crashes and request failures due to abnormal upstream service responses (e.g., quota exceeded,5xxerrors, invalid JSON)—improving RAG functionality stability and user-experience reliability, ensuring production-service continuity. -
Related PR: #5124
Contributor: @johnlanni
Change Log: Adds theDuplicateTopLevelMemberhelper function, detecting duplicate top-levelmodelfields in request bodies via single-pass structural scanning to avoid JSON parsing ambiguity; performs pre-validation in the AI load balancer and returns400errors to halt subsequent routing, auth, and mapping logic.
Feature Value: Enhances robustness and consistency of OpenAI-compatible interfaces, preventing unpredictable routing or auth behaviors caused by duplicatemodelfields—ensuring users receive clear error feedback, lowering debugging costs, and improving API reliability. -
Related PR: #5122
Contributor: @johnlanni
Change Log: Enforces HTTP Basic authentication for the MCP server database server type (GORM backend) during configuration parsing, validating non-emptyusername/password, aligning database service authentication behavior with RAG service—improving security.
Feature Value: Prevents unauthorized access to the database MCP service, avoiding sensitive data leakage; requires users to provide valid credentials in configuration, raising the security baseline for production environments and complying with least-privilege principles and enterprise security compliance requirements. -
Related PR: #5121
Contributor: @Metastarx
Change Log: Fixes inconsistent message publishing and subscription for MCP SSE sessions during Redis backend hot updates: binds each SSE session to its initial Redis client to prevent mixing old/new Redis clients due to filter config hot updates—ensuring messages always remain in closed-loop transmission within original pub/sub channels.
Feature Value: Guarantees strong consistency and reliability of MCP SSE sessions, preventing response loss or corruption in user sessions; improves system stability during dynamic configuration updates, lowering operational complexity and online failure risk. -
Related PR: #5092
Contributor: @Metastarx
Change Log: Fixes theqwen3guardplugin returning non-streaming JSON responses forstream=truerequests, adding SSE streaming denial-response support; dynamically selectsContent-Typeand response format by parsing thestreamfield in requests and updating README documentation.
Feature Value: Aligns interception denial responses with the client’sstreamflag, resolving empty-message display issues in streaming clients like Dify caused by missingdata:frames—improving compatibility and user experience, ensuringdenyMessagerenders correctly in workflows. -
Related PR: #5085
Contributor: @Metastarx
Change Log: Fixes panics inai-proxywhen parsing malformedcontentsections (e.g., emptyimage_urlobjects, non-string fields, missinginput_audio/filefields) by returning structured error responses instead—enhancing service robustness.
Feature Value: Prevents service crashes due to noncompliant user messages, improving API stability and availability; users receive clear error prompts instead of500responses, facilitating rapid identification and correction of request data issues. -
Related PR: #5083
Contributor: @Metastarx
Change Log: Fixes invalid JSON formatting in AI proxy plugin streaming SSE responses: the original hand-written JSON template failed to JSON-escape model outputs, breaking JSON structure with quotes, backslashes, and newlines, andtrimoperations erroneously removed legitimate leading/trailing quotes; replaced with standard JSON serialization to ensure valid SSE frames.
Feature Value: Ensures all standards-compliant SSE clients can correctly parse AI streaming responses, avoiding conversation interruption or display anomalies caused by JSON parsing failures—improving plugin stability and compatibility in production, especially critical for frontend applications strictly adhering to SSE specifications. -
Related PR: #5082
Contributor: @Metastarx
Change Log: Fixestokenrate limiter panics andfail-openbypass caused by malformedreal-IPrequest headers (e.g.,]or]:80); replaces vulnerablestrings.Splitwith safestrings.TrimPrefixfor IPv6 bracket removal and enhances IP parsing robustness.
Feature Value: Prevents attackers from bypassing rate limiting via maliciousreal-IPheaders, ensuring mandatory enforcement of AI token rate-limiting policies; improves gateway stability and security under anomalous traffic, avoiding critical protection failures due to panic recovery. -
Related PR: #5080
Contributor: @zhihao-yuan
Change Log: Fixes token undercounting and omission in non-streaming JSON responses: fully buffersapplication/jsonresponses hitting rate-limit rules before parsing to avoid incomplete JSON parsing from fragmented responses; optimizes MIME-type recognition to support case-insensitivity and parameters, excluding nonstandard cases like JSONP.
Feature Value: Improves accuracy of AI token usage statistics, ensuring rate-limiting policies enforce strictly; prevents undetected overspending due to undercounting, safeguarding service stability and billing compliance; users gain more reliable rate limiting without modifying business code. -
Related PR: #5079
Contributor: @Metastarx
Change Log: Fixes GraphQL variable injection vulnerabilities: enforces strict type validation and JSON escaping forInt/Float/Booleanvariables to prevent attackers from injecting arbitrary fields into thevariablesobject via malicious query parameters—preventing server-side logic tampering.
Feature Value: Enhances GraphQL gateway security, preventing privilege escalation or service anomalies caused by variable pollution; users gain protection without modifying business code, lowering API exploit risk and strengthening production environment stability. -
Related PR: #5029
Contributor: @sunxia0
Change Log: Fixes MCP server main-route proxy compatibility issues, restoring correct integration of HTTP MCPtools/listandtools/callwith theRouteCallSDK underlegacy/modern/autostrategies—ensuring request filtering, header/path rewriting, timeout, retry, and hashing policies work properly, while maintaining control-RPC execution as sidecalls.
Feature Value: Resolves tool-call failure issues in MCP services under multi-strategy routing, improving routing compatibility and stability; users restore cross-strategy tool-call capability without changing existing configurations and ensure correct passthrough of critical contextual headers (e.g.,Cookie, tenant headers), lowering upgrade risk. -
Related PR: #5000
Contributor: @Metastarx
Change Log: Fixesindex-out-of-rangepanics in Chroma vector provider’sparseQueryResponsefunction when handling empty responses (e.g., missingidsfield or emptyidsarray), adding boundary checks and error-handling logic to ensure HTTP callbacks complete normally and invokehandleQueryResults.
Feature Value: Prevents entire AI cache query requests from hanging or crashing due to abnormal empty Chroma service responses (e.g., unknown collection errors, emptyidsarrays)—improving system stability and fault tolerance, ensuring continued availability of AI-related features for users. -
Related PR: #4950
Contributor: @yyqdbngt
Change Log: FixesParseIPpanic caused by empty-string slicing when parsing malformed IPv6-formattedReal-IPheaders (e.g.,']'or']:80') by adopting safe substring extraction logic and adding boundary checks.
Feature Value: Prevents attackers from triggering cluster rate-limiting plugin crashes via maliciousX-Forwarded-Forheaders, improving gateway stability and security when per-IP rate limiting relies on header-extracted IPs. -
Related PR: #4948
Contributor: @yyqdbngt
Change Log: Fixesgeo-ippluginParseIPpanic when processing malformedReal-IPheaders (e.g.,"]"or"]:80") caused by empty-string slicing, replacingstrings.Splitwithstrings.TrimPrefixfor safe IPv6 address extraction and enhancing boundary validation.
Feature Value: Prevents WASM plugin crashes triggered by maliciousX-Forwarded-Forheaders, improving gateway stability and security in proxy scenarios and ensuring service availability under anomalous traffic. -
Related PR: #4946
Contributor: @btlqql
Change Log: Fixes unescaped user-inputpromptin upstream request-body construction for the ChatGPT proxy plugin by importing theencoding/jsonpackage and usingjson.Marshalto safely serializepromptand other fields—preventing JSON formatting errors or semantic tampering caused by quotes, backslashes, and newlines.
Feature Value: Prevents API request failures or silent content modification caused by malicious/special-character prompts, improving service stability and security; users submitting prompts with quotes, backslashes, or newlines can transmit them accurately to upstream models—ensuring interaction consistency and reliability. -
Related PR: #4944
Contributor: @btlqql
Change Log: Fixes panics in the IP restriction plugin when parsing malformedReal-IPrequest headers (e.g.,']'or']:80') caused by empty-string slicing, adopting safe string-trimming logic and adding boundary validation.
Feature Value: Prevents WASM plugin crashes triggered by maliciousX-Forwarded-Forheaders, improving gateway robustness and security when IP sources are header-configured—avoiding service interruption risks. -
Related PR: #4882
Contributor: @Metastarx
Change Log: Fixes nil-pointer dereference inFilterGrayRuleof thefrontend-grayplugin when rules arenil, adding safety checks forGetRulereturningnil, and introducing gray-deployment-and-rule-name consistency validation during config parsing to prevent silent failure due to missing rules.
Feature Value: Prevents panic-induced silent swallowing byrecoverFuncin canary releases caused by config mismatches, ensuring configuration errors surface promptly and fail fast—improving canary stability and observability and guaranteeing reliability of user traffic routing.
-
Related PR: #5330
Contributor: @johnlanni
Change Log: This PR primarily updates the project version number: upgradesVERSIONfile andappVersioninhelm/coreandhelm/higress Chart.yamlfrom2.2.5to2.2.6, and synchronizes thehigress-coredependency version inChart.lockto ensure Helm chart version consistency.
Feature Value: Provides users with a standardized v2.2.6 release package, ensuring strict version alignment of all components (core, console, plugin-server) during Helm deployments—improving installation stability and reproducibility and lowering operational upgrade risk. -
Related PR: #5324
Contributor: @johnlanni
Change Log: Upgrades Envoy data-plane dependencies to version1.36.12, updating submodule commits, Go module replacement paths, and build image URLs, and synchronizing references to amd64/arm64 multi-architecture release packages—ensuring build consistency and upstream compatibility.
Feature Value: Enhances Higress gateway security, stability, and performance; users transparently benefit from Envoy’s latest patches and optimizations, lowering potential vulnerability risks and improving deployment reliability and compatibility across multi-architecture environments. -
Related PR: #5319
Contributor: @johnlanni
Change Log: Modifies CI workflows to automatically publish WASM content formcp-server v2.0.3to legacy paths (1.0.0/2.0.0) duringplugin-serverbuilds, and adds compatibility tests verifying this behavior—ensuring legacyWasmPluginCRs continue loading without modification.
Feature Value: Ensures smooth upgrades for existing users, preventing runtime loading failures due to plugin path changes; lowers migration cost and enhances backward compatibility and stability—especially critical for production plugin configurations relying on fixed paths. -
Related PR: #5314
Contributor: @johnlanni
Change Log: Unifies and explicitly pins the Go toolchain version in CI/CD workflows to1.26.10, replacing prior dynamic reading viago.mod, adds toolchain version pinning and verification guidance toRELEASE.md, and cleans up obsoleteGO_VERSIONvariables inprebuild.sh.
Feature Value: Improves reproducibility and consistency of release builds, avoiding toolchain version drift due to differinggodirectives in modules; users receive more stable, verifiable binary artifacts, strengthening security audit and compliance capabilities. -
Related PR: #5312
Contributor: @johnlanni
Change Log: Changes the controller’s xDS gRPC listener address from wildcard binding (:15051/:15010) to loopback-only binding (127.0.0.1), and removes the exposed plaintext xDS ports15010and15051from the Service—tightening the default network attack surface.
Feature Value: Enhances controller security by preventing non-local components from accidentally accessing sensitive xDS interfaces; reduces attack surface, aligning with the principle of least privilege—functionally transparent to users but strengthens production deployment security baselines. -
Related PR: #5276
Contributor: @johnlanni
Change Log: Removesgolangci-lintsource dependencies (go.mod/go.sum/pin.go) in favor of the official precompiled binaryv2.15.0, secured via fixed SHA-256 checksum validation; migrates configuration tov2schema while retaining the 10-minute timeout limit.
Feature Value: Reduces build dependency complexity and security risk, accelerating CI lint-stage execution; avoids indirect dependency contamination of the project module graph, improving maintainability and reproducibility; no functional impact for end users but strengthens the stability and compliance of the code-quality assurance system. -
Related PR: #5125
Contributor: @johnlanni
Change Log: Replaces error-pronefmt.Sprintfstring concatenation for generating MCP server filter configurations in Ingress with typed-struct–basedencoding/jsonserialization—enhancing automatic field-value escaping and type safety, and unifying rendering logic.
Feature Value: Improves robustness and maintainability of configuration generation, avoiding Envoy configuration failures caused by JSON injection or formatting errors—making Ingress rule matching more stable and reliable, indirectly enhancing accuracy and security of user service routing and traffic management. -
Related PR: #5123
Contributor: @johnlanni
Change Log: Disables server reflection for xDS configuration push gRPC listeners in production environments to prevent easy enumeration of services and RPC interfaces; adds new unit tests explicitly locking down default gRPC configuration to enhance traceability of config changes and regression protection.
Feature Value: Enhances controller security in production environments by reducing the attack surface; locking default configuration via tests improves system stability and maintainability and reduces potential runtime anomalies caused by implicit config changes—delivering significant value to operations and security teams.
-
Related PR: #5318
Contributor: @johnlanni
Change Log: Fixes four lingering Git conflict markers (<<<<<<<,=======,>>>>>>>) in the MCP server Chinese README, adjusts the positions of sections “Main Request Forwarding Compatibility” and “Explicitly Deferred Scope” to align with the English version structure—ensuring readability and maintainability.
Feature Value: Eliminates confusing conflict markers in documentation, improving user reading experience and technical documentation credibility; unifies Chinese/English README structure, lowering multilingual maintenance cost and preventing developers from misconfiguring due to misinterpreting conflict content. -
Related PR: #5206
Contributor: @tju-yxq
Change Log: Corrects erroneous descriptions in migration documentation regarding Nginx annotation compatibility: removes 12 authentication-related annotations Higress does not implement (e.g.,auth-type/auth-secret/auth-realm), retaining only truly supported annotations, and synchronizes mapping relationships inannotation-mapping.md.
Feature Value: Prevents users from misusing unsupported Nginx authentication annotations causing configuration failures or behavioral anomalies—improving documentation accuracy and migration reliability; helps developers quickly identify genuinely available Higress-native annotations, lowering migration cognitive load and debugging time. -
Related PR: #5054
Contributor: @dusk5-Surtr
Change Log: Corrects spelling errors in multiple plugin READMEs and code comments, including'Json Web Toke'→'Json Web Token','ture'→'true', etc., identified and fixed using the project’s built-incodespellchecker—no functional or behavioral changes involved.
Feature Value: Improves documentation professionalism and readability, avoiding user misunderstandings caused by typos—especially ensuring accuracy of key terms like Boolean values in configuration instructions, enhancing developer confidence in plugin functionality and correct usage. -
Related PR: #5036
Contributor: @sunxia0
Change Log: Synchronizes Chinese/English READMEs and official website guides for the MCP Server plugin, embedding complete configuration documentation (including protocol strategies, toolsets, REST tools, credential handling, proxy examples, andmcp-routersource links) directly into the plugin repository docs, removing website-specific metadata and standardizing whitespace.
Feature Value: Improves developer experience by enabling one-stop, authoritative configuration documentation access within the repository—eliminating need to navigate to the website for MCP Server plugin deployment and debugging, lowering entry barriers and enhancing doc maintainability and multilingual consistency. -
Related PR: #5030
Contributor: @Black-Break
Change Log: Corrects two critical errors in thewasm-goplugin README: thefrontend-grayplugin’s incorrect injection field name (should beinjection.body.first/last, notafter) and theip-restrictionplugin’s HTTP header name casing error (x-real-iP→x-real-ip), ensuring strict documentation–code alignment.
Feature Value: Prevents users from misconfiguring plugins due to referencing incorrect documentation, improving configuration accuracy and out-of-the-box experience; particularly, fixing theip-restrictionheader name prevents case-sensitive auth failures, enhancing production stability. -
Related PR: #4996
Contributor: @github-actions[bot]
Change Log: This PR adds bilingual release notes files (README.mdandREADME_ZH.md) for v2.2.5, contributing 1,678 lines covering categorized statistics of 133 updates, new features, bug fixes, refactoring, and documentation improvements—automatically generated by GitHub Actions.
Feature Value: Provides users with a structured, searchable overview of version changes, significantly improving version transparency and upgrade decision efficiency; bilingual support lowers understanding barriers for domestic and international users, enhancing community friendliness and product professionalism. -
Related PR: #4916
Contributor: @muzimu217
Change Log: Adds documentation for thesecurityTokenconfiguration option in the Englishai-security-guardplugin README, supporting Alibaba Cloud STS temporary credential authentication—already implemented in Chinese docs and code but omitted in English docs.
Feature Value: Enables English-speaking users to fully understand all configurable options of theai-security-guardplugin, preventing oversight of security token configuration due to documentation gaps—improving multilingual user adoption of the plugin’s security capabilities and trust. -
Related PR: #4915
Contributor: @muzimu217
Change Log: Corrects a field-name error in the Englishai-proxyplugin README for Vertex provider security configuration, replacing the nonexistent'vertexGeminiSafetySetting'with the code-actual and used'geminiSafetySetting'—ensuring doc–source alignment.
Feature Value: Prevents users from misconfiguring security settings due to doc-induced errors, improving configuration accuracy and debugging efficiency, and enhancing documentation credibility and developer experience. -
Related PR: #4781
Contributor: @muzimu217
Change Log: Corrects erroneous descriptions of theinjection.bodyconfiguration field in the Chinesefrontend-grayplugin README, replacing the invalid'after'field name with the code-supported'first'and'last'—ensuring strict doc–source alignment.
Feature Value: Prevents gray injection functionality failure due to misconfiguration based on incorrect documentation, improving configuration accuracy and debugging efficiency, reducing online issue risks from doc ambiguity, and enhancing plugin usability and maintainability. -
Related PR: #4140
Contributor: @yyyCode
Change Log: Corrects spelling errors across multiplewasm-goplugins (ai-proxy,cors,transformer) and MCP server configuration files (mcp-business-credit-rating), including'compatiable'→'compatible','explictly'→'explicitly','protocal'→'protocol','arbitary'→'arbitrary', and tool name'bussiness-credit-rating'→'business-credit-rating'.
Feature Value: Improves documentation and configuration accuracy and professionalism, avoiding user misinterpretation of configuration meanings or confusion in debug logs due to typos; correcting the tool name ensures correct MCP protocol identification, safeguarding plugin registration and invocation reliability—indirectly enhancing system maintainability and collaboration efficiency.
-
Related PR: #5329
Contributor: @johnlanni
Change Log: Fixes the plugin preparation validation workflow’s execution environment fromubuntu-latesttoubuntu-22.04to avoidonigurumacompilation failures caused by Ubuntu 26’s bundled GCC 15, ensuring Rust artifacts rebuild stably in CI.
Feature Value: Improves CI build stability and predictability, preventing unexpected compilation failures due to system toolchain upgrades—ensuring smooth plugin release pipelines and lowering maintainer effort spent troubleshooting non-functional build issues. -
Related PR: #5326
Contributor: @johnlanni
Change Log: Pins the plugin release preparation CI job toubuntu-22.04, avoiding build failures caused byubuntu-latestupgrading to Ubuntu 26 and GCC 15’s incompatibility withonigurumaC source; only adjusts thepreparejob environment, leaving Wasm build containers unaffected.
Feature Value: Ensures stable and reliable plugin release processes, preventing compilation interruptions caused by system environment changes; guarantees users consistently receive fully tested plugin release candidates—enhancing delivery quality and trustworthiness. -
Related PR: #5322
Contributor: @johnlanni
Change Log: Adds end-to-end SRDS scaling regression protection tests: creates 200/400 Ingress resources in stages and measures latency for new Ingresses to become effective, validating gateway route-propagation performance stability—supported by CI workflows and configurable threshold validation.
Feature Value: Guarantees timely route activation during Ingress scale growth, preventing performance regressions from impacting business rollout speed; provides quantifiable SLA assurance capabilities for large-scale Ingress scenarios—enhancing production stability and operational observability. -
Related PR: #5320
Contributor: @johnlanni
Change Log: Adds a manually triggered CI workflow supporting appending additional tags to published plugin images in public registries, reusing existing registry configurations with dry-run and overwrite control—improving version-release flexibility.
Feature Value: Enables maintainers to rapidly patch or supplement plugin image tags (e.g., retroactively applying semantic-version tags) without rebuilding and repushing images—shortening incident response time and enhancing version-management reliability and operational efficiency. -
Related PR: #5286
Contributor: @johnlanni
Change Log: Adds regression tests for HTTP/2 DATA frame body handling, covering multi-frame, empty-frame, and end-of-stream body parsing logic inext-authandhmac-auth-apisixplugins—usingx/net/http2to parse real H2 frames and drive host simulators to execute plugin callbacks, improving test determinism in protocol-boundary scenarios.
Feature Value: Strengthens HTTP/2 protocol compatibility assurance, proactively capturing body-processing defects in edge cases like DATA frame fragmentation and empty frames—reducing production risks of authentication failures or data truncation from H2 streaming-body parsing anomalies and improving gateway stability/reliability in high-concurrency microservice H2 communication. -
Related PR: #5239
Contributor: @johnlanni
Change Log: Replaces shortened 7-character commit SHAs referenced in GitHub Actionstranslatesteps with full 40-character SHAs, fixing persistenttranslatestep failures caused by GitHub’s lack of support for short SHA resolution—ensuring stable execution of multilingual content translation in CI.
Feature Value: Fixes stability issues in the PR merge pipeline’s translation step, preventing CI failures due to action-reference invalidation—improving feedback reliability for developers submitting PRs and automation workflow success rates, ensuring continuous availability of documentation internationalization. -
Related PR: #5211
Contributor: @johnlanni
Change Log: Enhances the resilience of the content translation workflow against upstream API instability by pinning GitHub Action commit hashes, enablingcontinue-on-errorfor thetranslatestep, and optimizing error-handling logic—reducing CI failures caused by intermittent external service rejections (e.g., long Chinese texts).
Feature Value: Improves CI workflow stability and reliability, avoiding false negatives from transient upstream translation API rejections—reducing developer wait times for retries and accelerating PR review and merge efficiency, improving collaboration experience.
- 🚀 New Features: 2
- 🐛 Bug Fixes: 49
- ♻️ Refactoring & Optimizations: 8
- 📚 Documentation Updates: 10
- 🧪 Test Improvements: 7
Total: 76 changes
Thanks to all contributors for their hard work! 🎉
This release includes 19 updates, covering feature enhancements, bug fixes, performance optimizations, and more.
- New Features: 8
- Bug Fixes: 9
- Documentation Updates: 2
-
Related PR: #622
Contributor: @CH3CHO
Change Log: Switched the base image in the backend Dockerfile from the deprecatedopenjdk:21-jdk-slimto the officially recommendedeclipse-temurin:21-jdk, modifying only theFROMinstruction to ensure continued security updates and long-term support for the JDK runtime environment.
Feature Value: Enhances container image security and maintainability, preventing build failures or vulnerability risks caused by deprecation of theopenjdkimage repository; users benefit from a more stable and compliant Java runtime environment without any code changes. -
Related PR: #621
Contributor: @Thomas-Eliot
Change Log: Enhanced MCP Server interaction capabilities, including automaticHostheader rewriting for DNS backends, transport protocol selection, full path replacement, and correct parsing of the special character@in DSN strings under database (DB) scenarios; introduced newDirectRouteand DB configuration classes along with related constants.
Feature Value: Improves flexibility and compatibility when integrating MCP Servers, reduces user configuration complexity, prevents path ambiguity and DSN parsing errors, enabling developers to integrate diverse MCP services more stably and conveniently—thus strengthening platform extensibility and usability. -
Related PR: #608
Contributor: @Libres-coder
Change Log: Added plugin display functionality to the AI route management page, supporting expansion to view enabled plugins and displaying an "Enabled" label in the configuration panel; extendedroute.tsxandPluginListcomponent logic, integrated i18n internationalization support, and adapted plugin query logic for AI route types.
Feature Value: Users can intuitively view and verify enabled plugins directly within the AI route management interface—consistent with the experience for standard routes—enhancing transparency and maintainability of AI route configurations, reducing misconfiguration risks, and improving platform consistency and operational uniformity. -
Related PR: #604
Contributor: @CH3CHO
Change Log: Added support for regular-expression-based path rewriting via thehigress.io/rewrite-targetannotation; extended Kubernetes constant definitions and route configuration transformation logic, and added corresponding unit test cases as well as internationalized frontend and backend copy.
Feature Value: Enables users to flexibly define path rewrite rules using regular expressions, improving routing accuracy and flexibility—ideal for complex URL transformation scenarios—and significantly enhancing the gateway’s adaptability in microservice and API governance contexts. -
Related PR: #603
Contributor: @CH3CHO
Change Log: Defined the constantSTATIC_SERVICE_PORT = 80in the static service source form component and explicitly displayed this fixed port in the UI, making it clear to users that static services default to port 80—improving configuration transparency and predictability.
Feature Value: Users configuring static service sources can clearly see the preset port 80, reducing configuration errors caused by port-related misunderstandings, boosting operational efficiency and deployment success rates—especially beneficial for newcomers rapidly grasping service binding logic. -
Related PR: #602
Contributor: @CH3CHO
Change Log: Added search functionality to the upstream service selection component for AI routes, enhancing input interaction logic in theRouteFormcomponent to support dynamic filtering and rapid targeting of desired services, thereby improving configuration efficiency.
Feature Value: Users configuring AI routes can perform real-time searches for upstream services, eliminating the need to manually scroll through lengthy service lists—significantly shortening configuration time and lowering the probability of incorrect selections—enhancing platform usability and operational efficiency. -
Related PR: #566
Contributor: @OuterCyrex
Change Log: Added support for Tongyi Qwen (Qwen), a large language model service, including custom service configuration, internet search enablement, and file ID upload; introduced Qwen-specific handler classes, frontend multilingual translation entries, and a dedicated Provider configuration form component.
Feature Value: Empowers users to flexibly integrate self-hosted or privately deployed Qwen services, supporting advanced capabilities such as internet-connected search and file-context injection—enhancing the AI gateway’s compatibility with domestic large language models and its enterprise customization capability. -
Related PR: #552
Contributor: @lcfang
Change Log: Introduced theVPort(virtual port) attribute, extending registration center configuration capabilities in MCP Bridge; added thevportfield inServiceSource, and implementedvportparsing and propagation in both the Kubernetes model transformer and CRD definition—ensuring routing compatibility when service instance ports vary across environments.
Feature Value: Resolves routing failures caused by dynamically changing backend ports in registration centers (e.g., Eureka/Nacos); users can configure a unified virtual port (vport) to guarantee routing stability and cross-environment deployment compatibility—reducing operational configuration complexity.
-
Related PR: #620
Contributor: @CH3CHO
Change Log: Fixed a typographical error in thesortWasmPluginMatchRuleslogic—correcting misspelled variable names or conditional expressions—to ensure proper execution of WASM plugin match rule sorting and prevent potential null pointer exceptions or logic inconsistencies caused by naming errors.
Feature Value: Enhances the stability and reliability of WASM plugin match rule sorting, preventing runtime exceptions or erroneous rule ordering due to coding typos—ensuring that users’ custom WASM plugin policies take effect as intended and strengthening overall system robustness. -
Related PR: #619
Contributor: @CH3CHO
Change Log: Fixed duplicate version information persistence when convertingAiRoutetoConfigMap—removed theversionfield from thedataJSON payload to avoid conflicts with the version information embedded in theConfigMapmetadata—ensuring configuration consistency.
Feature Value: Improves the accuracy and reliability of Kubernetes resource configuration, preventing parsing anomalies or deployment failures caused by redundant version fields—makingAiRoute-based configuration management more stable and predictable. -
Related PR: #618
Contributor: @CH3CHO
Change Log: Refactored API authentication logic inSystemController, introducing the@AllowAnonymousannotation to explicitly mark endpoints requiring no authentication, and explicitly declaring exempt permissions in multiple controllers (e.g.,Healthz,Landing,Session) to eliminate unauthorized access security vulnerabilities stemming from default authentication policies.
Feature Value: Fixes an authentication bypass security vulnerability in system controllers, preventing unauthenticated users from accessing sensitive interfaces—significantly improving platform security and compliance—and safeguarding user data and system resources against unauthorized access or abuse. -
Related PR: #617
Contributor: @CH3CHO
Change Log: Fixed React warnings during frontend list rendering caused by missing uniquekeyprops; corrected the type of theConsumer.namefield (changed frombooleantostring); optimized image loading strategies to comply with Content Security Policy (CSP).
Feature Value: Enhances frontend application stability and user experience—eliminating console errors that interfere with development debugging, fixing type mismatches that could cause runtime exceptions, and resolving image loading failures to ensure UI elements render correctly. -
Related PR: #614
Contributor: @lc0138
Change Log: Fixed the type definition issue for thetypefield (indicating service origin) in theServiceSourceclass, adding dictionary-value validation logic to allow only legitimate registry types—preventing runtime type errors and illegal data writes.
Feature Value: Strengthens the robustness and security of service origin configuration—preventing service discovery failures or system anomalies caused by invalidtypevalues—and ensures configuration reliability and stability in multi-registry environments. -
Related PR: #613
Contributor: @lc0138
Change Log: Fixed the missing Content Security Policy (CSP) configuration on the frontend by adding the appropriate<meta>tag and related security headers indocument.tsx, mitigating client-side injection attacks such as XSS and enhancing overall application security.
Feature Value: Effectively mitigates cross-site scripting (XSS) and other security risks arising from incomplete CSP enforcement on the frontend—strengthening the security of user data and UI interactions, reducing the likelihood of malicious script execution, and improving system compliance and trustworthiness. -
Related PR: #612
Contributor: @zhwaaaaaa
Change Log: Added logic inDashboardServiceImplto ignore hop-to-hop headers (e.g.,transfer-encoding) per RFC 2616 Section 13.5.1, preventing reverse proxy forwarding of thetransfer-encoding: chunkedheader—which previously caused Grafana dashboard pages to fail loading.
Feature Value: Fixes the issue where Grafana dashboard pages failed to load due to reverse proxy passthrough of thetransfer-encoding: chunkedheader—improving console stability and user experience, and ensuring reliable operation of monitoring dashboards. -
Related PR: #609
Contributor: @CH3CHO
Change Log: Fixed a type error in theConsumerinterface’snamefield—correcting it frombooleantostring—to align the frontend data structure with actual backend response values and prevent runtime errors or type-checking failures caused by type mismatches.
Feature Value: Improves type safety and code robustness—preventing UI rendering anomalies, form submission failures, or TypeScript compilation errors resulting from an incorrectly typednamefield—and ensures accurate display and interaction with consumer information. -
Related PR: #605
Contributor: @SaladDay
Change Log: Refined the regular expression validation rule for AI route names—adding support for the dot (.) character while restricting alphabetic characters to lowercase only (a-z); updated both Chinese and English error messages to match the revised validation logic—ensuring UI prompts accurately reflect actual validation behavior.
Feature Value: Resolves issues where users were incorrectly blocked from creating AI routes containing dots in their names—enhancing form validation accuracy and UI consistency; prevents configuration failures caused by misleading error messages—strengthening system robustness and usability.
-
Related PR: #611
Contributor: @qshuai
Change Log: Fixed an inaccurate summary description in the OpenAPI documentation for the@PostMappingendpoint inLlmProvidersController, correcting the erroneous “Add a new route” text to a description aligned with the endpoint’s actual function—ensuring API documentation accuracy.
Feature Value: Improves API documentation accuracy and readability, helping developers correctly understand the endpoint’s purpose (LLM provider management) and avoid integration errors due to misleading descriptions—enhancing the usability and professionalism of the console’s API. -
Related PR: #610
Contributor: @heimanba
Change Log: Updated thefrontend-grayplugin documentation to mark therewrite,backendVersion, andenabledfields as optional; updated therules.namepath reference tograyDeployments[].name; and synchronized field descriptions and terminology in both Chinese and EnglishREADMEfiles andspec.yaml—improving documentation accuracy and configuration flexibility.
Feature Value: Grants users greater configuration flexibility and lowers the barrier to adoption; corrects field association descriptions and ensures consistent terminology—avoiding configuration misunderstandings or deployment failures caused by documentation inaccuracies—and enhances developer experience and plugin reliability.
- 🚀 New Features: 8
- 🐛 Bug Fixes: 9
- 📚 Documentation Updates: 2
Total: 19 changes
Thank you to all contributors for your hard work! 🎉
- Console: existing sessions are invalidated once after upgrade; users must sign in again. Default limits are 30 minutes idle / 8 hours absolute and can be disabled with
0. Basic auth is disabled by default. LLM provider keys are returned only at creation time; duplicate creates return 409. - mcp-e2bdev:
execute_code_sandboxwas removed. The MCP server now only creates and kills sandboxes. - REST-to-MCP: path arguments are escaped before being placed into the request URL. Path values containing
/, dot segments,?/#or pre-encoded data need migration, or the explicit unsafe compatibility switch. - Envoy: the data plane is upgraded to 1.36.12 through the proxy v2.2.6 packages.
v2.2.4
This release includes 18 updates, covering feature enhancements, bug fixes, and performance optimizations.
- New Features: 7 items
- Bug Fixes: 9 items
- Documentation Updates: 2 items
-
Related PR: #621
Contributor: @Thomas-Eliot
Change Log: Enhanced MCP Server interaction capabilities: added support for automatic Host header rewriting for DNS backends; improved transport selection and full-path configuration in direct routing scenarios; refined DSN special-character (e.g.,@) parsing logic for DB-to-MCP Server scenarios.
Feature Value: Improves flexibility and compatibility when integrating with MCP Servers, enabling users to configure diverse backend types more easily, avoiding path ambiguity and authentication-character parsing failures—thus reducing operational complexity and enhancing system stability. -
Related PR: #608
Contributor: @Libres-coder
Change Log: Added plugin display functionality to the AI Route Management page: extended AI route rows to show enabled plugins, added an "Enabled" label to the configuration page, and implemented frontend i18n support along with plugin-query logic adaptation.
Feature Value: Enables users to intuitively view and manage enabled plugins directly from the AI Route Management interface, aligning with conventional route functionality—improving transparency and operational consistency of AI route configurations and lowering learning and operational overhead. -
Related PR: #604
Contributor: @CH3CHO
Change Log: Introduced regex-based path rewrite functionality, supporting complex path matching and replacement via thehigress.io/rewrite-targetannotation; extended the rewrite configuration parsing logic inKubernetesModelConverter; added regex rewrite type identifiers to frontend and backend i18n resources.
Feature Value: Empowers users to define fine-grained path rewrite rules using regular expressions, significantly enhancing route matching precision and forwarding flexibility—ideal for multi-version API management, dynamic path mapping, and similar use cases—thereby improving gateway adaptability and operational efficiency. -
Related PR: #603
Contributor: @CH3CHO
Change Log: Added a constantSTATIC_SERVICE_PORT = 80to the static service source form component and displayed this fixed port in the UI, making it explicit to users that static services default to port 80—improving configuration transparency and consistency.
Feature Value: Users can clearly see the preconfigured port 80 when configuring static service sources, preventing service deployment failures caused by port misinterpretation—reducing adoption barriers and improving configuration accuracy and operational efficiency. -
Related PR: #602
Contributor: @CH3CHO
Change Log: Added search functionality to the upstream service selector component for AI routes, enabling frontend input-based filtering of the service list to accelerate service selection. Modified theRouteFormcomponent to include a search input field and filtering logic—achieving enhanced interactivity with minimal code changes.
Feature Value: Allows users to rapidly filter target upstream services during AI route configuration—eliminating manual scrolling through large service lists—significantly boosting configuration efficiency and user experience, especially in production environments with extensive microservice inventories. -
Related PR: #566
Contributor: @OuterCyrex
Change Log: Added support for Qwen (Tongyi Qwen) large language model (LLM) services, including custom service endpoints, internet search enablement, and file ID upload capabilities; introducedQwenLlmProviderHandler; completed configuration item and i18n adaptations on both frontend and backend.
Feature Value: Enables convenient web-based configuration of private or third-party Qwen services, expanding AI capability extensibility; internet search and file ID upload support enhance LLM invocation flexibility and practicality across real-world business scenarios. -
Related PR: #552
Contributor: @lcfang
Change Log: Addedvportattribute support for service virtual port configuration; extendedV1RegistryConfigandServiceSourcemodels; introducedVPortclass; integratedvportfield mapping into Kubernetes model conversion logic—resolving routing failures caused by inconsistent instance ports in service registries.
Feature Value: Users can now specify virtual ports for services registered via Eureka/Nacos, ensuring routing rules remain effective despite dynamic backend instance port changes—enhancing stability and compatibility of service discovery and traffic scheduling while reducing operational configuration complexity.
-
Related PR: #620
Contributor: @CH3CHO
Change Log: Fixed a typographical error in thesortWasmPluginMatchRuleslogic, correcting variable names or logical errors that could cause unexpected sorting anomalies—ensuring WASM plugin match rules are prioritized and sorted as intended.
Feature Value: Prevents rule-ordering inconsistencies due to typos, guaranteeing that WASM plugins are applied at the correct priority within the gateway—improving reliability and consistency of traffic routing and policy enforcement. -
Related PR: #619
Contributor: @CH3CHO
Change Log: Fixed duplicate version information persistence when convertingAiRoutetoConfigMap: removed theversionfield from the data JSON payload, retaining version metadata solely in theConfigMapmetadata—eliminating data redundancy and potential inconsistency.
Feature Value: Enhances configuration consistency and reliability, preventing parsing errors or deployment anomalies caused by duplicated version fields—delivering a more stable Kubernetes resource management experience forAiRouteusers. -
Related PR: #618
Contributor: @CH3CHO
Change Log: Refactored API authorization logic inSystemController, introducing an@AllowAnonymousannotation mechanism to uniformly handle unauthenticated endpoints and removing hardcoded path whitelists—improving maintainability and security of authorization policies.
Feature Value: Resolves potential security vulnerabilities in the system controller, preventing unauthorized access to sensitive APIs and enhancing overall platform security; users benefit from stronger access protection without additional configuration—reducing exposure to malicious exploitation. -
Related PR: #617
Contributor: @CH3CHO
Change Log: Fixed three critical frontend console issues: missing uniquekeyprops causing rendering warnings, Content Security Policy (CSP) blocking image loading, and incorrect type definition forConsumer.name(corrected frombooleantostring).
Feature Value: Improves application stability and user experience—eliminating console errors that disrupt development debugging, ensuring proper avatar and list rendering, and fixing data types to prevent runtime type errors—strengthening frontend code robustness. -
Related PR: #614
Contributor: @lc0138
Change Log: Fixed a type-definition error for thetypefield in theServiceSourceclass and added dictionary-value validation logic—ensuring only valid registry types are permitted and preventing runtime type mismatches.
Feature Value: Enhances robustness and security of service-source configuration, preventing service registration failures or system exceptions caused by invalidtypevalues—ensuring stability and reliability when configuring heterogeneous service sources. -
Related PR: #613
Contributor: @lc0138
Change Log: Fixed a frontend Content Security Policy (CSP) configuration defect by correctly injecting meta tags and security headers in theDocumentcomponent—preventing XSS and other client-side script injection attacks and improving overall web application security.
Feature Value: Significantly reduces the risk of cross-site scripting (XSS) and related security exploits on the frontend, strengthening user data and session security, ensuring production environment compliance, and elevating platform trustworthiness and user confidence. -
Related PR: #612
Contributor: @zhwaaaaaa
Change Log: Added hop-to-hop header (e.g.,Transfer-Encoding) ignore logic inDashboardServiceImpl, adhering to RFC 2616—preventing reverse proxy forwarding of chunked encoding headers from disrupting Grafana dashboard rendering and resolving frontend rendering failures caused by HTTP header passthrough.
Feature Value: Fixes inability to load Grafana monitoring pages, enhancing stability of console-backend integration; users gain RFC-compliant proxy behavior out-of-the-box—no manual proxy filtering rules required—improving operational experience and system observability. -
Related PR: #609
Contributor: @CH3CHO
Change Log: Corrected the type definition for thenamefield in theConsumerinterface—frombooleantostring—resolving potential runtime errors and TypeScript compilation issues caused by type mismatch.
Feature Value: EnsuresConsumer.namecorrectly represents a string-typed username, improving type safety and API consistency—preventing front-end logic misinterpretation and data rendering anomalies—and enhancing system stability and developer experience. -
Related PR: #605
Contributor: @SaladDay
Change Log: Refined the regex validation rule for AI route names to permit periods (.) and restrict characters to lowercase letters; synchronized Chinese/English error messages to ensure UI prompts accurately reflect actual validation logic—fixing erroneous rejection of valid route names (e.g.,api.v1).
Feature Value: Improves AI route configuration experience—enabling correct usage of period-containing names—while eliminating form submission failures due to inconsistent validation—enhancing system reliability and user trust.
-
Related PR: #611
Contributor: @qshuai
Change Log: Corrected the Swagger API documentation summary description for the@PostMappingendpoint inLlmProvidersController, replacing the inaccurate "Add a new route" with a precise functional description—improving API documentation accuracy and readability.
Feature Value: Aligns API documentation with actual behavior, helping developers quickly grasp endpoint purpose—reducing misuse risk—and improving development experience and integration efficiency for the console’s AI service module. -
Related PR: #610
Contributor: @heimanba
Change Log: Updatedfrontend-grayplugin documentation: markedrewrite,backendVersion, andenabledfields as optional; updatedrules.namereference path tograyDeployments[].name; synchronized field descriptions and terminology across Chinese/English READMEs andspec.yaml—enhancing configuration guidance accuracy and consistency.
Feature Value: Increases flexibility of gray-scale configuration for diverse deployment scenarios—lowering user configuration barriers; standardized documentation terminology and linkage logic—reducing configuration errors stemming from ambiguous documentation—and improving developer understanding and reliable plugin usage.
- 🚀 New Features: 7 items
- 🐛 Bug Fixes: 9 items
- 📚 Documentation Updates: 2 items
Total: 18 changes
Thank you to all contributors for your hard work! 🎉
v2.2.3
This release includes 48 updates, covering AI Gateway enhancements, multi-provider LLM protocol compatibility, gateway stability, Gateway API and Helm improvements, test coverage, and release maintenance.
- New Features: 11 items
- Bug Fixes: 28 items
- Documentation Updates: 1 item
- Testing Improvements: 5 items
- Release and Dependency Maintenance: 3 items
-
Related PR: #3849
Contributor: @GHX5T-SOL
Change Log: Key Auth now supports multiple credentials for a single service.
Feature Value: Simplifies migration and multi-client access scenarios where more than one key must be managed for the same service. -
Related PR: #3838
Contributor: @Betula-L
Change Log:jwt-authnow supports remote JWKS.
Feature Value: Makes centralized key management and key rotation easier for JWT-based authentication. -
Related PR: #3894
Contributor: @JianweiWang
Change Log:ai-security-guardadds structuredx_higressdeny responses, error-path metrics, and AI logging.
Feature Value: Improves observability and policy feedback for AI content safety enforcement. -
Related PR: #3898
Contributor: @zat366
Change Log:ai-load-balanceradds acluster_hashload balancing policy based on FNV-1a consistent hashing.
Feature Value: Provides more stable routing across model backend clusters. -
Related PR: #3895
Contributor: @JianweiWang
Change Log:ai-security-guardadds Embedding API content detection support.
Feature Value: Extends AI content safety checks beyond chat/completion-style requests. -
Related PR: #3916
Contributor: @ponypony0123
Change Log:model-routeraddskeepOriginalModelNameto preserve the full original model name.
Feature Value: Helps users keep downstream model identity semantics intact while still applying model routing rules. -
Related PR: #3979
Contributor: @EndlessSeeker
Change Log: Helm now supports skipping IngressClass creation.
Feature Value: Better supports clusters where IngressClass resources are pre-managed or controlled by platform teams. -
Related PR: #3981
Contributor: @EndlessSeeker
Change Log: GatewayClass isolation is now configurable.
Feature Value: Gives operators more control over resource boundaries in multi-GatewayClass environments. -
Related PR: #3943
Contributor: @zijiren233
Change Log: Enhanced SSL passthrough support.
Feature Value: Improves Higress support for TLS passthrough scenarios. -
Related PR: #3989
Contributor: @Rand01ph
Change Log: AI Proxy adds vLLM passthrough support for Anthropic Messages and newer OpenAI endpoints.
Feature Value: Improves compatibility for users running vLLM behind Higress as an AI gateway. -
Related PR: #4000
Contributor: @ponypony0123
Change Log: Added theai-context-limitWASM plugin for context window limit enforcement.
Feature Value: Helps reduce failures and cost risks caused by requests that exceed model context limits.
-
Related PR: #3864
Contributor: @Jing-ze
Change Log:ai-proxyre-anchorsX-HI-ORIGINAL-AUTHon the first hop to fix cascaded-gateway 401 responses.
Feature Value: Restores correct authentication behavior in cascaded gateway deployments. -
Related PR: #3839
Contributor: @zat366
Change Log:ai-proxyusesHasSuffixinstead ofContainsin Claude API name detection.
Feature Value: Avoids sub-path misidentification and improves Claude-compatible routing accuracy. -
Related PR: #3870
Contributor: @CH3CHO
Change Log: Fixed descriptions forbasePath-related fields in theai-proxyplugin.
Feature Value: Makes plugin configuration documentation clearer and less error-prone. -
Related PR: #3869
Contributor: @CH3CHO
Change Log: Fixed test cases inregistry/nacos/mcpserver/watcher_test.go.
Feature Value: Improves reliability of registry and MCP server watcher tests. -
Related PR: #3860
Contributor: @Jing-ze
Change Log:ai-proxynow routes Anthropic Messages natively to Vertex:rawPredict.
Feature Value: Improves Vertex AI compatibility for Anthropic Messages requests. -
Related PR: #3851
Contributor: @JianweiWang
Change Log:ai-statisticsskips empty streaming model values.
Feature Value: Prevents inaccurate or noisy model statistics for streaming requests. -
Related PR: #3904
Contributor: @Jing-ze
Change Log:ai-proxystripsanthropic-betaandanthropic-versionheaders in Vertex passthrough mode.
Feature Value: Avoids incompatible headers when routing Anthropic-style requests through Vertex. -
Related PR: #3914
Contributor: @Jing-ze
Change Log: Bumpedoauth2-proxyto fix a nil panic in the OIDC verifier callback.
Feature Value: Improves OIDC authentication stability. -
Related PR: #3923
Contributor: @johnlanni
Change Log: Removed request-count rebuild triggers in WASM.
Feature Value: Reduces unnecessary rebuild behavior. -
Related PR: #3922
Contributor: @johnlanni
Change Log: Rebuilds the MCP filter under high memory usage.
Feature Value: Improves runtime stability under memory pressure. -
Related PR: #3928
Contributor: @Jing-ze
Change Log: FixedSet-Cookieheader corruption during OIDC session refresh.
Feature Value: Prevents broken sessions during OIDC refresh flows. -
Related PR: #3964
Contributor: @EndlessSeeker
Change Log: Merges InferencePool route configs correctly during HTTPRoute merging.
Feature Value: Fixes route config loss in Gateway API inference routing scenarios. -
Related PR: #3971
Contributor: @EndlessSeeker
Change Log: Helm disables alpha Gateway API watches by default.
Feature Value: Reduces default install risk from alpha API watchers. -
Related PR: #3980
Contributor: @EndlessSeeker
Change Log: Sets Gateway status address type by value.
Feature Value: Fixes Gateway status address reporting. -
Related PR: #3956
Contributor: @XinhhD
Change Log:ai-proxycleans clientAuthorizationheaders for API-key providers.
Feature Value: Prevents client credentials from leaking into upstream API-key provider requests. -
Related PR: #3973
Contributor: @XinhhD
Change Log:ai-proxypreserves VertexthoughtSignaturevalues in OpenAI tool calls.
Feature Value: Improves Vertex tool-call compatibility. -
Related PR: #3985
Contributor: @XinhhD
Change Log:ai-proxyincludes tool call type in Claude stream deltas.
Feature Value: Improves Claude stream compatibility for tool calls. -
Related PR: #3924
Contributor: @geekspeng
Change Log: Helm movesimagePullPolicyfrom PodSpec to the gateway container level.
Feature Value: Aligns rendered gateway manifests with Kubernetes container-level image pull policy semantics. -
Related PR: #3905
Contributor: @philo-x
Change Log: Fixed golang-filter architecture mismatch during local gateway builds on arm64 macOS.
Feature Value: Improves local build reliability on Apple Silicon machines. -
Related PR: #3998
Contributor: @yyyCode
Change Log: Helm usesChart.Versionas the default plugin-server image tag.
Feature Value: Keeps plugin-server image tag defaults aligned with chart versions. -
Related PR: #3994
Contributor: @EndlessSeeker
Change Log: Preserves Ingress LoadBalancer hostnames.
Feature Value: Avoids losing hostname-based load balancer addresses in Ingress status. -
Related PR: #4002
Contributor: @geekspeng
Change Log: Helm appliesimagePullPolicyto the controller container and promtail sidecar.
Feature Value: Ensures rendered manifests apply image pull behavior consistently across containers. -
Related PR: #3988
Contributor: @enkilee
Change Log: Fixed several typos.
Feature Value: Improves repository documentation and code readability. -
Related PR: #3962
Contributor: @CH3CHO
Change Log:ai-cachehandles SSE first chunks that only contain a role, fixing #3953.
Feature Value: Improves AI cache compatibility with streaming responses. -
Related PR: #3990
Contributor: @XinhhD
Change Log:ai-proxyadds IDs for Vertex tool calls.
Feature Value: Improves downstream tool-call correlation and compatibility. -
Related PR: #4013
Contributor: @EndlessSeeker
Change Log: OIDC now fails closed when the verifier is unavailable.
Feature Value: Avoids unsafe authentication behavior during verifier failures. -
Related PR: #4012
Contributor: @EndlessSeeker
Change Log: Hardened cluster key rate-limit cookie parsing.
Feature Value: Improves robustness for cluster-level rate-limit cookie handling. -
Related PR: #4016
Contributor: @EndlessSeeker
Change Log: Reverted "Skip TLS certificate verification for HTTPS upstreams".
Feature Value: Restores safer TLS verification behavior for HTTPS upstreams.
- Related PR: #3890
Contributor: @FAUST-BENCHOU
Change Log: Added the missing Chinese README for extensions.
Feature Value: Improves documentation coverage for Chinese users.
-
Related PR: #3871
Contributor: @Jing-ze
Change Log: Expanded unit test coverage for thewasm-go/mcpmcp-server framework.
Feature Value: Improves confidence in MCP server framework behavior. -
Related PR: #3873
Contributor: @Jing-ze
Change Log: Added end-to-end transformer coverage and fixed silent error wrapping.
Feature Value: Improves transformer reliability and error visibility. -
Related PR: #3875
Contributor: @Jing-ze
Change Log: Covered thehmac-auth-apisixalgorithm matrix, clock skew, and authentication edge cases.
Feature Value: Strengthens authentication plugin reliability. -
Related PR: #3878
Contributor: @Jing-ze
Change Log: Coveredtraffic-tagoperators, weight CDF boundaries, and parser rejection paths.
Feature Value: Improves confidence in traffic tagging behavior under edge conditions. -
Related PR: #3879
Contributor: @Jing-ze
Change Log: Increased unit test coverage to at least 90% across 9 WASM plugins.
Feature Value: Improves plugin quality and regression protection.
-
Related PR: #3987
Contributor: @johnlanni
Change Log: Updated the Envoy submodule.
Feature Value: Keeps the gateway data-plane dependency aligned with the release baseline. -
Related PR: #4017
Contributor: @johnlanni
Change Log: Updated the Envoy submodule.
Feature Value: Pulls in the latest Envoy dependency updates for the release. -
Related PR: #4019
Contributor: @EndlessSeeker
Change Log: Released v2.2.3.
Feature Value: Updates release metadata and versioned dependencies for Higress v2.2.3.
- 🚀 New Features: 11 items
- 🐛 Bug Fixes: 28 items
- 📚 Documentation Updates: 1 item
- 🧪 Testing Improvements: 5 items
- 🔧 Release and Dependency Maintenance: 3 items
Total: 48 changes
Thank you to all contributors for your hard work! 🎉
This release includes 8 updates, covering MCP configuration fixes, LLM provider usability improvements, route and service stability, YAML cleanup, and workflow maintenance.
- New Features: 1 item
- Bug Fixes: 7 items
- Related PR: #722
Contributor: @CH3CHO
Change Log: Added support for collapsing token lists for LLM providers.
Feature Value: Improves readability and usability when configuring providers with many tokens.
-
Related PR: #724
Contributor: @JayLi52
Change Log: Fixed parsing when MCP service names contain colons.
Feature Value: Prevents MCP service configuration failures caused by service-name parsing. -
Related PR: #733
Contributor: @CH3CHO
Change Log: Fixed stale state inServiceWeightTable.
Feature Value: Keeps service weight display and edits aligned with the current state. -
Related PR: #729
Contributor: @CH3CHO
Change Log: Fixed a possible NPE inSystemServiceImpl.
Feature Value: Improves backend stability for system service operations. -
Related PR: #730
Contributor: @CH3CHO
Change Log: Trims trailing whitespace inhigress-configYAML data before submission.
Feature Value: Avoids configuration noise and accidental YAML formatting issues. -
Related PR: #734
Contributor: @CH3CHO
Change Log: Improved SSE transport path concatenation inDirectRoutingDetailStrategy.
Feature Value: Prevents incorrect direct-routing paths for SSE transport. -
Related PR: #735
Contributor: @JayLi52
Change Log: Preserves same-name routes when deleting MCP servers.
Feature Value: Avoids deleting unrelated routes that share a name with the MCP server. -
Related PR: #737
Contributor: @CH3CHO
Change Log: Fixed deploy-to-OSS workflow failures caused by Node.js 20 deprecation.
Feature Value: Restores release and deployment automation reliability.
- 🚀 New Features: 1 item
- 🐛 Bug Fixes: 7 items
Total: 8 changes
Thanks to all contributors for their hard work! 🎉
- @GHX5T-SOL made their first contribution in #3849
- @FAUST-BENCHOU made their first contribution in #3890
- @ponypony0123 made their first contribution in #3916
- @XinhhD made their first contribution in #3956
- @geekspeng made their first contribution in #3924
- @philo-x made their first contribution in #3905
- @yyyCode made their first contribution in #3998
- @zijiren233 made their first contribution in #3943
- @enkilee made their first contribution in #3988
- @Rand01ph made their first contribution in #3989
Full Changelog:
- Higress: v2.2.2...v2.2.3
- Higress Console: v2.2.2...v2.2.3
v2.2.2
This release includes 37 updates, covering feature enhancements, bug fixes, performance optimizations, and more.
- New Features: 13 items
- Bug Fixes: 18 items
- Documentation Updates: 5 items
- Testing Improvements: 1 item
-
Related PR: #3827
Contributor: @rinfx
Change Log: Added themodelToHeaderconfiguration option, with default valuex-higress-llm-model-final; synchronously updates this header after parsing thenewModelfrom the request body to ensure downstream logic such as rate limiting and metering aligns with the model mapping result; callsDisableReroutewhen reading the body to prevent routing conflicts.
Feature Value: Enhances model routing consistency and reliability, enabling fallback, model-based rate limiting, and metering features to accurately reflect the actual matched model; users gain more stable and precise model dispatching capabilities without modifying business logic, reducing the risk of policy deviation caused by header synchronization issues. -
Related PR: #3823
Contributor: @johnlanni
Change Log: Introduced an nginx-rewrite-compatible WASM plugin that implements compatible parsing of Nginxrewrite+setsemantics, securely executes rewriting logic within a WASM sandbox to avoid the CVE-2026-42945 heap overflow vulnerability, and supports path matching, variable capture, and substitution.
Feature Value: Enables Higress users to smoothly migrate existing Nginx rewrite rules while ensuring compatibility and eliminating critical security risks, lowering the refactoring cost and operational risk for legacy services transitioning from Nginx to Higress. -
Related PR: #3820
Contributor: @wydream
Change Log: Refactored the/v1/messagesrequest handling for the Bedrock Provider: replaced the original two-layer protocol conversion chain (OpenAI → Converse) with direct connectivity to the native Bedrock Mantle Anthropic Messages API; added support for the Mantle endpoint, restructured request routing logic, and extended capability declarations.
Feature Value: Delivers lower latency, higher compatibility, and native Anthropic feature support (e.g., tool use, beta headers) for/v1/messagescalls; avoids semantic loss and performance overhead associated with protocol translation, significantly improving the Bedrock integration experience and stability. -
Related PR: #3766
Contributor: @rinfx
Change Log: Added support for cached token usage (CacheReadInputTokens) in the streaming response transformation logic from OpenAI to Claude; modified core transformer code and added corresponding unit test cases to ensure the Claude compatibility layer accurately conveys cached token count information.
Feature Value: Enables AI agents to correctly report input token savings resulting from cache hits when invoking Claude models, helping users precisely monitor and optimize API costs; simultaneously improves transparency and billing consistency across multi-model metering, enhancing enterprise-grade usage analytics capabilities. -
Related PR: #3748
Contributor: @zat366
Change Log: Added theenable_path_suffixesconfiguration option to theQuotaConfigstruct to support custom path suffix matching; updated configuration parsing logic to handle default values; modified thegetOperationModefunction to accommodate the new path suffix logic; enhanced test coverage for the new configuration and its impact on operation modes.
Feature Value: Allows users to flexibly define API path suffix matching rules per business requirements, increasing quota control precision and adaptability; administrators can manage quota policies for different AI service paths with finer granularity, enhancing plugin applicability and maintainability across diverse scenarios. -
Related PR: #3742
Contributor: @wydream
Change Log: Added KlingAI provider support, featuring official AK/SK JWT authentication and third-party gateway static Bearer token authentication modes, covering both OpenAI-compatible and native Kling protocols, and enabling full interface capabilities including text-to-video and image-to-video generation.
Feature Value: Users can directly invoke KlingAI video generation capabilities via the AI proxy service without implementing JWT signing or adapting to various gateways—significantly lowering the integration barrier and expanding platform support for AIGC video-generation models. -
Related PR: #3739
Contributor: @johnlanni
Change Log: Added thereplaceconfiguration option to theai-prompt-decoratorplugin, supporting ordered, role-conditioned text replacement in thecontentfield of the final assembledmessages, using either literal strings or RE2 regular expressions, enhancing dynamic request content rewriting capabilities.
Feature Value: Enables users to flexibly implement text processing needs—including sensitive word filtering, brand term normalization, and placeholder desensitization—without modifying business logic, improving the AI gateway’s adaptability in compliance, security, and multi-tenant scenarios. -
Related PR: #3738
Contributor: @JianweiWang
Change Log: Added configurable fallback JSON paths for response content extraction (responseContentFallbackJsonPathsandresponseStreamContentFallbackJsonPaths) to theai-security-guardplugin, supporting non-OpenAI formats such as Anthropic Claude; when the primary path yields an empty result, fallback paths are attempted sequentially, automatically skipping any fallback path identical to the primary one.
Feature Value: Enhances plugin compatibility and robustness, allowing users to perform content safety checks against diverse LLMs (e.g., Claude) without code changes—reducing multi-model adaptation effort and ensuring stable, accurate response content extraction. -
Related PR: #3734
Contributor: @CH3CHO
Change Log: Added existence check for thepatchcommand in thebuild-envoy.shscript; triggers early failure if missing; also optimized error handling duringbuild-envoy.patchapplication to prevent silent Bazel dependency errors caused by unexecuted patches.
Feature Value: Significantly improves observability and robustness of the Envoy build process; users receive immediate, clear error messages if thepatchcommand is absent, drastically lowering debugging effort and environment configuration troubleshooting costs. -
Related PR: #3724
Contributor: @wydream
Change Log: Added Qwen rerank and conversations API path support to the AI Proxy plugin, extending path mapping rules, API name constants, and Qwen-specific routing logic; supplemented comprehensive regression test cases covering path recognition and provider routing functionality.
Feature Value: Users can invoke Qwen’s reranking and conversational capabilities via standard-compatibility interfaces, improving unified multi-model service access experiences; broadens AI Proxy support for domestic large language models (Qwen), lowering business integration barriers and boosting routing accuracy. -
Related PR: #3700
Contributor: @wydream
Change Log: Added thecooldownDurationconfiguration option to theai-proxyfailover mechanism, enabling automatically restored API keys after a specified millisecond cooldown period—eliminating dependency on real requests for health checking and reducing token consumption and configuration complexity.
Feature Value: Empowers users to manage API key availability more flexibly, mitigating long-term unavailability risks due to rate limiting, saving invocation costs, and simplifying failover configuration to enhance system stability and operational efficiency. -
Related PR: #3694
Contributor: @CH3CHO
Change Log: Added configurable forwarding capability for attributes in external authorization requests, supporting transparent transmission of key contextual fields such asroute_nameandcluster_name; implemented via extension of theAuthorizationRequeststruct with anAllowedPropertiesfield, alongside updates to configuration parsing logic and SDK dependencies.
Feature Value: Enables users to access richer Envoy gateway context information in external authorization services, improving the precision and flexibility of authorization policies and facilitating fine-grained access control based on dimensions like route and cluster—lowering customization development costs. -
Related PR: #3690
Contributor: @JianweiWang
Change Log: Added support for sensitive data masking, enabling desensitization and replacement of sensitive fields in API responses via theriskActionconfiguration (block/mask); introduced new dimension types—customLabel,maliciousFile, andwaterMark—and added dimension-level action configuration to improve risk mitigation flexibility.
Feature Value: Allows dynamic desensitization of sensitive information without service interruption, strengthening AI application compliance capabilities; multi-dimensional, fine-grained risk control strategies enable more precise content security governance—reducing false positives and satisfying regulatory requirements across diverse business scenarios.
-
Related PR: #3829
Contributor: @CH3CHO
Change Log: Fixed a typo in the JSON/YAML tag for theapiTokensfield in theProviderConfigstruct within theai-proxyplugin, correcting it to the proper format to ensure correct configuration parsing and serialization.
Feature Value: Prevents configuration parsing failures or incorrect loading of API tokens caused by erroneous field tags, enhancing the stability and reliability of the AI proxy service and enabling users to seamlessly configure and utilize authentication credentials for various AI providers. -
Related PR: #3801
Contributor: @CH3CHO
Change Log: Fixed logging issues duringEnvoyFilterconstruction regarding unsupported upstream protocols, by adding missing formatting parameters to ensure warning logs correctly display the protocol type and context.
Feature Value: Improves debugging and operational observability, enabling users to accurately identify unsupported protocols and their locations upon misconfiguration—reducing troubleshooting time and enhancing Ingress gateway configuration robustness and maintainability. -
Related PR: #3799
Contributor: @Betula-L
Change Log: Fixed an issue where empty input objects (input:{}) in Claude tool calls were unexpectedly omitted during internal bridge conversion to Bedrock Converse format; addressed via adjustments to struct field JSON tags and expanded test coverage to ensure empty maps are preserved correctly.
Feature Value: Ensures Claude messages using parameterless tools are accurately relayed to the underlying Bedrock service, preventing tool call failures or abnormal behavior caused by missing inputs—improving AI proxy compatibility and reliability in multi-model adaptation scenarios. -
Related PR: #3788
Contributor: @Betula-L
Change Log: Fixed structural data loss in Bedrock Claude inference blocks duringai-proxyprotocol bridging by refactoring theconvertEventFromBedrockToOpenAIlogic and introducingredactedBlockIndexesstate management—ensuringreasoningContentremains within native Anthropic message blocks rather than being merged into plain text.
Feature Value: Users invoking Bedrock Claude models will correctly receive structured reasoning blocks (e.g.,<think>...</think>), avoiding accidental exposure of reasoning processes to end users—enhancing response semantic integrity and compatibility, and guaranteeing Anthropic Messages API specification–compliant interactions. -
Related PR: #3786
Contributor: @Betula-L
Change Log: Fixed incorrect mapping betweencontentBlockIndexin Bedrock Claude streaming responses andtool_calls[].indexin OpenAI format, properly handling index misalignment for parallel tool calls and refiningtool_choiceparameter conversion logic to preserve semantic consistency and ordering fidelity in streaming tool calls withinai-proxy.
Feature Value: Users performing parallel multi-tool calls with Bedrock Claude models will receive accurate, predictable streamingtool_callsindices and correctly triggeredtool_choicebehaviors—preventing tool execution disorder or loss and significantly enhancing production-environment compatibility and reliability. -
Related PR: #3779
Contributor: @CH3CHO
Change Log: Fixed an issue where certain controller logs continued outputting as plaintext despite enabling the--log_as_jsonflag; resolved by uniformly replacing log package imports withistio.io/istio/pkg/log, ensuring all components use the same JSON logging implementation.
Feature Value: Improves log format consistency and observability, facilitating centralized collection, parsing, and analysis of Higress controller logs in environments like Kubernetes—reducing operational troubleshooting cost and strengthening production log standardization. -
Related PR: #3777
Contributor: @wydream
Change Log: Fixed API key injection issues for Vertex AI Express Mode’s raw REST endpoints in theai-proxyplugin, expanding regex patterns to match Express Mode URLs lacking/projects/{project}/locations/{location}path segments and adding test cases validating request header processing logic.
Feature Value: Enables users to correctly invoke simplified Vertex AI Express Mode REST interfaces (e.g.,streamGenerateContent) without manually constructing complex paths, enhancing proxy compatibility and usability—and avoiding 401 authentication failures caused by missing key injection. -
Related PR: #3770
Contributor: @CH3CHO
Change Log: Fixed inability to skip TLS certificate verification for HTTPS upstream connections by adding configuration support for certificate verification bypass inupstreamtls.go, and supplementing protobuf andgoogle.golang.orgdependencies in test files to support unit testing of the new capability.
Feature Value: Enables Higress to support HTTPS upstream services using self-signed certificates, resolving connection failures arising from untrusted certificates in enterprise internal or testing environments—improving deployment flexibility and compatibility. -
Related PR: #3765
Contributor: @wydream
Change Log: Fixedai-proxysupport for Azure OpenAI v1 service URLs by adding recognition and routing logic for/openai/v1and subpaths, accommodating the new URL format withoutapi-versionparameters, while retainingapi-versionvalidation logic for legacy deployment URLs.
Feature Value: Enables users to seamlessly integrate with Azure OpenAI’s latest v1 REST API standard without manually appendingapi-version, enhancing configuration flexibility and service compatibility—reducing request failure rates due to URL format changes and strengthening proxy stability and usability. -
Related PR: #3757
Contributor: @srpatcha
Change Log: Added nil checks, safe type assertions, and panic protection mechanisms to fix multiple potential nil pointer dereferences and type assertion failures; additionally optimized regex compilation logic in WASM plugins to prevent runtime panics.
Feature Value: Significantly improves gateway stability and robustness, preventing service crashes due to anomalous inputs or misconfigurations; users benefit from a more reliable API gateway experience, lowering online failure rates and operational overhead. -
Related PR: #3756
Contributor: @wydream
Change Log: Fixed loss ofthinking/redacted_thinkingcontent blocks during/v1/messagesto OpenAIchat/completionsrequest transformation for Claude, enhanced transmission of tool-call reasoning context, and introducedpreserve_thinkingandpromote_thinking_on_emptyconfiguration options for provider-level compatibility control.
Feature Value: Ensures AI proxies backed by Claude correctly convey complete chain-of-thought information to models supportingreasoning_content(e.g., Qwen), while avoiding compatibility breakage for strict-standard providers like OpenAI/Azure—improving functional consistency and reliability in multi-model routing scenarios. -
Related PR: #3733
Contributor: @wydream
Change Log: Fixed compatibility issues with non-standard upstream responses in Claude streaming transformations: correctly handles empty-stringfinish_reason, prevents duplicate triggering ofmessage_stopdue tousage, and avoids processing redundant chunks aftermessage_stopto prevent event reordering.
Feature Value: Enhances AI proxy stability and reliability in multi-vendor compatibility scenarios, preventing streaming response interruptions or disorder—ensuring users receive complete, chronologically ordered Claude-style SSE streams and improving the overall LLM invocation experience. -
Related PR: #3731
Contributor: @JianweiWang
Change Log: Removed the mandatory fallback interception logic forSuggestion=blockin the AI Security Guard, replacing it with unified risk-dimension–based threshold evaluation; modified core assessment logic inconfig.goand updated multiple test cases to accurately cover threshold-drivenRiskBlockdecision paths.
Feature Value: Improves risk interception accuracy and configurability, preventing unintended blocking caused by misconfiguredSuggestion=block; users now exert precise control over interception behavior via thresholds—enhancing policy transparency, debuggability, and reducing false positive rates. -
Related PR: #3722
Contributor: @wydream
Change Log: Migrated Qwen-compatible response endpoint path from the deprecated legacy URL/api/v2/apps/protocols/compatible-mode/v1/responsesto the new official path/compatible-mode/v1/responses, updating path constants and assertions inprovider/qwen.goand test files to ensure continued valid interface invocation by the AI proxy.
Feature Value: Prevents service disruption caused by Qwen (DashScope) deprecation of the legacy API path, safeguarding stability and continuity of Qwen model invocation viaai-proxy—enabling seamless transition to the new interface without client-side code changes. -
Related PR: #3695
Contributor: @wydream
Change Log: Fixed missing API Key authentication in Vertex Raw Express Mode by appending the API Key to the URL query string inOnRequestBodyand cleaning theAuthorizationheader; also resolved global authentication header leakage and URL construction logic defects in Express Mode.
Feature Value: Enables Vertex Raw Express Mode to authenticate correctly against Google Vertex AI services via API Key—preventing 401 errors; improves proxy stability and compatibility, ensuring users can reliably invoke large language model APIs in this mode. -
Related PR: #3682
Contributor: @CH3CHO
Change Log: Fixed absence ofTARGET_ARCHvalidity checking in thegolang-filterduringbuild-gateway-local, by introducing aVALID_ARCHSwhitelist and error-checking logic inMakefile.core.mk—supporting onlyamd64andarm64, preventing build failures or erroneous binaries from invalid architecture parameters.
Feature Value: Enhances robustness and maintainability of multi-architecture builds, preventing silent build errors or runtime anomalies due to invalidTARGET_ARCHvalues (e.g.,x86,ppc64le); guarantees correct compilation and deployment of the Higress gateway across diverse CPU architectures. -
Related PR: #3576
Contributor: @Jing-ze
Change Log: Fixed staleROUTE_NAMEattribute returning outdated route names post-reroute in WASM contexts, by correcting theStreamInfoImpl::getRouteName()invocation logic in Envoy 1.36 to ensure fresh route names are retrieved afterclearRouteCache.
Feature Value: Ensures WASM plugins correctly match rules following rerouting, preventingmatchRulefailures due to stale route names—improving routing policy execution accuracy and stability, which is critical for user features relying on dynamic route matching. -
Related PR: #3425
Contributor: @CH3CHO
Change Log: Added a default value (higress-registry.cn-hangzhou.cr.aliyuncs.com/higress) to theHUBargument inDockerfile.higress, eliminating build-time warnings whenHUBis not explicitly provided, while preserving backward compatibility: explicitly passed values retain precedence.
Feature Value: Removes redundant warnings during Docker builds, improving CI/CD pipeline readability and stability; users can complete local builds without specifying theHUBparameter—lowering entry barriers and maintenance costs.
-
Related PR: #3830
Contributor: @EndlessSeeker
Change Log: Added OpenSSF Best Practices badges to README files in English, Chinese, and Japanese versions, embedded via Markdown image links pointing to the project’s assessment page on the OpenSSF Best Practices platform—enhancing project compliance and credibility visibility.
Feature Value: Strengthens project transparency and trustworthiness, enabling users to quickly assess Higress’ adherence to open-source best practices in security and maintainability—boosting community and enterprise user confidence and adoption willingness. -
Related PR: #3764
Contributor: @EndlessSeeker
Change Log: UpdatedSECURITY.md,CONTRIBUTINGseries documentation, and addedGOVERNANCE.md, formalizing vulnerability reporting procedures, defining security response SLAs and teams, and clarifying CNCF governance models—meeting CNCF Sandbox and OpenSSF Best Practices certification requirements.
Feature Value: Elevates project security compliance and transparency, providing users with standardized channels and response commitments for security issues—strengthening enterprise user trust; simultaneously enhances multilingual contribution guidelines, lowering global developer participation barriers and promoting healthy, sustainable community growth. -
Related PR: #3754
Contributor: @johnlanni
Change Log: Added a top-levelMAINTAINERS.mdfile listing current Higress project maintainers, including maintainer responsibility descriptions and CNCF Sandbox compliance statements—providing essential governance documentation required for CNCF sandbox onboarding.
Feature Value: Enhances project transparency and community governance standardization, assisting external contributors in identifying core maintenance teams, accelerating CNCF sandbox certification, and laying foundations for future maintainer transitions and permission management—bolstering user confidence in the project’s long-term stability. -
Related PR: #3730
Contributor: @CH3CHO
Change Log: Updated English and Chinese README files to align with the latest configuration parsing logic, correcting contradictory defaults, inaccurate path descriptions, and unclear string concatenation formats, and removing outdated build instructions (e.g.,tinygorequirements).
Feature Value: Improves documentation accuracy and consistency, preventing plugin activation failures stemming from obsolete or erroneous configuration examples; synchronized bilingual documentation lowers comprehension barriers for multilingual users—enhancing AI caching plugin usability and reliability. -
Related PR: #3696
Contributor: @github-actions[bot]
Change Log: Added bilingual release notes files for version 2.2.1 (README.mdandREADME_ZH.md), automatically summarizing 65 updates spanning new features, bug fixes, refactorings, optimizations, and documentation improvements—with categorical statistics.
Feature Value: Provides users with a well-structured, multilingual overview of version changes, accelerating understanding of upgrade benefits and impact scope—enhancing transparency and maintainability and lowering upgrade decision-making costs.
- Related PR: #3790
Contributor: @Jing-ze
Change Log: Expanded integration test coverage for the AI Proxy WASM plugin, including boundary cases for configuration parsing, streaming response body handling, failover verification, and utility function testing; addedexport_test.goto expose internal functions for testing purposes—significantly improving WASM environment test completeness.
Feature Value: Strengthens stability and compatibility assurance for the AI Proxy plugin across diverse WASM runtimes and AI service providers, lowering risks of service interruption arising from configuration anomalies or network failures—enhancing reliability and maintainability for production deployments.
- 🚀 New Features: 13 items
- 🐛 Bug Fixes: 18 items
- 📚 Documentation Updates: 5 items
- 🧪 Testing Improvements: 1 item
Total: 37 changes
Thank you to all contributors for your hard work! 🎉
This release includes 18 updates, covering feature enhancements, bug fixes, performance optimizations, and more.
- New Features: 7 items
- Bug Fixes: 9 items
- Documentation Updates: 2 items
-
Related PR: #621
Contributor: @Thomas-Eliot
Change Log: Enhanced MCP Server interaction capabilities: added support for automaticHostheader rewriting for DNS backends; improved transport protocol selection and full-path configuration in direct routing scenarios; enhanced parsing of special characters (e.g.,@) in DSNs for DB-to-MCP Server scenarios.
Feature Value: Improves flexibility and compatibility of MCP Server integration, enabling users to connect more easily to backend services deployed in diverse environments, reducing configuration complexity, and preventing connectivity issues caused by path prefix misinterpretation or DSN parsing failures. -
Related PR: #608
Contributor: @Libres-coder
Change Log: Added plugin visibility functionality to the AI Route Management page: supports expanding rows to view enabled plugins and displays an'Enabled'badge on the configuration page; extendedPluginListcomponent logic to supportAI_ROUTE-type queries, and enhanced cleanup of i18n language-change listeners inroute.tsx.
Feature Value: Users can now intuitively view plugins enabled for AI routes, aligning the experience with that of conventional route management—improving maintainability and observability of AI route configurations; unified UI interactions reduce learning overhead and enhance completeness of platform support for AI use cases. -
Related PR: #604
Contributor: @CH3CHO
Change Log: Introduced support for regex-based path rewriting via thehigress.io/rewrite-targetannotation, extended Kubernetes annotation constants, route transformation logic, and front-end/back-end internationalized copy, thereby increasing routing match flexibility.
Feature Value: Enables precise control over path rewriting behavior using regular expressions, meeting complex routing requirements such as dynamic path parameter extraction and mapping—significantly enhancing the expressiveness of gateway configuration and its adaptability to business needs. -
Related PR: #603
Contributor: @CH3CHO
Change Log: Added the constantSTATIC_SERVICE_PORT = 80to the static service source form component and explicitly displays this fixed port in the UI, making users clearly aware that static services default to port 80—improving configuration transparency and predictability.
Feature Value: Users configuring static service sources can immediately see that the default port is 80, avoiding configuration errors or debugging difficulties caused by port misconceptions—lowering entry barriers and improving deployment efficiency and consistency of user experience. -
Related PR: #602
Contributor: @CH3CHO
Change Log: Added a search function to the upstream service selection component in AI route configuration; extended theSelectcomponent logic inindex.tsxto enable real-time searching and filtering across large numbers of upstream services—improving configuration efficiency and accuracy.
Feature Value: Users can quickly locate target upstream services when configuring AI routes instead of manually scrolling through long lists—significantly reducing configuration error rates, especially in complex AI gateway scenarios with dozens or more services—enhancing both operational and development efficiency. -
Related PR: #566
Contributor: @OuterCyrex
Change Log: Added support for Tongyi Qwen large language model (LLM) services, including custom service endpoint configuration, Internet search toggle, and file ID upload; implementedQwenLlmProviderHandleron the backend and added multilingual support and provider form adaptation on the frontend.
Feature Value: Enables flexible integration with self-hosted or cloud-based Qwen services, supporting search augmentation and file context injection—improving compatibility and extensibility of the AI gateway for domestic LLMs and lowering enterprise private-deployment barriers. -
Related PR: #552
Contributor: @lcfang
Change Log: Introduced theVPortvirtual port attribute, extending MCP Bridge registry configuration capabilities; added thevportfield and corresponding CRD model toServiceSource, enabling uniform specification of default backend ports for service instances—resolving routing failures caused by inconsistent actual port numbers across instances registered in Eureka/Nacos registries.
Feature Value: Allows users to explicitly declare a virtual port during service discovery configuration, ensuring routing rules remain resilient to backend port changes—preventing traffic disruptions due to dynamic instance port changes, thus improving microservice governance stability and operational predictability.
-
Related PR: #620
Contributor: @CH3CHO
Change Log: Fixed a spelling error in thesortWasmPluginMatchRuleslogic—corrected variable names or logical typos causing potential behavioral anomalies during matching rule sorting—ensuring WASM plugin matching rules are sorted by priority as intended.
Feature Value: Prevents incorrect rule ordering caused by typographical errors, guaranteeing that WASM plugins take effect in Kubernetes strictly according to user-specified priorities—enhancing reliability and consistency of plugin routing and policy enforcement. -
Related PR: #619
Contributor: @CH3CHO
Change Log: Fixed duplicate version information storage when convertingAiRoutetoConfigMap: removed theversionfield from thedataJSON payload, retaining it exclusively in theConfigMapmetadata—to eliminate data redundancy and potential inconsistency.
Feature Value: Improves accuracy and consistency of configuration management, preventing parsing errors or deployment anomalies caused by duplicated version fields—enhancing system stability and maintainability, delivering direct benefits to users managing route configurations via KubernetesConfigMap. -
Related PR: #618
Contributor: @CH3CHO
Change Log: Refactored API authentication logic inSystemController, introducing anAllowAnonymousannotation mechanism to uniformly handle unauthenticated endpoints—replacing hard-coded whitelisting checks—thereby improving maintainability and security of authentication logic.
Feature Value: Resolves potential security vulnerabilities in the system controller that could allow unauthorized access to sensitive API endpoints—enhancing overall platform security, safeguarding user data and system resources from illicit calls, and strengthening compliance and trustworthiness in enterprise production environments. -
Related PR: #617
Contributor: @CH3CHO
Change Log: Fixed missing uniquekeyprops in front-end list rendering (triggering React warnings), resolved Content Security Policy (CSP) blocking of external image loading, and corrected a type definition error for theConsumer.namefield (erroneously typed asbooleaninstead ofstring)—improving component robustness and type safety.
Feature Value: Eliminates console warnings and image-loading failures, improving developer experience and debugging efficiency; corrects interface type definitions to prevent runtime type errors—enhancing application stability and developer collaboration reliability, delivering smoother, warning-free UI interactions for end users. -
Related PR: #614
Contributor: @lc0138
Change Log: Fixed a type definition error for thetypefield (indicating service source) in theServiceSourceclass and added validation logic for dictionary values—ensuring incoming registry types belong exclusively to a predefined valid set—to prevent illegal values from triggering runtime exceptions.
Feature Value: Enhances robustness and security of service source configuration, preventing service registration failure or system exceptions due to invalidtypefield values—ensuring stable, predictable behavior when configuring various service registries. -
Related PR: #613
Contributor: @lc0138
Change Log: Fixed missing Content Security Policy (CSP) configuration on the front end—added a meta tag indocument.tsxto declare the security policy—mitigating risks such as XSS attacks and strengthening security controls over page resource loading and script execution.
Feature Value: Enhances front-end application security posture, effectively mitigating common web threats like cross-site scripting (XSS)—safeguarding user data and interactions, fulfilling enterprise-level security compliance requirements, and reinforcing end-user trust. -
Related PR: #612
Contributor: @zhwaaaaaa
Change Log: Added logic inDashboardServiceImplto ignore hop-to-hop HTTP headers (e.g.,Transfer-Encoding: chunked) per RFC 2616 Section 13.5.1—preventing reverse proxy forwarding anomalies caused by illegal pass-through of hop-to-hop headers, which previously broke Grafana dashboard rendering.
Feature Value: Resolves Grafana console page loading failures caused by reverse proxies forwarding hop-to-hop headers likeTransfer-Encoding: chunked—improving console stability and user experience and ensuring reliable availability of monitoring integration features. -
Related PR: #609
Contributor: @CH3CHO
Change Log: Fixed a type error in theConsumerinterface where thenamefield was incorrectly declared asboolean; corrected it tostringto ensure alignment between front-end data structures and actual back-end response payloads—avoiding runtime errors or TypeScript compilation warnings caused by type mismatches.
Feature Value: Enhances type safety and front-end/back-end data consistency—preventing UI rendering anomalies or flawed logic decisions due to field-type mismatches—boosting application stability, reducing developer debugging effort, and improving overall development experience. -
Related PR: #605
Contributor: @SaladDay
Change Log: Corrected the front-end form validation regex for AI route names to support periods (.) while restricting characters to lowercase letters only; synchronized English and Chinese error message texts to ensure UI prompts precisely reflect actual validation logic.
Feature Value: Resolves issues where users’ AI routes were erroneously rejected or inaccurately warned about names containing periods—improving form usability and user experience; strict alignment between validation rules and UI guidance reduces user cognitive load and operation failure rates.
-
Related PR: #611
Contributor: @qshuai
Change Log: Corrected API endpoint annotations inLlmProvidersControllerfor newly added LLM provider methods—replaced inaccurate summary'Add a new route'with a title accurately reflecting functionality—ensuring generated API documentation (e.g., Swagger) correctly describes actual behavior.
Feature Value: Improves API documentation accuracy and developer experience—preventing misunderstandings by front-end or client developers caused by misleading summaries; enhances professionalism and maintainability of console API docs for users, reducing integration and debugging costs. -
Related PR: #610
Contributor: @heimanba
Change Log: Updatedfrontend-grayplugin documentation to markrewrite,backendVersion, andenabledfields as optional; updated therules.nameassociation path tograyDeployments[].name; and synchronized field descriptions and terminology in both English and ChineseREADMEs andspec.yaml—ensuring configuration guidance accurately reflects the latest design for enhanced flexibility.
Feature Value: Improves compatibility and usability of gray-scale configurations—lowering user configuration barriers; precise field descriptions and consistent terminology reduce misunderstandings and configuration errors—helping developers adopt front-end gray-scale features more efficiently and accurately.
- 🚀 New Features: 7 items
- 🐛 Bug Fixes: 9 items
- 📚 Documentation Updates: 2 items
Total: 18 changes
Thanks to all contributors for their hard work! 🎉
- @Betula-L made their first contribution in https://github.com/alibaba/higress/pull/3786
- @srpatcha made their first contribution in https://github.com/alibaba/higress/pull/3757
- @KevinKingKong made their first contribution in https://github.com/higress-group/higress-console/pull/671
- @zengyr49 made their first contribution in https://github.com/higress-group/higress-console/pull/688
- @huchunnuan made their first contribution in https://github.com/higress-group/higress-console/pull/693
- @zat366 made their first contribution in https://github.com/higress-group/higress-console/pull/697
Full Changelog: https://github.com/alibaba/higress/compare/v2.2.1...v2.2.2
v2.2.2
This release includes 37 updates, covering feature enhancements, bug fixes, performance optimizations, and more.
- New Features: 13 items
- Bug Fixes: 18 items
- Documentation Updates: 5 items
- Testing Improvements: 1 item
-
Related PR: #3827
Contributor: @rinfx
Change Log: Added themodelToHeaderconfiguration option, with default valuex-higress-llm-model-final; synchronously updates this header after parsing thenewModelfrom the request body to ensure downstream logic such as rate limiting and metering aligns with the model mapping result; callsDisableReroutewhen reading the body to prevent routing conflicts.
Feature Value: Enhances model routing consistency and reliability, enabling fallback, model-based rate limiting, and metering features to accurately reflect the actual matched model; users gain more stable and precise model dispatching capabilities without modifying business logic, reducing the risk of policy deviation caused by header synchronization issues. -
Related PR: #3823
Contributor: @johnlanni
Change Log: Introduced an nginx-rewrite-compatible WASM plugin that implements compatible parsing of Nginxrewrite+setsemantics, securely executes rewriting logic within a WASM sandbox to avoid the CVE-2026-42945 heap overflow vulnerability, and supports path matching, variable capture, and substitution.
Feature Value: Enables Higress users to smoothly migrate existing Nginx rewrite rules while ensuring compatibility and eliminating critical security risks, lowering the refactoring cost and operational risk for legacy services transitioning from Nginx to Higress. -
Related PR: #3820
Contributor: @wydream
Change Log: Refactored the/v1/messagesrequest handling for the Bedrock Provider: replaced the original two-layer protocol conversion chain (OpenAI → Converse) with direct connectivity to the native Bedrock Mantle Anthropic Messages API; added support for the Mantle endpoint, restructured request routing logic, and extended capability declarations.
Feature Value: Delivers lower latency, higher compatibility, and native Anthropic feature support (e.g., tool use, beta headers) for/v1/messagescalls; avoids semantic loss and performance overhead associated with protocol translation, significantly improving the Bedrock integration experience and stability. -
Related PR: #3766
Contributor: @rinfx
Change Log: Added support for cached token usage (CacheReadInputTokens) in the streaming response transformation logic from OpenAI to Claude; modified core transformer code and added corresponding unit test cases to ensure the Claude compatibility layer accurately conveys cached token count information.
Feature Value: Enables AI agents to correctly report input token savings resulting from cache hits when invoking Claude models, helping users precisely monitor and optimize API costs; simultaneously improves transparency and billing consistency across multi-model metering, enhancing enterprise-grade usage analytics capabilities. -
Related PR: #3748
Contributor: @zat366
Change Log: Added theenable_path_suffixesconfiguration option to theQuotaConfigstruct to support custom path suffix matching; updated configuration parsing logic to handle default values; modified thegetOperationModefunction to accommodate the new path suffix logic; enhanced test coverage for the new configuration and its impact on operation modes.
Feature Value: Allows users to flexibly define API path suffix matching rules per business requirements, increasing quota control precision and adaptability; administrators can manage quota policies for different AI service paths with finer granularity, enhancing plugin applicability and maintainability across diverse scenarios. -
Related PR: #3742
Contributor: @wydream
Change Log: Added KlingAI provider support, featuring official AK/SK JWT authentication and third-party gateway static Bearer token authentication modes, covering both OpenAI-compatible and native Kling protocols, and enabling full interface capabilities including text-to-video and image-to-video generation.
Feature Value: Users can directly invoke KlingAI video generation capabilities via the AI proxy service without implementing JWT signing or adapting to various gateways—significantly lowering the integration barrier and expanding platform support for AIGC video-generation models. -
Related PR: #3739
Contributor: @johnlanni
Change Log: Added thereplaceconfiguration option to theai-prompt-decoratorplugin, supporting ordered, role-conditioned text replacement in thecontentfield of the final assembledmessages, using either literal strings or RE2 regular expressions, enhancing dynamic request content rewriting capabilities.
Feature Value: Enables users to flexibly implement text processing needs—including sensitive word filtering, brand term normalization, and placeholder desensitization—without modifying business logic, improving the AI gateway’s adaptability in compliance, security, and multi-tenant scenarios. -
Related PR: #3738
Contributor: @JianweiWang
Change Log: Added configurable fallback JSON paths for response content extraction (responseContentFallbackJsonPathsandresponseStreamContentFallbackJsonPaths) to theai-security-guardplugin, supporting non-OpenAI formats such as Anthropic Claude; when the primary path yields an empty result, fallback paths are attempted sequentially, automatically skipping any fallback path identical to the primary one.
Feature Value: Enhances plugin compatibility and robustness, allowing users to perform content safety checks against diverse LLMs (e.g., Claude) without code changes—reducing multi-model adaptation effort and ensuring stable, accurate response content extraction. -
Related PR: #3734
Contributor: @CH3CHO
Change Log: Added existence check for thepatchcommand in thebuild-envoy.shscript; triggers early failure if missing; also optimized error handling duringbuild-envoy.patchapplication to prevent silent Bazel dependency errors caused by unexecuted patches.
Feature Value: Significantly improves observability and robustness of the Envoy build process; users receive immediate, clear error messages if thepatchcommand is absent, drastically lowering debugging effort and environment configuration troubleshooting costs. -
Related PR: #3724
Contributor: @wydream
Change Log: Added Qwen rerank and conversations API path support to the AI Proxy plugin, extending path mapping rules, API name constants, and Qwen-specific routing logic; supplemented comprehensive regression test cases covering path recognition and provider routing functionality.
Feature Value: Users can invoke Qwen’s reranking and conversational capabilities via standard-compatibility interfaces, improving unified multi-model service access experiences; broadens AI Proxy support for domestic large language models (Qwen), lowering business integration barriers and boosting routing accuracy. -
Related PR: #3700
Contributor: @wydream
Change Log: Added thecooldownDurationconfiguration option to theai-proxyfailover mechanism, enabling automatically restored API keys after a specified millisecond cooldown period—eliminating dependency on real requests for health checking and reducing token consumption and configuration complexity.
Feature Value: Empowers users to manage API key availability more flexibly, mitigating long-term unavailability risks due to rate limiting, saving invocation costs, and simplifying failover configuration to enhance system stability and operational efficiency. -
Related PR: #3694
Contributor: @CH3CHO
Change Log: Added configurable forwarding capability for attributes in external authorization requests, supporting transparent transmission of key contextual fields such asroute_nameandcluster_name; implemented via extension of theAuthorizationRequeststruct with anAllowedPropertiesfield, alongside updates to configuration parsing logic and SDK dependencies.
Feature Value: Enables users to access richer Envoy gateway context information in external authorization services, improving the precision and flexibility of authorization policies and facilitating fine-grained access control based on dimensions like route and cluster—lowering customization development costs. -
Related PR: #3690
Contributor: @JianweiWang
Change Log: Added support for sensitive data masking, enabling desensitization and replacement of sensitive fields in API responses via theriskActionconfiguration (block/mask); introduced new dimension types—customLabel,maliciousFile, andwaterMark—and added dimension-level action configuration to improve risk mitigation flexibility.
Feature Value: Allows dynamic desensitization of sensitive information without service interruption, strengthening AI application compliance capabilities; multi-dimensional, fine-grained risk control strategies enable more precise content security governance—reducing false positives and satisfying regulatory requirements across diverse business scenarios.
-
Related PR: #3829
Contributor: @CH3CHO
Change Log: Fixed a typo in the JSON/YAML tag for theapiTokensfield in theProviderConfigstruct within theai-proxyplugin, correcting it to the proper format to ensure correct configuration parsing and serialization.
Feature Value: Prevents configuration parsing failures or incorrect loading of API tokens caused by erroneous field tags, enhancing the stability and reliability of the AI proxy service and enabling users to seamlessly configure and utilize authentication credentials for various AI providers. -
Related PR: #3801
Contributor: @CH3CHO
Change Log: Fixed logging issues duringEnvoyFilterconstruction regarding unsupported upstream protocols, by adding missing formatting parameters to ensure warning logs correctly display the protocol type and context.
Feature Value: Improves debugging and operational observability, enabling users to accurately identify unsupported protocols and their locations upon misconfiguration—reducing troubleshooting time and enhancing Ingress gateway configuration robustness and maintainability. -
Related PR: #3799
Contributor: @Betula-L
Change Log: Fixed an issue where empty input objects (input:{}) in Claude tool calls were unexpectedly omitted during internal bridge conversion to Bedrock Converse format; addressed via adjustments to struct field JSON tags and expanded test coverage to ensure empty maps are preserved correctly.
Feature Value: Ensures Claude messages using parameterless tools are accurately relayed to the underlying Bedrock service, preventing tool call failures or abnormal behavior caused by missing inputs—improving AI proxy compatibility and reliability in multi-model adaptation scenarios. -
Related PR: #3788
Contributor: @Betula-L
Change Log: Fixed structural data loss in Bedrock Claude inference blocks duringai-proxyprotocol bridging by refactoring theconvertEventFromBedrockToOpenAIlogic and introducingredactedBlockIndexesstate management—ensuringreasoningContentremains within native Anthropic message blocks rather than being merged into plain text.
Feature Value: Users invoking Bedrock Claude models will correctly receive structured reasoning blocks (e.g.,<think>...</think>), avoiding accidental exposure of reasoning processes to end users—enhancing response semantic integrity and compatibility, and guaranteeing Anthropic Messages API specification–compliant interactions. -
Related PR: #3786
Contributor: @Betula-L
Change Log: Fixed incorrect mapping betweencontentBlockIndexin Bedrock Claude streaming responses andtool_calls[].indexin OpenAI format, properly handling index misalignment for parallel tool calls and refiningtool_choiceparameter conversion logic to preserve semantic consistency and ordering fidelity in streaming tool calls withinai-proxy.
Feature Value: Users performing parallel multi-tool calls with Bedrock Claude models will receive accurate, predictable streamingtool_callsindices and correctly triggeredtool_choicebehaviors—preventing tool execution disorder or loss and significantly enhancing production-environment compatibility and reliability. -
Related PR: #3779
Contributor: @CH3CHO
Change Log: Fixed an issue where certain controller logs continued outputting as plaintext despite enabling the--log_as_jsonflag; resolved by uniformly replacing log package imports withistio.io/istio/pkg/log, ensuring all components use the same JSON logging implementation.
Feature Value: Improves log format consistency and observability, facilitating centralized collection, parsing, and analysis of Higress controller logs in environments like Kubernetes—reducing operational troubleshooting cost and strengthening production log standardization. -
Related PR: #3777
Contributor: @wydream
Change Log: Fixed API key injection issues for Vertex AI Express Mode’s raw REST endpoints in theai-proxyplugin, expanding regex patterns to match Express Mode URLs lacking/projects/{project}/locations/{location}path segments and adding test cases validating request header processing logic.
Feature Value: Enables users to correctly invoke simplified Vertex AI Express Mode REST interfaces (e.g.,streamGenerateContent) without manually constructing complex paths, enhancing proxy compatibility and usability—and avoiding 401 authentication failures caused by missing key injection. -
Related PR: #3770
Contributor: @CH3CHO
Change Log: Fixed inability to skip TLS certificate verification for HTTPS upstream connections by adding configuration support for certificate verification bypass inupstreamtls.go, and supplementing protobuf andgoogle.golang.orgdependencies in test files to support unit testing of the new capability.
Feature Value: Enables Higress to support HTTPS upstream services using self-signed certificates, resolving connection failures arising from untrusted certificates in enterprise internal or testing environments—improving deployment flexibility and compatibility. -
Related PR: #3765
Contributor: @wydream
Change Log: Fixedai-proxysupport for Azure OpenAI v1 service URLs by adding recognition and routing logic for/openai/v1and subpaths, accommodating the new URL format withoutapi-versionparameters, while retainingapi-versionvalidation logic for legacy deployment URLs.
Feature Value: Enables users to seamlessly integrate with Azure OpenAI’s latest v1 REST API standard without manually appendingapi-version, enhancing configuration flexibility and service compatibility—reducing request failure rates due to URL format changes and strengthening proxy stability and usability. -
Related PR: #3757
Contributor: @srpatcha
Change Log: Added nil checks, safe type assertions, and panic protection mechanisms to fix multiple potential nil pointer dereferences and type assertion failures; additionally optimized regex compilation logic in WASM plugins to prevent runtime panics.
Feature Value: Significantly improves gateway stability and robustness, preventing service crashes due to anomalous inputs or misconfigurations; users benefit from a more reliable API gateway experience, lowering online failure rates and operational overhead. -
Related PR: #3756
Contributor: @wydream
Change Log: Fixed loss ofthinking/redacted_thinkingcontent blocks during/v1/messagesto OpenAIchat/completionsrequest transformation for Claude, enhanced transmission of tool-call reasoning context, and introducedpreserve_thinkingandpromote_thinking_on_emptyconfiguration options for provider-level compatibility control.
Feature Value: Ensures AI proxies backed by Claude correctly convey complete chain-of-thought information to models supportingreasoning_content(e.g., Qwen), while avoiding compatibility breakage for strict-standard providers like OpenAI/Azure—improving functional consistency and reliability in multi-model routing scenarios. -
Related PR: #3733
Contributor: @wydream
Change Log: Fixed compatibility issues with non-standard upstream responses in Claude streaming transformations: correctly handles empty-stringfinish_reason, prevents duplicate triggering ofmessage_stopdue tousage, and avoids processing redundant chunks aftermessage_stopto prevent event reordering.
Feature Value: Enhances AI proxy stability and reliability in multi-vendor compatibility scenarios, preventing streaming response interruptions or disorder—ensuring users receive complete, chronologically ordered Claude-style SSE streams and improving the overall LLM invocation experience. -
Related PR: #3731
Contributor: @JianweiWang
Change Log: Removed the mandatory fallback interception logic forSuggestion=blockin the AI Security Guard, replacing it with unified risk-dimension–based threshold evaluation; modified core assessment logic inconfig.goand updated multiple test cases to accurately cover threshold-drivenRiskBlockdecision paths.
Feature Value: Improves risk interception accuracy and configurability, preventing unintended blocking caused by misconfiguredSuggestion=block; users now exert precise control over interception behavior via thresholds—enhancing policy transparency, debuggability, and reducing false positive rates. -
Related PR: #3722
Contributor: @wydream
Change Log: Migrated Qwen-compatible response endpoint path from the deprecated legacy URL/api/v2/apps/protocols/compatible-mode/v1/responsesto the new official path/compatible-mode/v1/responses, updating path constants and assertions inprovider/qwen.goand test files to ensure continued valid interface invocation by the AI proxy.
Feature Value: Prevents service disruption caused by Qwen (DashScope) deprecation of the legacy API path, safeguarding stability and continuity of Qwen model invocation viaai-proxy—enabling seamless transition to the new interface without client-side code changes. -
Related PR: #3695
Contributor: @wydream
Change Log: Fixed missing API Key authentication in Vertex Raw Express Mode by appending the API Key to the URL query string inOnRequestBodyand cleaning theAuthorizationheader; also resolved global authentication header leakage and URL construction logic defects in Express Mode.
Feature Value: Enables Vertex Raw Express Mode to authenticate correctly against Google Vertex AI services via API Key—preventing 401 errors; improves proxy stability and compatibility, ensuring users can reliably invoke large language model APIs in this mode. -
Related PR: #3682
Contributor: @CH3CHO
Change Log: Fixed absence ofTARGET_ARCHvalidity checking in thegolang-filterduringbuild-gateway-local, by introducing aVALID_ARCHSwhitelist and error-checking logic inMakefile.core.mk—supporting onlyamd64andarm64, preventing build failures or erroneous binaries from invalid architecture parameters.
Feature Value: Enhances robustness and maintainability of multi-architecture builds, preventing silent build errors or runtime anomalies due to invalidTARGET_ARCHvalues (e.g.,x86,ppc64le); guarantees correct compilation and deployment of the Higress gateway across diverse CPU architectures. -
Related PR: #3576
Contributor: @Jing-ze
Change Log: Fixed staleROUTE_NAMEattribute returning outdated route names post-reroute in WASM contexts, by correcting theStreamInfoImpl::getRouteName()invocation logic in Envoy 1.36 to ensure fresh route names are retrieved afterclearRouteCache.
Feature Value: Ensures WASM plugins correctly match rules following rerouting, preventingmatchRulefailures due to stale route names—improving routing policy execution accuracy and stability, which is critical for user features relying on dynamic route matching. -
Related PR: #3425
Contributor: @CH3CHO
Change Log: Added a default value (higress-registry.cn-hangzhou.cr.aliyuncs.com/higress) to theHUBargument inDockerfile.higress, eliminating build-time warnings whenHUBis not explicitly provided, while preserving backward compatibility: explicitly passed values retain precedence.
Feature Value: Removes redundant warnings during Docker builds, improving CI/CD pipeline readability and stability; users can complete local builds without specifying theHUBparameter—lowering entry barriers and maintenance costs.
-
Related PR: #3830
Contributor: @EndlessSeeker
Change Log: Added OpenSSF Best Practices badges to README files in English, Chinese, and Japanese versions, embedded via Markdown image links pointing to the project’s assessment page on the OpenSSF Best Practices platform—enhancing project compliance and credibility visibility.
Feature Value: Strengthens project transparency and trustworthiness, enabling users to quickly assess Higress’ adherence to open-source best practices in security and maintainability—boosting community and enterprise user confidence and adoption willingness. -
Related PR: #3764
Contributor: @EndlessSeeker
Change Log: UpdatedSECURITY.md,CONTRIBUTINGseries documentation, and addedGOVERNANCE.md, formalizing vulnerability reporting procedures, defining security response SLAs and teams, and clarifying CNCF governance models—meeting CNCF Sandbox and OpenSSF Best Practices certification requirements.
Feature Value: Elevates project security compliance and transparency, providing users with standardized channels and response commitments for security issues—strengthening enterprise user trust; simultaneously enhances multilingual contribution guidelines, lowering global developer participation barriers and promoting healthy, sustainable community growth. -
Related PR: #3754
Contributor: @johnlanni
Change Log: Added a top-levelMAINTAINERS.mdfile listing current Higress project maintainers, including maintainer responsibility descriptions and CNCF Sandbox compliance statements—providing essential governance documentation required for CNCF sandbox onboarding.
Feature Value: Enhances project transparency and community governance standardization, assisting external contributors in identifying core maintenance teams, accelerating CNCF sandbox certification, and laying foundations for future maintainer transitions and permission management—bolstering user confidence in the project’s long-term stability. -
Related PR: #3730
Contributor: @CH3CHO
Change Log: Updated English and Chinese README files to align with the latest configuration parsing logic, correcting contradictory defaults, inaccurate path descriptions, and unclear string concatenation formats, and removing outdated build instructions (e.g.,tinygorequirements).
Feature Value: Improves documentation accuracy and consistency, preventing plugin activation failures stemming from obsolete or erroneous configuration examples; synchronized bilingual documentation lowers comprehension barriers for multilingual users—enhancing AI caching plugin usability and reliability. -
Related PR: #3696
Contributor: @github-actions[bot]
Change Log: Added bilingual release notes files for version 2.2.1 (README.mdandREADME_ZH.md), automatically summarizing 65 updates spanning new features, bug fixes, refactorings, optimizations, and documentation improvements—with categorical statistics.
Feature Value: Provides users with a well-structured, multilingual overview of version changes, accelerating understanding of upgrade benefits and impact scope—enhancing transparency and maintainability and lowering upgrade decision-making costs.
- Related PR: #3790
Contributor: @Jing-ze
Change Log: Expanded integration test coverage for the AI Proxy WASM plugin, including boundary cases for configuration parsing, streaming response body handling, failover verification, and utility function testing; addedexport_test.goto expose internal functions for testing purposes—significantly improving WASM environment test completeness.
Feature Value: Strengthens stability and compatibility assurance for the AI Proxy plugin across diverse WASM runtimes and AI service providers, lowering risks of service interruption arising from configuration anomalies or network failures—enhancing reliability and maintainability for production deployments.
- 🚀 New Features: 13 items
- 🐛 Bug Fixes: 18 items
- 📚 Documentation Updates: 5 items
- 🧪 Testing Improvements: 1 item
Total: 37 changes
Thank you to all contributors for your hard work! 🎉
This release includes 18 updates, covering feature enhancements, bug fixes, performance optimizations, and more.
- New Features: 7 items
- Bug Fixes: 9 items
- Documentation Updates: 2 items
-
Related PR: #621
Contributor: @Thomas-Eliot
Change Log: Enhanced MCP Server interaction capabilities: added support for automaticHostheader rewriting for DNS backends; improved transport protocol selection and full-path configuration in direct routing scenarios; enhanced parsing of special characters (e.g.,@) in DSNs for DB-to-MCP Server scenarios.
Feature Value: Improves flexibility and compatibility of MCP Server integration, enabling users to connect more easily to backend services deployed in diverse environments, reducing configuration complexity, and preventing connectivity issues caused by path prefix misinterpretation or DSN parsing failures. -
Related PR: #608
Contributor: @Libres-coder
Change Log: Added plugin visibility functionality to the AI Route Management page: supports expanding rows to view enabled plugins and displays an'Enabled'badge on the configuration page; extendedPluginListcomponent logic to supportAI_ROUTE-type queries, and enhanced cleanup of i18n language-change listeners inroute.tsx.
Feature Value: Users can now intuitively view plugins enabled for AI routes, aligning the experience with that of conventional route management—improving maintainability and observability of AI route configurations; unified UI interactions reduce learning overhead and enhance completeness of platform support for AI use cases. -
Related PR: #604
Contributor: @CH3CHO
Change Log: Introduced support for regex-based path rewriting via thehigress.io/rewrite-targetannotation, extended Kubernetes annotation constants, route transformation logic, and front-end/back-end internationalized copy, thereby increasing routing match flexibility.
Feature Value: Enables precise control over path rewriting behavior using regular expressions, meeting complex routing requirements such as dynamic path parameter extraction and mapping—significantly enhancing the expressiveness of gateway configuration and its adaptability to business needs. -
Related PR: #603
Contributor: @CH3CHO
Change Log: Added the constantSTATIC_SERVICE_PORT = 80to the static service source form component and explicitly displays this fixed port in the UI, making users clearly aware that static services default to port 80—improving configuration transparency and predictability.
Feature Value: Users configuring static service sources can immediately see that the default port is 80, avoiding configuration errors or debugging difficulties caused by port misconceptions—lowering entry barriers and improving deployment efficiency and consistency of user experience. -
Related PR: #602
Contributor: @CH3CHO
Change Log: Added a search function to the upstream service selection component in AI route configuration; extended theSelectcomponent logic inindex.tsxto enable real-time searching and filtering across large numbers of upstream services—improving configuration efficiency and accuracy.
Feature Value: Users can quickly locate target upstream services when configuring AI routes instead of manually scrolling through long lists—significantly reducing configuration error rates, especially in complex AI gateway scenarios with dozens or more services—enhancing both operational and development efficiency. -
Related PR: #566
Contributor: @OuterCyrex
Change Log: Added support for Tongyi Qwen large language model (LLM) services, including custom service endpoint configuration, Internet search toggle, and file ID upload; implementedQwenLlmProviderHandleron the backend and added multilingual support and provider form adaptation on the frontend.
Feature Value: Enables flexible integration with self-hosted or cloud-based Qwen services, supporting search augmentation and file context injection—improving compatibility and extensibility of the AI gateway for domestic LLMs and lowering enterprise private-deployment barriers. -
Related PR: #552
Contributor: @lcfang
Change Log: Introduced theVPortvirtual port attribute, extending MCP Bridge registry configuration capabilities; added thevportfield and corresponding CRD model toServiceSource, enabling uniform specification of default backend ports for service instances—resolving routing failures caused by inconsistent actual port numbers across instances registered in Eureka/Nacos registries.
Feature Value: Allows users to explicitly declare a virtual port during service discovery configuration, ensuring routing rules remain resilient to backend port changes—preventing traffic disruptions due to dynamic instance port changes, thus improving microservice governance stability and operational predictability.
-
Related PR: #620
Contributor: @CH3CHO
Change Log: Fixed a spelling error in thesortWasmPluginMatchRuleslogic—corrected variable names or logical typos causing potential behavioral anomalies during matching rule sorting—ensuring WASM plugin matching rules are sorted by priority as intended.
Feature Value: Prevents incorrect rule ordering caused by typographical errors, guaranteeing that WASM plugins take effect in Kubernetes strictly according to user-specified priorities—enhancing reliability and consistency of plugin routing and policy enforcement. -
Related PR: #619
Contributor: @CH3CHO
Change Log: Fixed duplicate version information storage when convertingAiRoutetoConfigMap: removed theversionfield from thedataJSON payload, retaining it exclusively in theConfigMapmetadata—to eliminate data redundancy and potential inconsistency.
Feature Value: Improves accuracy and consistency of configuration management, preventing parsing errors or deployment anomalies caused by duplicated version fields—enhancing system stability and maintainability, delivering direct benefits to users managing route configurations via KubernetesConfigMap. -
Related PR: #618
Contributor: @CH3CHO
Change Log: Refactored API authentication logic inSystemController, introducing anAllowAnonymousannotation mechanism to uniformly handle unauthenticated endpoints—replacing hard-coded whitelisting checks—thereby improving maintainability and security of authentication logic.
Feature Value: Resolves potential security vulnerabilities in the system controller that could allow unauthorized access to sensitive API endpoints—enhancing overall platform security, safeguarding user data and system resources from illicit calls, and strengthening compliance and trustworthiness in enterprise production environments. -
Related PR: #617
Contributor: @CH3CHO
Change Log: Fixed missing uniquekeyprops in front-end list rendering (triggering React warnings), resolved Content Security Policy (CSP) blocking of external image loading, and corrected a type definition error for theConsumer.namefield (erroneously typed asbooleaninstead ofstring)—improving component robustness and type safety.
Feature Value: Eliminates console warnings and image-loading failures, improving developer experience and debugging efficiency; corrects interface type definitions to prevent runtime type errors—enhancing application stability and developer collaboration reliability, delivering smoother, warning-free UI interactions for end users. -
Related PR: #614
Contributor: @lc0138
Change Log: Fixed a type definition error for thetypefield (indicating service source) in theServiceSourceclass and added validation logic for dictionary values—ensuring incoming registry types belong exclusively to a predefined valid set—to prevent illegal values from triggering runtime exceptions.
Feature Value: Enhances robustness and security of service source configuration, preventing service registration failure or system exceptions due to invalidtypefield values—ensuring stable, predictable behavior when configuring various service registries. -
Related PR: #613
Contributor: @lc0138
Change Log: Fixed missing Content Security Policy (CSP) configuration on the front end—added a meta tag indocument.tsxto declare the security policy—mitigating risks such as XSS attacks and strengthening security controls over page resource loading and script execution.
Feature Value: Enhances front-end application security posture, effectively mitigating common web threats like cross-site scripting (XSS)—safeguarding user data and interactions, fulfilling enterprise-level security compliance requirements, and reinforcing end-user trust. -
Related PR: #612
Contributor: @zhwaaaaaa
Change Log: Added logic inDashboardServiceImplto ignore hop-to-hop HTTP headers (e.g.,Transfer-Encoding: chunked) per RFC 2616 Section 13.5.1—preventing reverse proxy forwarding anomalies caused by illegal pass-through of hop-to-hop headers, which previously broke Grafana dashboard rendering.
Feature Value: Resolves Grafana console page loading failures caused by reverse proxies forwarding hop-to-hop headers likeTransfer-Encoding: chunked—improving console stability and user experience and ensuring reliable availability of monitoring integration features. -
Related PR: #609
Contributor: @CH3CHO
Change Log: Fixed a type error in theConsumerinterface where thenamefield was incorrectly declared asboolean; corrected it tostringto ensure alignment between front-end data structures and actual back-end response payloads—avoiding runtime errors or TypeScript compilation warnings caused by type mismatches.
Feature Value: Enhances type safety and front-end/back-end data consistency—preventing UI rendering anomalies or flawed logic decisions due to field-type mismatches—boosting application stability, reducing developer debugging effort, and improving overall development experience. -
Related PR: #605
Contributor: @SaladDay
Change Log: Corrected the front-end form validation regex for AI route names to support periods (.) while restricting characters to lowercase letters only; synchronized English and Chinese error message texts to ensure UI prompts precisely reflect actual validation logic.
Feature Value: Resolves issues where users’ AI routes were erroneously rejected or inaccurately warned about names containing periods—improving form usability and user experience; strict alignment between validation rules and UI guidance reduces user cognitive load and operation failure rates.
-
Related PR: #611
Contributor: @qshuai
Change Log: Corrected API endpoint annotations inLlmProvidersControllerfor newly added LLM provider methods—replaced inaccurate summary'Add a new route'with a title accurately reflecting functionality—ensuring generated API documentation (e.g., Swagger) correctly describes actual behavior.
Feature Value: Improves API documentation accuracy and developer experience—preventing misunderstandings by front-end or client developers caused by misleading summaries; enhances professionalism and maintainability of console API docs for users, reducing integration and debugging costs. -
Related PR: #610
Contributor: @heimanba
Change Log: Updatedfrontend-grayplugin documentation to markrewrite,backendVersion, andenabledfields as optional; updated therules.nameassociation path tograyDeployments[].name; and synchronized field descriptions and terminology in both English and ChineseREADMEs andspec.yaml—ensuring configuration guidance accurately reflects the latest design for enhanced flexibility.
Feature Value: Improves compatibility and usability of gray-scale configurations—lowering user configuration barriers; precise field descriptions and consistent terminology reduce misunderstandings and configuration errors—helping developers adopt front-end gray-scale features more efficiently and accurately.
- 🚀 New Features: 7 items
- 🐛 Bug Fixes: 9 items
- 📚 Documentation Updates: 2 items
Total: 18 changes
Thanks to all contributors for their hard work! 🎉
- @Betula-L made their first contribution in https://github.com/alibaba/higress/pull/3786
- @srpatcha made their first contribution in https://github.com/alibaba/higress/pull/3757
- @KevinKingKong made their first contribution in https://github.com/higress-group/higress-console/pull/671
- @zengyr49 made their first contribution in https://github.com/higress-group/higress-console/pull/688
- @huchunnuan made their first contribution in https://github.com/higress-group/higress-console/pull/693
- @zat366 made their first contribution in https://github.com/higress-group/higress-console/pull/697
Full Changelog: https://github.com/alibaba/higress/compare/v2.2.1...v2.2.2
v2.2.1
This release includes 65 updates, covering feature enhancements, bug fixes, and performance optimizations.
- New Features: 29
- Bug Fixes: 26
- Refactoring & Optimizations: 3
- Documentation Updates: 7
-
Related PR: #3689
Contributor: @rinfx
Change Log: Introduces a newmodelToHeaderconfiguration option for themodel-mapperplugin, enabling users to customize the HTTP request header name into which the mapped model is written. The default value isx-higress-llm-model. Additionally, refactors the header update logic to support dynamic configuration and backward compatibility.
Feature Value: Allows users to flexibly specify the request header field name used to propagate LLM model identifiers—meeting diverse backend service integration requirements. Prevents hard-coding–induced compatibility issues and enhances the plugin’s adaptability and governance flexibility in multi-cloud and hybrid deployment scenarios. -
Related PR: #3686
Contributor: @rinfx
Change Log: Adds a newproviderBasePathconfiguration option, allowing definition of a base path prefix inProviderConfig. This prefix is automatically injected into all provider request paths during path rewriting. Also optimizesproviderDomainhandling logic to improve flexibility and reliability when combining domains and paths.
Feature Value: Enables unified API path prefix management viaproviderBasePath, facilitating gateway-level route aggregation, multi-tenancy isolation, and reverse proxy path rewriting. Significantly enhances the AI proxy plugin’s adaptability to complex deployment scenarios such as nested routing and SaaS multi-instance deployments. -
Related PR: #3651
Contributor: @wydream
Change Log: Refactors multipart image request handling logic for the Azure Provider, fixing JSON model mapping errors and inconsistent model mapping in domain-only scenarios. Optimizes memory usage and eliminates redundant reads for large images or high-concurrency workloads, and adds comprehensive test coverage.
Feature Value: Improves stability and performance of Azure image editing/variation APIs, ensuring correct parsing of multipart requests during large image uploads and high-concurrency scenarios—preventing request interruptions due to model mapping failures and increasing user call success rates and response efficiency. -
Related PR: #3649
Contributor: @wydream
Change Log: Implements mapping from OpenAIresponse_formatto VertexgenerationConfigfor the Vertex Provider inai-proxy, with focused support for structured output ingemini-2.5+. Forgemini-2.0-*, adopts a safe-ignore strategy and adds extensive test cases validating structured output logic.
Feature Value: Enables stable use of OpenAI-standard JSON Schema response formats on Vertex backends (especiallygemini-2.5+), improving model output controllability and downstream system integration efficiency. Ensures compatibility with legacy models for seamless service upgrades and reduces migration costs. -
Related PR: #3642
Contributor: @JianweiWang
Change Log: Replaces the original plain-textdenyMessagein the AI Security Guard plugin with a structuredDenyResponseBody, introducing a response schema containingblockedDetails,requestId, andguardCode. Adds JSON serialization support and corresponding construction/parsing helper functions within theconfigpackage.
Feature Value: Delivers richer, standardized denial-response metadata—enabling clients to precisely identify interception reasons, trace request chains, and integrate with risk control systems. Significantly improves troubleshooting efficiency and collaborative security incident analysis capabilities. -
Related PR: #3638
Contributor: @rinfx
Change Log: Adds a universalproviderDomainconfiguration field andresolveDomainDNS resolution logic to theai-proxyplugin, supporting custom domain configuration for Gemini and Claude providers. Integrates this capability intoCreateProviderandTransformRequestHeaders, and supplements full unit test coverage.
Feature Value: Allows users to flexibly connect Gemini and Claude services across different network environments via custom domains—improving deployment flexibility and network adaptability. Particularly beneficial for enterprise intranets, proxy relays, or compliance-driven domain governance scenarios—reducing service invocation failure rates. -
Related PR: #3632
Contributor: @lexburner
Change Log: Introduces a GitHub Actions workflow that automatically builds and pushes theplugin-serverDocker image when anhigressv*.*.*tag is released. Supports specifying theplugin-serverbranch/tag/commit viaworkflow_dispatch, enhancing automation for plugin service deployment.
Feature Value: Eliminates manualplugin-serverimage building and publishing—significantly simplifying version synchronization and deployment processes across the Higress plugin ecosystem. Enhances delivery reliability and efficiency of plugin services while lowering operational overhead. -
Related PR: #3625
Contributor: @johnlanni
Change Log: Adds a newpromoteThinkingOnEmptyconfiguration option: when a model response contains onlyreasoning_contentand notext, it automatically promotesreasoning_contenttotext. Also introduces thehiclawModeshortcut toggle, simultaneously enablingmergeConsecutiveMessagesandpromoteThinkingOnEmpty, supporting HiClaw multi-agent collaboration scenarios—including both streaming (SSE) and non-streaming response paths.
Feature Value: Significantly improves response completeness and downstream compatibility of AI proxies in complex reasoning-chain scenarios—avoiding client exceptions caused by empty responses.hiclawModesimplifies multi-agent coordination configuration, lowers user integration barriers, and enhances robustness and usability in real-world business scenarios. -
Related PR: #3624
Contributor: @rinfx
Change Log: Increases the defaultvalue_length_limitin theai-statisticsplugin from 4000 to 32000 and writes token usage toAILogimmediately upon parsing it during streaming—rather than waiting until stream completion—enhancing large-field support and observability for streaming responses.
Feature Value: Enables more complete logging of long attribute values and real-time token consumption when using coding tools like Codex—improving accuracy of AI invocation behavior analytics. Particularly mitigates token-usage loss caused by premature client disconnections in streaming scenarios—enhancing production monitoring reliability. -
Related PR: #3620
Contributor: @wydream
Change Log: Adds path recognition and routing support for OpenAI speech transcription (/v1/audio/transcriptions), translation (/v1/audio/translations), real-time communication (/v1/realtime), and Qwen-compatible mode Responses API (/api/v2/apps/protocols/compatible-mode/v1/responses). Extends provider mapping relationships and test coverage.
Feature Value: Enables theai-proxyplugin to fully support OpenAI speech and real-time API standards, as well as the Bailian Qwen compatibility protocol—allowing users to seamlessly invoke advanced capabilities like speech processing and real-time streaming interaction. Improves multimodal AI service integration efficiency and protocol compatibility. -
Related PR: #3609
Contributor: @wydream
Change Log: Adds configurable Prompt Cache retention policies for the Amazon Bedrock Provider—supporting both request-level dynamic overrides and provider-level default fallbacks. Unifies and corrects thecached_tokensmeasurement metric and integrates native Bedrock usage fields likecacheReadInputTokens.
Feature Value: Empowers users to flexibly manage Prompt cache lifecycles—improving cache hit rates and cost-effectiveness. Default configuration capability lowers API invocation complexity and improves integration usability. Accurate usage metrics enable granular cost accounting and consumption analytics. -
Related PR: #3598
Contributor: @johnlanni
Change Log: Adds a newmergeConsecutiveMessagesconfiguration option. During AI proxy request preprocessing, it automatically merges consecutive messages of the same role (e.g., multipleusermessages) by traversing and reconstructing themessagesarray—ensuring compatibility with strict alternating-message requirements of non-OpenAI models such as GLM, Kimi, and Qwen.
Feature Value: Enables seamless adaptation of theai-proxyplugin to mainstream domestic and local LLM services—preventing API rejection errors caused by message format noncompliance and significantly improving request success rates and user experience consistency across multi-model scenarios. -
Related PR: #3585
Contributor: @CH3CHO
Change Log: Adds/responsesto the default path suffix list in both themodel-routerandmodel-mapperplugins—natively enabling/v1/responsesinterface invocations without additional configuration required for routing or mapping response-related requests.
Feature Value: Allows users to directly invoke model service response functionality via the/v1/responsespath—improving API consistency and usability. Reduces customization overhead and strengthens the model gateway’s out-of-the-box support for emerging OpenAI-compatible interfaces. -
Related PR: #3570
Contributor: @CH3CHO
Change Log: Upgrades the Console component to v2.2.1 and synchronously releases the main Higress version v2.2.1—updating theVERSIONfile,appVersioninChart.yaml, and dependency versions and digests inChart.lockto ensure the correct Console subchart version is pulled during Helm deployment.
Feature Value: Delivers the latest Console features and UX enhancements—improving management interface stability and compatibility. Semantic version synchronization strengthens cluster deployment consistency, reduces operational risks from version mismatches, and simplifies upgrade procedures. -
Related PR: #3563
Contributor: @wydream
Change Log: Adds OpenAI Prompt Cache parameter support to the Bedrock Provider—implementing conversion of request-sideprompt_cache_retention/prompt_cache_keyto Bedrock’scachePoint, and mapping response-sidecacheRead/cacheWritetokens to OpenAI’scached_tokensfield inusage.
Feature Value: Enables seamless enjoyment of OpenAI Prompt Cache functionality when using Bedrock backends—reducing repeated prompt inference overhead, improving response speed, and saving costs—while delivering standard OpenAI cache-usage metrics for monitoring and billing. -
Related PR: #3550
Contributor: @icylord
Change Log: Adds configurableimagePullPolicysupport for thegateway,plugin server, andcontrollercomponents in the Helm Chart—achieving flexible image pull strategy control via template conditionals and new fields invalues.yaml, enhancing deployment flexibility.
Feature Value: Enables users to define image pull strategies (Always/IfNotPresent/Never) per environment (e.g., dev/staging/prod)—avoiding service disruptions due to image caching issues and improving deployment reliability and operational controllability. -
Related PR: #3536
Contributor: @wydream
Change Log: Adds support for OpenAI image editing (/v1/images/edits) and variation generation (/v1/images/variations) APIs in the Vertex Provider ofai-proxy, implementing multipart/form-data request parsing and transformation, adding JSONimage_urlcompatibility logic, and introducingmultipart_helper.gofor binary image upload handling.
Feature Value: Allows users to directly call Vertex AI image editing and variation features via standard OpenAI SDKs (Python/Node)—without modifying client code—enhancing seamless cross-cloud AI service integration and development efficiency. -
Related PR: #3523
Contributor: @johnlanni
Change Log: Adds tool-call parsing capability for Claude/Anthropic streaming responses in theai-statisticsplugin—supporting event-driven format: identifyingtool_useblocks, accumulating JSON parameter fragments, and fully assembling tool call information. Extends theStreamingParserstruct to track content-block states.
Feature Value: Enables accurate statistics and analysis of streaming tool calls when using Claude models—boosting AI application observability and debugging efficiency. Provides critical support for unified multi-model monitoring and enhances platform compatibility with the Anthropic ecosystem. -
Related PR: #3521
Contributor: @johnlanni
Change Log: Refactors theglobal.hubparameter into a foundational image registry configuration shared across Higress deployments and Wasm plugins—and introduces an independentpluginNamespacenamespace so plugin image paths can be distinguished from core components. Simultaneously unifies image reference logic across multiple Helm templates.
Feature Value: Empowers users to more flexibly manage image sources for different components (e.g., gateway, controller, plugin, Redis)—supporting distinct repositories or paths for plugins versus core components. Improves multi-environment deployment consistency and private customization capabilities—reducing image-pull failure risks. -
Related PR: #3518
Contributor: @johnlanni
Change Log: Adds logic in the Claude-to-OpenAI request transformation process to parse and strip the dynamically changingcchfield from system messages—ensuringx-anthropic-billing-headerremains cacheable. Modifies core transformation code and adds comprehensive unit tests covering this behavior.
Feature Value: Solves Prompt cache invalidation caused by dynamiccchfields—significantly improving AI proxy response speed and service stability, lowering redundant request overhead, and enhancing user interaction experience and CLI tool performance. -
Related PR: #3512
Contributor: @johnlanni
Change Log: Introduces a lightweight mode configuration optionuse_default_response_attributes, skipping buffering of large request/response bodies (e.g.,messages,answer,reasoning) to dramatically reduce memory footprint—suitable for high-concurrency AI observability scenarios in production.
Feature Value: Helps users balance AI observability and resource overhead in production—avoiding OOM risks from full-message-body buffering and improving service stability and throughput. Especially beneficial for long conversations and streaming-response scenarios. -
Related PR: #3511
Contributor: @johnlanni
Change Log: Adds built-insystemfield support to theai-statisticsplugin—parsing the top-levelsystemfield in Claude/v1/messagesAPI responses, extending structured collection capability for Claude system prompts—implemented via defining theBuiltinSystemKeyconstant inmain.go.
Feature Value: Enables accurate statistics and analysis of system prompt content in Claude model invocations—improving AI call observability and compliance auditing capabilities. Supports finer-grained evaluation of prompt engineering effectiveness and implementation of security policies. -
Related PR: #3499
Contributor: @johnlanni
Change Log: Introduces consumer affinity for OpenAI stateful APIs (e.g.,Responses,Files,Batches)—parsing thex-mse-consumerrequest header and consistently selecting the same API token using the FNV-1a hash algorithm—ensuring session stickiness and state continuity across requests.
Feature Value: Solves 404 errors in stateful APIs caused by inconsistent routing under multi-token configurations—significantly enhancing stability and reliability in fine-tuning and response-chaining scenarios. Users receive correct responses without needing to perceive underlying load-distribution logic. -
Related PR: #3489
Contributor: @johnlanni
Change Log: Adds support for z.ai model services—including multilingual brand name display (Chinese “智谱”, English “z.ai”) and an auto-region detection script that determines user region based on system timezone—automatically configuring theapi.z.aidomain and code plan mode options.
Feature Value: Improves out-of-the-box experience for the z.ai service in the Higress AI Gateway—lowering configuration barriers for Chinese and international users. Automatic domain adaptation prevents manual misconfiguration, enhancing deployment reliability and localization friendliness—accelerating AI capability integration. -
Related PR: #3488
Contributor: @johnlanni
Change Log: Adds configurable domain support (China/international dual endpoints), code planning mode routing switching, and thinking mode support for the ZhipuAI provider—extending API request path and authentication adaptation capabilities—to increase flexibility in multi-regional deployments and specialized code-scenario model invocations.
Feature Value: Enables users to flexibly switch ZhipuAI service endpoints per deployment region. Enabling code planning mode delivers superior programming-assistance responses; thinking mode further improves complex reasoning-task outcomes—enhancing AI proxy practicality and adaptability in development scenarios. -
Related PR: #3482
Contributor: @johnlanni
Change Log: Optimizes the OSS skill sync workflow—packing each skill directory into an individual ZIP file (e.g.,my-skill.zip) and uploading tooss://higress-ai/skills/, while maintaining backward compatibility with the AI Gateway installation script.
Feature Value: Enables on-demand download and deployment of specific skills—increasing skill distribution flexibility and reuse efficiency. Avoids full skill-package pulls—reducing bandwidth consumption and deployment time—and enhances edge-scenario adaptability. -
Related PR: #3481
Contributor: @johnlanni
Change Log: Adds a GitHub Action workflow listening for changes in the.claude/skillsdirectory on the.mainbranch—automatically triggering sync to OSS object storage for real-time, automated cloud backup and distribution of skill files.
Feature Value: Eliminates manual skill-file uploads—improving developer collaboration efficiency. Ensures skill version consistency and high availability—facilitating team sharing and rapid deployment—while lowering operational costs and human-error risk. -
Related PR: #3479
Contributor: @johnlanni
Change Log: Adds compatibility logic for non-OpenAI AI providers—automatically converting unsupported'developer'roles to'system'roles in chat completion requests via modifications toprovider.goto unify role mapping adaptation.
Feature Value: Enhances cross-platform compatibility of the AI proxy plugin—enabling developers to use Claude, Anthropic, and other vendor APIs without manually modifying requests—lowering integration barriers and avoiding runtime errors.
-
Related PR: #3667
Contributor: @wydream
Change Log: Fixes incorrect passthrough of non-standard fieldsthinkingandreasoning_max_tokensin Claude-to-OpenAI protocol conversion—retaining only the OpenAI-compliantreasoning_effortfield—to prevent HTTP 400 errors from Azure and other providers.
Feature Value: Improvesai-proxycompatibility and stability with Azure and other standard OpenAI-compatible providers—ensuring successful user requests when invoking Azure via Anthropic protocols and preventing service unavailability due to invalid fields. -
Related PR: #3652
Contributor: @CH3CHO
Change Log: Fixes a regex matching error in the template processor when mixing default and non-default namespaces—strictly restricting/and}characters intype/name/namespace, permitting/only inkeywhile forbidding}—ensuring accurate template reference resolution.
Feature Value: Resolves template parsing failures caused by mixed-namespace usage—improving configuration loading stability and reliability. Prevents silent errors or service anomalies due to illegal character misuse—enhancing system robustness. -
Related PR: #3599
Contributor: @wydream
Change Log: Fixes JSON event fragmentation across network boundaries causing parsing failures in Vertex Provider streaming responses—refactoring chunk buffering and line-boundary detection logic to retain and merge partial JSON payloads—and correcting premature[DONE]marker returns that caused valid data loss.
Feature Value: Improves stability and data integrity of Vertex streaming responses—preventing content truncation or parsing errors for large-model streaming outputs (e.g., extended reasoning chains)—significantly enhancing AI proxy service availability and user experience. -
Related PR: #3590
Contributor: @wydream
Change Log: Fixes a regression in the Bedrock Provider’s SigV4 canonical URI encoding logic: restoresencodeSigV4Pathto applyPathEscapedirectly to path segments—avoiding distortion from double-parsing already-encoded characters (e.g.,%3A,%2F) afterPathUnescape—ensuring signature alignment with AWS service endpoints.
Feature Value: Resolves frequent 403 errors caused by signature failures—particularly affecting model names with special characters (e.g.,nova-2-lite-v1:0or ARN-formatted inference profiles)—significantly boosting production stability and API call success rates. -
Related PR: #3587
Contributor: @Sunrisea
Change Log: Upgradesnacos-sdk-go/v2to v2.3.5—fixing cancellation logic for multi-callback scenarios, supporting multi-cluster service re-subscription, resolving memory leaks, fixing log file handle leaks, and addressing logger initialization regressions—while updating gRPC and Go dependencies.
Feature Value: Improves Nacos client stability and reliability—preventing OOM or resource exhaustion in production due to memory/file-handle leaks. Enhances multi-cluster service discovery capability—improving registration/discovery resilience for microservices in complex topologies. -
Related PR: #3582
Contributor: @lx1036
Change Log: Removes duplicate"istio.io/istio/pilot/pkg/model"package imports inpkg/ingress/translation/translation.go, retaining only the aliased import statement—eliminating compiler warnings and potential symbol collision risks—improving code robustness and maintainability.
Feature Value: Fixes duplicate imports to avoid Go compiler warnings and potential package-initialization conflicts—enhancing code stability. Improves build reliability and long-term maintainability of the Istio Ingress translation module—reducing unexpected error probability. -
Related PR: #3580
Contributor: @shiyan2016
Change Log: Fixes a defect in the KIngress controller’s duplicate route detection logic—incorporating request header matching conditions into deduplication key computation—preventing legitimate routes from being erroneously discarded due to header differences.
Feature Value: Ensures header-differentiated routes are correctly identified and retained—enhancing route configuration reliability and preventing service unavailability or traffic loss from accidental route deletion. -
Related PR: #3575
Contributor: @shiyan2016
Change Log: Fixes a status-update logic error inpkg/ingress/kube/kingress/status.go’supdateStatusmethod—correcting an inverted condition for determining whether to update KIngress status—and avoiding abnormal status synchronization. Adds 186 lines of unit test coverage for this logic.
Feature Value: Ensures accurate and timely updates of KIngress resource statuses (e.g.,LoadBalancerIngress)—preventing service unavailability or inaccurate monitoring alerts due to status misjudgment—enhancing Ingress controller stability and observability. -
Related PR: #3567
Contributor: @DamosChen
Change Log: Fixes occasional endpoint handshake event loss for SSE connections under high load—replacing Redis Pub/Sub–based event publishing with direct asynchronousInjectDatawrites to the SSE response stream via local goroutines—eliminating subscribe-goroutine startup latency and timing races.
Feature Value: Improves SSE connection reliability—ensuring all clients reliably receive endpoint events even under high load or CPU-constrained scenarios—preventing session initialization anomalies and functionality loss from handshake failures—enhancing user experience and system robustness. -
Related PR: #3549
Contributor: @wydream
Change Log: Fixes incomplete SigV4 signature coverage for theai-proxyplugin’s Bedrock Provider in AWS AK/SK auth mode—centralizingsetAuthHeaderscalls from scattered request handlers into theTransformRequestBodyHeadersentrypoint—ensuring all Bedrock APIs (including embeddings and other extensions) undergo full SigV4 signing.
Feature Value: Resolves AWS authentication failures caused by missing SigV4 signatures on some APIs—improving Bedrock Provider stability and compatibility across multifaceted capabilities—enabling reliable use of various Bedrock services (e.g., embedding, converse) without authentication concerns. -
Related PR: #3530
Contributor: @Jing-ze
Change Log: Fixes the Anthropic-compatible API message endpoint path for the Qwen provider—updating the legacy path/api/v2/apps/claude-code-proxy/v1/messagesto the official new path/apps/anthropic/v1/messages—ensuring alignment with the Bailian Anthropic API compatibility documentation.
Feature Value: Enables correct AI proxy invocation of Qwen’s Anthropic-compatible interface—preventing message-request failures from outdated paths—improving service stability and compatibility. Users achieve seamless integration with the latest API without code changes. -
Related PR: #3517
Contributor: @johnlanni
Change Log: Fixes incorrect mapping of OpenAItool-role messages during conversion to Claude protocol—adding logic to transform OpenAItoolmessages into Claude-compatibleuser-role messages embeddingtool_resultcontent—ensuring request format compliance with Claude API specifications.
Feature Value: Enables correct forwarding of OpenAI requests containing tool-call results to Claude models—preventing API rejection errors—improving multi-model protocol compatibility and user stability. Users seamlessly switch backends without modifying existing tool-call logic. -
Related PR: #3513
Contributor: @johnlanni
Change Log: Fixes the absence ofquestionandmodelfields in the AI statistics plugin under lightweight mode—adjusting request-phase attribute extraction logic to extract key fields upfront without buffering response bodies—and updating default attribute configurations.
Feature Value: Makes AI observability data more complete and accurate under lightweight mode—enabling users to obtain question content and model information for analysis—improving debugging efficiency and statistical dimension completeness while preserving low-overhead characteristics. -
Related PR: #3510
Contributor: @johnlanni
Change Log: Fixes improper nesting of thetypefield withindeltaobjects inmessage_deltaevents during Claude protocol conversion—correcting struct definitions inclaude.go, updating conversion logic inclaude_to_openai.go, and synchronizing test cases and model config structures.
Feature Value: Ensures AI proxy compliance with Claude protocol specs when interfacing with OpenAI-compatible services like ZhipuAI—avoiding message parsing failures or streaming response interruptions from malformed formats—enhancing stability and compatibility across multi-model services. -
Related PR: #3507
Contributor: @johnlanni
Change Log: Fixes missingtool_callsdata in Claude AI proxy’s OpenAI-compatible streaming responses—adding correct parsing and conversion ofthinkingcontent—and implementing mapping of OpenAIreasoning_effortto Claudethinking.budget_tokens.
Feature Value: Enables users to fully retrieve tool-call information and reasoning-process content in streaming responses when using Claude as a backend—improving reliability and debuggability of multi-step AI workflows—and enhancing practicality of the OpenAI compatibility layer. -
Related PR: #3506
Contributor: @johnlanni
Change Log: Fixes incorrect conversion of Claude APIstop_reason = 'tool_use'responses into OpenAI-compatibletool_callsformat—unifying handling for both non-streaming and streaming responses—and supplementing missingtool_callsarrays andfinish_reasonmappings.
Feature Value: Enablesai-proxyto correctly relay Claude tool-call responses to OpenAI clients—improving multi-model proxy compatibility and stability—and preventing downstream application failures from format mismatches. -
Related PR: #3505
Contributor: @johnlanni
Change Log: Fixesanswerfield extraction failure in streaming responses—whereextractStreamingBodyByJsonPathreturnednildue to an empty default rule whenuse_default_attributeswas enabled. SetsBuiltinAnswerKey’s rule default toRuleAppendto ensure proper concatenation and extraction of streaming content.
Feature Value: Users reliably captureanswerfield content when using AI streaming-response statistics—avoidingai_logentries withresponse_type = streambut missinganswer—enhancing observation data completeness and debugging efficiency. -
Related PR: #3503
Contributor: @johnlanni
Change Log: Fixes text content loss in Claude protocol conversions when bothtool_resultandtextare present—adding logic inclaude_to_openai.goto preservetext contentand supplementing test cases for multi-content coexistence scenarios.
Feature Value: Ensures user-provided text messages are not lost in tool-call scenarios (e.g., Claude Code)—improving AI proxy compatibility and reliability for mixed-content messages—and enhancing developer experience and debugging efficiency in complex interactive workflows. -
Related PR: #3502
Contributor: @johnlanni
Change Log: Fixes missingeventfield in SSE format for Claude streaming responses—adding necessary event identifiers (event: message_delta,event: message_stop) in[DONE]message handling to ensure full compliance with the official Claude streaming protocol.
Feature Value: Enables correct parsing of Claude model streaming responses—preventing frontend message loss or parsing failures due to malformed formats—enhancing stability and user experience for unified multi-model access. -
Related PR: #3500
Contributor: @johnlanni
Change Log: Changes GitHub Actions workflow runtime environment fromubuntu-latestto fixedubuntu-22.04—resolving CI stability issues where underlying image upgrades causedkindcluster container image loading failures (ctr images importerrors).
Feature Value: Fixes persistent failures in critical CI tasks likehigress-conformance-test—ensuring reliable code-merge workflows and automated validation—preventing developers from being blocked by CI false positives. -
Related PR: #3496
Contributor: @johnlanni
Change Log: Fixes serialization of emptyContentfields insystemprompts for Claude Code mode—adjusting JSON tags inclaudeChatMessageContentstruct to omit emptycontentfields instead of outputtingnull—preventing API request rejections.
Feature Value: Resolves request failures caused by invalidsystemfields in Claude API calls—enhancing system stability and compatibility—ensuring users receive normal responses in Claude Code mode without manually avoiding empty-content scenarios. -
Related PR: #3491
Contributor: @johnlanni
Change Log: Fixes streaming-response body buffering failure in the AI statistics plugin—explicitly settingValueSource = ResponseStreamingBodyfor built-in attributes—ensuringanswerfields are correctly extracted and logged toai_logwhenuse_default_attributesis enabled.
Feature Value: Enables accurate capture and logging of streaming AI responseanswercontent when default attribute collection is enabled—improving log observability and debugging capability—avoiding critical response-data loss leading to analytical blind spots. -
Related PR: #3485
Contributor: @johnlanni
Change Log: Fixes incorrect model-reference prefix logic in Higress providers—removing conditional checks and universally prepending'higress/'to all model IDs (includinghigress/auto)—ensuring correct model-reference formatting in configurations generated by OpenClaw integration plugins.
Feature Value: Resolves configuration-parsing failures caused by missing model-reference prefixes—improving stability and compatibility between Higress and OpenClaw integration—enabling correct use ofhigress/autoand other auto-models without manual configuration corrections. -
Related PR: #3484
Contributor: @johnlanni
Change Log: Fixes installation path issues for thehigress-openclaw-integrationskill—addingmkdir -p higress-installandcd higress-installcommands—and updating the log path from./higress/logs/access.logto./higress-install/logs/access.logto avoid polluting the current working directory.
Feature Value: Isolates Higress installation artifacts in a dedicated directory—improving workspace cleanliness. Enables easy cleanup or reinstallation—reducing environment conflict risks—and enhancing skill-deployment reliability and maintainability. -
Related PR: #3483
Contributor: @johnlanni
Change Log: Fixes path-resolution issues in the skill-packaging workflow—replacing error-prone relative paths with absolute paths based on$GITHUB_WORKSPACE, using subshells to avoid directory-change side effects, and adding output-directory existence checks—improving CI robustness.
Feature Value: Ensures stable ZIP-package generation regardless of execution subdirectory—preventing build failures from path errors—and enhancing OSS skill-sync reliability and developer collaboration efficiency. -
Related PR: #3477
Contributor: @johnlanni
Change Log: Fixes redundant/v1path concatenation in the OpenClaw plugin’sbaseUrl—removing manual/v1additions from functions liketestGatewayConnectionto prevent invalid URLs (e.g.,http://localhost:8080/v1/v1)—ensuring correct gateway request paths.
Feature Value: Resolves API call failures caused by duplicate paths—improving plugin connection stability and compatibility. Users can use model services normally without manual URL adjustments—lowering deployment and debugging barriers.
-
Related PR: #3657
Contributor: @CH3CHO
Change Log: Removes 29 unused Pilot configuration items (e.g.,autoscaleEnabled,replicaCount) fromhigress-core/values.yamlin the Helm Chart—and updates parameter descriptions inREADME.md—streamlining the configuration file and improving chart maintainability and clarity.
Feature Value: Reduces user configuration confusion and avoids deployment anomalies from residual deprecated parameters. Simplifies chart structure—lowering operational complexity and improving upgrade/customization efficiency—helping users focus on core configuration parameters. -
Related PR: #3516
Contributor: @johnlanni
Change Log: Migrates the MCP SDK from an external repository into the main repo—movingmcp-servers/all-in-onetoextensions/mcp-server, introducingpkg/mcp, deleting obsolete modules likepkg/log, and unifying all MCP import paths and dependency references.
Feature Value: Improves code maintainability and build consistency—avoiding cross-repository dependency issues. Users gain more stable MCP functionality—significantly improving plugin development and debugging efficiency—and laying a unified foundation for future MCP capability expansion. -
Related PR: #3475
Contributor: @johnlanni
Change Log: Renames the skill fromhigress-clawdbot-integrationtohigress-openclaw-integration, removes deprecatedagent-session-monitordocumentation content, and updates model IDs across multiple scripts (e.g.,claude-opus-4.5→4.6,gpt-5.2→5.3-codex)—ensuring configuration consistency and naming accuracy.
Feature Value: Enhances project naming standardization and maintainability—avoiding confusion from legacy names. Updated model IDs support newer large-model versions—enabling users to seamlessly leverage higher-performance, more stable models—enhancing AI gateway integration experiences.
-
Related PR: #3644
Contributor: @Jholly2008
Change Log: Fixes two brokenhigress.iolinks inREADME.mdanddocs/architecture.md: replacing the Quick Start link in the English README and the Admin SDK blog link in the architecture doc—ensuring link accuracy and accessibility.
Feature Value: Improves documentation usability and user experience—preventing information-access disruption from broken links. Ensures smooth onboarding for new users and seamless architecture-resource lookup for developers—enhancing project professionalism and credibility. -
Related PR: #3524
Contributor: @github-actions[bot]
Change Log: Adds bilingual (Chinese/English) Release Notes documents for v2.1.11—including release overview, update distribution stats (4 new features, 2 bug fixes), and full changelog structure—automatically generated and maintained by GitHub Actions to ensure version information is traceable and searchable.
Feature Value: Provides users with clear, structured version-upgrade references—helping them quickly understand new features, fixes, and compatibility changes. Enhances product transparency and usability—reducing upgrade risks and learning costs. -
Related PR: #3490
Contributor: @johnlanni
Change Log: Optimizes the model provider list in the OpenClaw integration skill documentation—topping 8 frequently used providers (Zhipu, Claude Code, Moonshot, etc.) and collapsing infrequent ones into expandable sections—to improve readability and information hierarchy.
Feature Value: Significantly improves the new-user configuration experience for Higress AI Gateway—lowering learning costs. Structured presentation of provider options helps users rapidly identify mainstream supported models—enhancing OpenClaw skill usability and adoption efficiency. -
Related PR: #3480
Contributor: @johnlanni
Change Log: Updates the OpenClaw integration documentationSKILL.md—adding dynamic configuration update instructions covering LLM provider hot-addition, online API key updates, and multi-model auto-routing mechanisms—and adding configuration-update guidance prompts in plugin hints.
Feature Value: Helps users understand how to dynamically extend and update AI service configurations without restarts—lowering operational barriers and improving multi-model switching and management flexibility—enhancing product usability and enterprise-grade configuration governance. -
Related PR: #3478
Contributor: @johnlanni
Change Log: Explicitly labels OpenClaw’s Higress plugin-related commands inSKILL.mdas interactive operations—adding warning prompts and separating user-manual-execution steps—to avoid AI agents executing them incorrectly.
Feature Value: Helps users clearly identify commands requiring manual intervention—improving integration process predictability and success rates—while reducing operation failures and debugging costs caused by AI agents attempting interactive command execution. -
Related PR: #3476
Contributor: @johnlanni
Change Log: Refactors thehigress-openclaw-integrationskill documentation—simplifying deployment from 6 steps to 3, collecting all necessary information upfront—and adding a 21+-provider comparison table clarifying model-prefix patterns and OAuth token requirements for Claude.
Feature Value: Significantly boosts skill invocation success rates and stability—even for weaker AI agents—reducing user comprehension and usage barriers. Minimizes configuration errors from verbose steps or missing info—accelerating Higress AI Gateway adoption within the OpenClaw ecosystem. -
Related PR: #3468
Contributor: @github-actions[bot]
Change Log: Adds bilingual (Chinese/English) release notes for v2.2.0—including release overview, update distribution stats (48 new features, 20 bug fixes, etc.), and full changelog—automatically generated by GitHub Actions to ensure authoritative, timely, and bilingual version information.
Feature Value: Provides users and developers with clear, structured version-upgrade references—lowering usage barriers and migration costs. Bilingual support improves accessibility for international users—enhancing project professionalism and community trust.
- 🚀 New Features: 29
- 🐛 Bug Fixes: 26
- ♻️ Refactoring & Optimizations: 3
- 📚 Documentation Updates: 7
Total: 65 changes
Thank you to all contributors for your hard work! 🎉
This release includes 18 updates, covering feature enhancements, bug fixes, and performance optimizations.
- New Features: 7
- Bug Fixes: 9
- Documentation Updates: 2
-
Related PR: #621
Contributor: @Thomas-Eliot
Change Log: Enhanced MCP Server interaction capabilities: supports automatic Host header rewriting for DNS backends; improves transport protocol selection and full-path configuration in direct routing scenarios; refines parsing of DSN special characters (e.g.,@) in DB-to-MCP Server scenarios.
Feature Value: Improves the flexibility and compatibility of MCP Server integration, reduces user configuration complexity, prevents connection failures caused by path prefix ambiguity or DSN special characters, and significantly enhances multi-environment deployment experience and system stability. -
Related PR: #608
Contributor: @Libres-coder
Change Log: Added plugin display functionality to the AI Route Management page, supporting expansion to view enabled plugins and showing an "Enabled" badge in the configuration panel; reused the standard route plugin display logic, involving frontend AI route components, plugin list query logic, and route page initialization optimization.
Feature Value: Enables users to intuitively view and verify enabled plugins directly within the AI Route Management interface, improving observability and operational consistency of AI route configurations, reducing misconfiguration risks, and enhancing unified platform management experience and operational efficiency. -
Related PR: #604
Contributor: @CH3CHO
Change Log: Added support for regular expression-based path rewriting via thehigress.io/rewrite-targetannotation; extended Kubernetes annotation constants, updated route transformation logic, introduced a regex rewrite type enumeration, and added frontend i18n support.
Feature Value: Empowers users to define flexible path rewriting rules using regular expressions, enhancing routing match precision and adaptability—ideal for complex URL transformation scenarios—while lowering gateway configuration barriers and strengthening business integration capability. -
Related PR: #603
Contributor: @CH3CHO
Change Log: Introduced the constantSTATIC_SERVICE_PORT = 80in the static service source form component and explicitly displays this fixed port in the UI, enabling users to clearly understand the default HTTP port bound to static services and thereby improving configuration transparency and comprehensibility.
Feature Value: Users can visually identify the default port80when configuring static service sources, preventing service access failures caused by port misunderstanding; lowers operational overhead and improves deployment efficiency and user experience consistency. -
Related PR: #602
Contributor: @CH3CHO
Change Log: Added search functionality to the upstream service selection component in AI Routes, enabling frontend input filtering of the service list to improve selection efficiency for long lists; achieved via minimal code changes to theRouteFormcomponent to enhance interactivity.
Feature Value: Allows users to quickly search and locate target upstream services during AI route configuration, significantly improving usability when numerous services exist, reducing configuration error rates, and boosting both operational and development efficiency. -
Related PR: #566
Contributor: @OuterCyrex
Change Log: Added support for Tongyi Qwen large language model (LLM) services, including a dedicatedQwenLlmProviderHandlerimplementation, frontend i18n adaptation, and a configuration form supporting custom service endpoints, internet search, and file ID uploads.
Feature Value: Enables flexible integration of private or customized Qwen services, improving AI gateway compatibility with domestic LLMs; simplifies deployment workflows via the configuration UI, lowers enterprise-level AI service integration barriers, and strengthens platform extensibility. -
Related PR: #552
Contributor: @lcfang
Change Log: Added support for thevport(virtual port) attribute to extend MCP Bridge registry configuration capabilities; introduced theVPortclass intoServiceSource, enhanced Kubernetes model conversion logic, and made service virtual ports configurable—resolving routing failures caused by dynamic backend instance port changes in registries such as Eureka/Nacos.
Feature Value: Allows users to specify a service virtual port (vport) in registry configurations, ensuring routing rules remain effective despite backend port changes; enhances service governance stability and compatibility, reduces traffic forwarding anomalies due to port mismatches, and simplifies multi-environment deployment and operational complexity.
-
Related PR: #620
Contributor: @CH3CHO
Change Log: Fixed a typo in thesortWasmPluginMatchRuleslogic, correcting variable or method name errors that could cause latent logic anomalies during matching rule sorting—ensuring Wasm plugin rules are sorted correctly according to their intended priority.
Feature Value: Prevents matching rule sorting errors caused by typos, guaranteeing accurate application order of Wasm plugins in Kubernetes CRs; improves reliability of plugin-based routing and policy enforcement, reducing issues where configured behavior deviates from expectations. -
Related PR: #619
Contributor: @CH3CHO
Change Log: Fixed redundant version information storage when convertingAiRoutetoConfigMap: removed theversionfield from thedataJSON payload, retaining it solely in theConfigMapmetadata to eliminate data redundancy and potential inconsistency.
Feature Value: Improves configuration management accuracy and consistency, preventing parsing errors or synchronization anomalies caused by duplicate version fields; enhances system stability and operational reliability—delivering direct benefits to users managing route configurations via Kubernetes ConfigMaps. -
Related PR: #618
Contributor: @CH3CHO
Change Log: Refactored API authentication logic inSystemController, introducing an@AllowAnonymousannotation mechanism for unified handling of unauthenticated endpoints; replaced hardcoded path whitelists with AOP-based fine-grained access control, resolving a security vulnerability permitting unauthorized access to sensitive system interfaces.
Feature Value: Addresses a latent unauthorized access vulnerability in the system controller, significantly improving platform security; delivers stronger permission guarantees for users and mitigates risks of data leakage or privilege escalation caused by authentication logic defects—enhancing compliance and stability in production environments. -
Related PR: #617
Contributor: @CH3CHO
Change Log: Fixed three critical frontend console issues: missing uniquekeyprops causing React warnings during list rendering; Content Security Policy (CSP) blocking remote image loading; and incorrect type definition for theConsumer.namefield (corrected frombooleantostring).
Feature Value: Improves frontend application stability and user experience, eliminating console errors that interfere with development debugging, ensuring proper avatar rendering and accurate consumer information parsing, and preventing runtime exceptions or data display issues caused by type mismatches. -
Related PR: #614
Contributor: @lc0138
Change Log: Corrected the type definition of thetypefield (indicating service source) in theServiceSourceclass and added validation logic to ensure incoming registry types belong to a predefined set, preventing illegal values from triggering runtime exceptions.
Feature Value: Enhances system robustness and data consistency, avoiding configuration parsing failures or backend exceptions caused by invalid service source types; ensures reliable operation of service registration and discovery functions and reduces operational troubleshooting effort. -
Related PR: #613
Contributor: @lc0138
Change Log: Fixed a frontend Content Security Policy (CSP) configuration defect by adding essential<meta>tags and security policy declarations indocument.tsx, preventing XSS and other malicious script injections and strengthening security header control during page loading.
Feature Value: Significantly reduces the risk of cross-site scripting (XSS) attacks and data injection vulnerabilities in the frontend application, enhancing user access security and trust; aligns with modern web security best practices and provides more reliable security assurance for production environments. -
Related PR: #612
Contributor: @zhwaaaaaa
Change Log: Added logic inDashboardServiceImplto ignore hop-to-hop headers (e.g.,Transfer-Encoding) per RFC 2616, filtering headers that must not be forwarded by proxies—resolving Grafana frontend page load failures caused by reverse proxies transmittingTransfer-Encoding: chunked.
Feature Value: Fixes the issue whereTransfer-Encoding: chunkedheaders transmitted by reverse proxies cause Grafana frontend pages to crash, improving stability and compatibility when integrating external monitoring services in the console; enables seamless dashboard access for users. -
Related PR: #609
Contributor: @CH3CHO
Change Log: Fixed a type error in theConsumerinterface’snamefield, correcting it frombooleantostringto ensure frontend data structures align with actual backend response values and avoid runtime type errors and UI rendering anomalies.
Feature Value: Enhances accuracy and stability of consumer information display, preventing page crashes or incorrect data rendering due to type mismatches, and improving user experience and system reliability during consumer management. -
Related PR: #605
Contributor: @SaladDay
Change Log: Corrected the frontend form validation regex for AI route names, adding support for periods (.) and restricting alphabetic characters to lowercase only; simultaneously updated Chinese and English error messages to accurately reflect the revised rules.
Feature Value: Resolves issues where users incorrectly receive rejection errors when creating AI routes with names containing periods or uppercase letters; improves consistency between form validation logic and UI prompts, reduces configuration failure rates, and enhances overall usability.
-
Related PR: #611
Contributor: @qshuai
Change Log: Corrected the OpenAPI documentation summary comment for the@PostMappingendpoint inLlmProvidersController, replacing the inaccurate description “Add a new route” with a precise one reflecting its actual purpose (adding an LLM provider). Ensures API documentation matches real functionality.
Feature Value: Improves API documentation accuracy, helping developers correctly understand the endpoint’s purpose—reducing integration misunderstandings and debugging effort—and enhancing the maintainability and user experience of the console’s APIs. -
Related PR: #610
Contributor: @heimanba
Change Log: Updated frontend canary plugin documentation: changedrewrite,backendVersion, andenabledfields from required to optional; corrected the associated path for thenamefield withinrules(fromdeploy.gray[].nametograyDeployments[].name); and synchronized field descriptions and requirements across Chinese/EnglishREADMEs andspec.yaml.
Feature Value: Increases configuration flexibility and compatibility, lowering the barrier to adopting canary capabilities; provides more precise terminology and path references, minimizing configuration errors caused by documentation ambiguity and enhancing developer experience and documentation credibility.
- 🚀 New Features: 7
- 🐛 Bug Fixes: 9
- 📚 Documentation Updates: 2
Total: 18 changes
Thank you to all contributors for your hard work! 🎉
- @DamosChen made their first contribution in https://github.com/alibaba/higress/pull/3567
- @lx1036 made their first contribution in https://github.com/alibaba/higress/pull/3582
- @Sunrisea made their first contribution in https://github.com/alibaba/higress/pull/3587
- @shiyan2016 made their first contribution in https://github.com/alibaba/higress/pull/3575
- @Jholly2008 made their first contribution in https://github.com/alibaba/higress/pull/3644
- @JianweiWang made their first contribution in https://github.com/alibaba/higress/pull/3642
- @icylord made their first contribution in https://github.com/alibaba/higress/pull/3550
Full Changelog: https://github.com/alibaba/higress/compare/v2.2.0...v2.2.1
v2.1.11
This release includes 6 updates, covering feature enhancements, bug fixes, and performance optimizations.
- New Features: 4
- Bug Fixes: 2
-
Related PR: #666
Contributor: @johnlanni
Change Log: Added configuration options for the plugin image registry and namespace. Supports dynamically specifying built-in WASM plugin image addresses via environment variablesHIGRESS_ADMIN_WASM_PLUGIN_IMAGE_REGISTRY/NAMESPACE, eliminating the need to modifyplugins.properties. Corresponding Helm Chartvaluesparameters and deployment template rendering logic have also been integrated.
Feature Value: Enables users to flexibly configure WASM plugin image sources across diverse network environments (e.g., private cloud, air-gapped environments), improving deployment flexibility and security; reduces operational overhead and mitigates maintenance difficulties and upgrade risks associated with hard-coded configurations. -
Related PR: #665
Contributor: @johnlanni
Change Log: Added support for Zhipu AI’s Code Plan mode and Claude’s API version configuration. Achieved by extendingZhipuAILlmProviderHandlerandClaudeLlmProviderHandlerto support custom domains, code-generation optimization toggles, and API version parameters—enhancing LLM invocation flexibility and scenario adaptability.
Feature Value: Allows users to enable model-specific code generation modes (e.g., Zhipu Code Plan) based on AI vendor characteristics and precisely control Claude API versions, significantly improving code generation quality and compatibility, lowering integration barriers, and strengthening the practicality of the AI Gateway in multi-model collaborative development scenarios. -
Related PR: #661
Contributor: @johnlanni
Change Log: Introduced a lightweight mode configuration for the AI statistics plugin. Added theUSE_DEFAULT_ATTRIBUTESconstant and enableduse_default_response_attributes: trueinAiRouteServiceImpl, reducing response attribute collection overhead and preventing memory buffer issues.
Feature Value: Improves production environment stability and performance while lowering resource consumption of AI route statistics; eliminates the need for manual configuration of complex attributes—the system automatically adopts a default, streamlined attribute set—simplifying operations and enhancing reliability under high-concurrency workloads. -
Related PR: #657
Contributor: @liangziccc
Change Log: Removed the original text-input search from the Route Management page and introduced multi-select dropdown filters for five fields: Route Name, Domain, Route Conditions, Destination Service, and Request Authorization. Completed Chinese–English internationalization support and implemented multi-dimensional composite filtering (OR within each field, AND across fields), significantly improving data filtering precision.
Feature Value: Enables users to quickly locate specific routes via intuitive dropdown selection, avoiding input errors; bilingual support accommodates international usage scenarios; multi-condition combined filtering substantially boosts query efficiency and operational experience for SREs managing large-scale route configurations.
-
Related PR: #662
Contributor: @johnlanni
Change Log: Fixed an issue where the OCI image path for themcp-serverplugin was not migrated synchronously—updated the original pathmcp-server/all-in-onetoplugins/mcp-serverto align with the new plugin directory structure, ensuring correct plugin loading and deployment.
Feature Value: Prevents plugin pull or startup failures caused by incorrect image paths, guaranteeing stable operation and seamless upgrades of themcp-serverplugin within the Higress Gateway, thereby enhancing deployment reliability in plugin-driven use cases. -
Related PR: #654
Contributor: @fgksking
Change Log: Upgraded theswagger-uiversion dependency ofspringdocby introducing a newer version of thewebjars-lodependency inpom.xmland updating related version properties, resolving an issue where request body schemas appeared empty in Swagger UI.
Feature Value: Ensures users can correctly view and interact with request body structures when using the API documentation functionality in the Higress Console, improving API debugging experience and development efficiency—and preventing interface misinterpretations caused by documentation display anomalies.
- 🚀 New Features: 4
- 🐛 Bug Fixes: 2
Total: 6 changes
Thank you to all contributors for your hard work! 🎉
Full Changelog: https://github.com/alibaba/higress/compare/v2.1.10...v2.1.11
v2.2.0
This release includes 73 updates, covering enhancements, bug fixes, performance optimizations, and more.
- New Features: 48
- Bug Fixes: 20
- Refactoring and Optimization: 3
- Documentation Updates: 2
-
Related PR: #3459
Contributor: @johnlanni
Change Log: Added support for Claude Code mode, allowing authentication with OAuth tokens and mimicking the request format of the Claude CLI.
Feature Value: This feature expands the ability to interact with the Anthropic Claude API, enabling users to utilize more customized configuration options to meet specific needs. -
Related PR: #3455
Contributor: @EndlessSeeker
Change Log: This PR updated the project's submodules, including upgrading Envoy and go-control-plane versions, and updating Istio to use the latest version of go-control-plane.
Feature Value: By synchronizing with the latest key dependency libraries, it enhances system compatibility and stability, helping users receive better service and support. -
Related PR: #3438
Contributor: @johnlanni
Change Log: Improved the documentation structure of the higress-clawdbot-integration skill, streamlined and merged duplicate content, and achieved full compatibility with the Clawdbot plugin.
Feature Value: By optimizing the documentation structure and ensuring the compatibility of the Clawdbot plugin, it enhances the user experience, simplifies the configuration process, and allows users to integrate and configure the gateway more quickly and conveniently. -
Related PR: #3437
Contributor: @johnlanni
Change Log: This PR integrated thehigress-ai-gatewayplugin into thehigress-clawdbot-integrationskill, simplifying the installation and configuration process by migrating and bundling related files.
Feature Value: This feature enables users to more easily install and configure Higress AI Gateway with Clawbot/OpenClaw, enhancing user experience and software usability. -
Related PR: #3436
Contributor: @johnlanni
Change Log: This PR updated the list of service providers in the Higress-OpenClaw integration and moved the OpenClaw plugin package from higress-standalone to the main repository.
Feature Value: By enhancing the list of service providers and integrating the plugin package, users can more easily configure and use Higress AI Gateway, improving the user experience and system flexibility. -
Related PR: #3428
Contributor: @johnlanni
Change Log: Added two new skills, higress-auto-router and higress-clawdbot-integration, supporting natural language configuration for automatic model routing and deployment of Higress AI Gateway via CLI parameters.
Feature Value: This enhancement improves the integration capabilities of Higress AI Gateway with Clawbot, providing users with a more convenient configuration method and flexible routing strategies, thereby enhancing the user experience. -
Related PR: #3427
Contributor: @johnlanni
Change Log: Added theuse_default_attributesconfiguration option, allowing the ai-statistics plugin to use a default attribute set, simplifying the user configuration process. This change involves significant modifications to the main logic file.
Feature Value: By introducing the functionality to automatically apply default attributes, it reduces the initial setup burden for users, making the ai-statistics plugin easier to get started with while maintaining advanced customization capabilities to meet specific needs. -
Related PR: #3426
Contributor: @johnlanni
Change Log: Added the Agent Session Monitor skill, supporting real-time parsing of Higress access logs, tracking multi-turn conversations throughsession_id, and providing token usage analysis.
Feature Value: By monitoring the real-time usage of LLMs in the Higress environment, users can better understand and control resource consumption, optimizing the performance of the conversation system. -
Related PR: #3424
Contributor: @johnlanni
Change Log: This PR added support for detailed token usage information in the ai-statistics plugin, including two new built-in attribute keys:reasoning_tokensandcached_tokens.
Feature Value: By recording more detailed token usage, users can better understand and optimize resource consumption during the AI inference process, which helps improve efficiency and reduce costs. -
Related PR: #3420
Contributor: @johnlanni
Change Log: This PR added session ID tracking to the AI statistics plugin, supporting the retrieval of session IDs through custom headers or default headers to track multi-turn conversations.
Feature Value: The new session ID tracking capability helps users better analyze and understand the interaction of multi-turn conversations, enhancing the observability and user experience of the system. -
Related PR: #3417
Contributor: @johnlanni
Change Log: Added an important warning about unsupported fragments and provided pre-migration check commands to help users identify affected Ingress resources.
Feature Value: By providing critical warnings and guidelines, this feature significantly reduces potential issues during migration, improving the user experience and migration success rate. -
Related PR: #3411
Contributor: @johnlanni
Change Log: Added a skill for migrating from ingress-nginx to Higress, including analyzing existing Nginx Ingress resources, generating migration test scripts, and creating Wasm plugin frameworks for unsupported features.
Feature Value: This feature helps users smoothly migrate their Kubernetes environments from ingress-nginx to Higress, providing detailed migration guides and tools to reduce migration burdens and enhance the user experience. -
Related PR: #3409
Contributor: @johnlanni
Change Log: Added thecontextCleanupCommandsconfiguration option, allowing users to define commands to clean up the conversation context. When a user message exactly matches the configured cleanup command, all non-system messages before that command will be cleared.
Feature Value: This feature enables users to actively manage their conversation history by sending predefined commands to clear irrelevant or outdated messages, thus improving the quality and relevance of the conversation. -
Related PR: #3404
Contributor: @johnlanni
Change Log: Added the Higress community governance daily report generation skill, which can automatically track project GitHub activity and generate structured reports.
Feature Value: This feature helps users better track and manage the daily progress and issue resolution of the project, enhancing community engagement and issue resolution efficiency. -
Related PR: #3403
Contributor: @johnlanni
Change Log: This PR added an automatic routing feature based on the content of user messages to the model-router plugin. It uses regular expressions to match user input and decide which model to use.
Feature Value: This feature allows the selection of the most appropriate processing model based on the message content, greatly enhancing the user experience and system flexibility, making the service more intelligent and efficient. -
Related PR: #3402
Contributor: @johnlanni
Change Log: Added a Claude skill for developing Higress WASM plugins using Go 1.24+, covering reference documents for HTTP client, Redis client, and local testing.
Feature Value: This feature provides a comprehensive guide for developers to create and debug Higress gateway plugins, significantly improving work efficiency and plugin quality. -
Related PR: #3394
Contributor: @changsci
Change Log: Whenprovider.apiTokensis not configured, support retrieving the API key from the request header. The changes mainly involve importingproxywasminopenai.goand adding related configuration logic inprovider.go.
Feature Value: This feature enhances system flexibility, allowing users to pass the API key through the request header, thus enabling normal service use even whenprovider.apiTokensis not configured, improving the user experience and security. -
Related PR: #3384
Contributor: @ThxCode-Chen
Change Log: This PR enhanced the system's ability to handle IPv6 addresses by adding support for static IPv6 addresses in thewatcher.gofile. Specifically, it introduced new logic in thegenerateServiceEntryfunction to recognize and handle static IPv6 addresses.
Feature Value: The added support for static IPv6 addresses allows users to use IPv6 addresses in their network configurations, enhancing the system's network flexibility and compatibility, and providing convenience for users who need to deploy in an IPv6 environment. -
Related PR: #3375
Contributor: @wydream
Change Log: This PR added Vertex Raw mode support to the Vertex AI Provider of the ai-proxy plugin, enabling thegetAccessTokenmechanism when accessing native REST APIs via Vertex.
Feature Value: The added Vertex Raw mode support enhances the user's ability to directly invoke Vertex AI hosted models and ensures automatic OAuth authentication when using native API paths, improving the user experience. -
Related PR: #3367
Contributor: @rinfx
Change Log: This PR updated the wasm-go dependency, introducing Foreign Function to enable Wasm plugins to perceive the log level of the Envoy host in real-time and optimizing the log handling process to improve performance.
Feature Value: This feature enhances system runtime efficiency, especially under high load, by reducing unnecessary memory allocation and copying operations, resulting in lower resource consumption and better application response speed for users. -
Related PR: #3342
Contributor: @Aias00
Change Log: This PR implemented the mapping of Nacos instance weights to Istio WorkloadEntry weights in watchers, ensuring more precise traffic distribution between services.
Feature Value: By mapping Nacos instance weights to Istio WorkloadEntry weights, it enhances the flexibility and accuracy of traffic management in the service mesh, allowing users to more finely control request distribution between services. -
Related PR: #3335
Contributor: @wydream
Change Log: This PR added image generation support to the Vertex AI Provider of the ai-proxy plugin, implementing the conversion of OpenAI's image generation protocol to Vertex AI's image generation protocol.
Feature Value: Users can now call the image generation functionality of Vertex AI using the standard OpenAI SDK, enhancing the plugin's functionality and user experience. -
Related PR: #3324
Contributor: @wydream
Change Log: This PR implemented OpenAI-compatible endpoint support in the Vertex AI Provider of the ai-proxy plugin, allowing developers to directly use the OpenAI SDK and API format to call Vertex AI models.
Feature Value: By adding OpenAI-compatible endpoint support, this feature simplifies the migration process from OpenAI to Vertex AI, making it easier for users to seamlessly integrate Vertex AI services using existing OpenAI toolchains, enhancing development efficiency and user experience. -
Related PR: #3318
Contributor: @hanxiantao
Change Log: Applied Istio's native authentication logic to the debug endpoint using thewithConditionalAuthmiddleware, while maintaining the existing behavior based on theDebugAuthfeature flag.
Feature Value: This enhancement enhances system security by ensuring that only authenticated users can access the debug endpoint, thereby reducing potential security risks and providing a more secure service environment. -
Related PR: #3317
Contributor: @rinfx
Change Log: Added two Wasm-Go plugins,model-mapperandmodel-router, supporting mapping and routing based on themodelparameter in the LLM protocol, including prefix matching and wildcard fallback.
Feature Value: This enhancement improves Higress's ability to handle large language model requests, improving the user experience and service efficiency by more flexibly managing model names and provider information. -
Related PR: #3305
Contributor: @CZJCC
Change Log: Added Bearer Token authentication support for the AWS Bedrock provider, retaining the original AWS Signature V4 authentication method and cleaning up some unused code.
Feature Value: This feature provides more flexible authentication options, allowing users to choose the appropriate authentication method based on their needs, thereby enhancing the system's flexibility and security. -
Related PR: #3301
Contributor: @wydream
Change Log: This PR implemented Express Mode support for the Vertex AI Provider of the ai-proxy plugin, simplifying the authentication process and allowing users to start using an API Key quickly.
Feature Value: By adding Express Mode support, users no longer need to configure complex Service Account authentication to use Vertex AI, significantly lowering the entry barrier and enhancing the user experience. -
Related PR: #3295
Contributor: @rinfx
Change Log: This PR added MCP support to the ai-security-guard plugin, including security checks for both standard and streaming responses.
Feature Value: By adding support for MCP API types, the plugin can now better protect data related to the model context protocol, enhancing the overall security of the system. -
Related PR: #3267
Contributor: @erasernoob
Change Log: This PR implemented the hgctl agent module, adding new features and related services, and updating dependencies.
Feature Value: The new hgctl agent module provides users with more powerful command-line tool support, enhancing the system's operability and user experience. -
Related PR: #3261
Contributor: @rinfx
Change Log: This PR added the ability to disable thinking for gemini-2.5-flash and its simplified version, and included reasoning token usage information in the response.
Feature Value: By adding the ability to disable thinking and providing reasoning token consumption details, users can more flexibly control the behavior of the AI proxy and better understand resource consumption. -
Related PR: #3255
Contributor: @nixidexiangjiao
Change Log: Improved the global minimum request count load balancing strategy, fixing issues with abnormal node preference, inconsistent new node handling, and uneven sampling distribution, enhancing the stability and accuracy of the algorithm.
Feature Value: By optimizing the load balancing algorithm, it avoids concentrating traffic on faulty nodes, leading to service interruptions, and enhances system availability and reliability, reducing operational burdens. -
Related PR: #3236
Contributor: @rinfx
Change Log: This PR implemented support for the Claude model in Vertex AI and handled cases where delta might be empty, ensuring system stability in edge cases.
Feature Value: The added support for the Claude model in Vertex AI broadens the application scenarios of the AI proxy plugin, allowing users to leverage a wider range of AI models, increasing the system's flexibility and applicability. -
Related PR: #3218
Contributor: @johnlanni
Change Log: Enhanced the model mapper and router, adding request count monitoring and memory usage monitoring, and setting up an automatic rebuild trigger mechanism; expanded supported path suffixes.
Feature Value: By adding an automatic rebuild trigger mechanism, it enhances the stability of the service under high load or low memory conditions. The expanded path support allows more features to be correctly routed and processed, improving the system's flexibility and compatibility. -
Related PR: #3213
Contributor: @rinfx
Change Log: This PR added support for global regions in the Vertex AI support, modifying the request domain to accommodate the latest Gemini-3 series models.
Feature Value: This enhancement improves system compatibility, allowing users to seamlessly access the latest Gemini-3 series models, enhancing the user experience and system flexibility. -
Related PR: #3206
Contributor: @rinfx
Change Log: This PR implemented content checking for prompts and images in the request body for the AI security guard plugin, enhancing content security detection.
Feature Value: By supporting checks for prompts and images, it improves the system's security when handling image generation requests, helping to protect users from inappropriate content. -
Related PR: #3200
Contributor: @YTGhost
Change Log: This PR added support for array-type content in the ai-proxy plugin, extending thechatToolMessage2BedrockMessagefunction's handling capabilities.
Feature Value: This enhancement improves message processing, allowing the system to correctly parse and convert array-formatted message content, enhancing the user experience and system flexibility. -
Related PR: #3185
Contributor: @rinfx
Change Log: This PR added a rebuild logic for ai-cache, optimizing memory management to avoid high memory usage issues. The changes are mainly concentrated ingo.mod,go.sum, andmain.gofiles.
Feature Value: The newly added ai-cache rebuild logic effectively prevents memory overflow issues caused by caching, enhancing system stability and performance, providing a more reliable user experience. -
Related PR: #3184
Contributor: @rinfx
Change Log: This PR added support for user-defined domain name configuration in the DouBao plugin, involving modifications to theMakefileand two Go files, allowing the service to communicate based on the new domain.
Feature Value: Allowing users to configure custom domain names for specific services enhances the system's flexibility and user experience, enabling users to adjust service access paths according to their needs. -
Related PR: #3175
Contributor: @wydream
Change Log: Added a new generic provider to handle requests for unmapped paths, utilizing shared headers andbasePathtool. Additionally, updated the README to include configuration details and introduced relevant tests.
Feature Value: By providing a vendor-agnostic generic provider, users can more flexibly handle various requests, enhancing the system's adaptability and maintainability. -
Related PR: #3173
Contributor: @EndlessSeeker
Change Log: This PR added a new global parameter to support inference scaling, involving updates to Helm templates and values files, enhancing system flexibility.
Feature Value: The new global parameter allows users to enable or disable the inference scaling feature, providing more configuration options to better meet the needs of different scenarios. -
Related PR: #3171
Contributor: @wilsonwu
Change Log: This PR added topology spread constraints support for the gateway and controller, implemented through new configuration items in Helm templates.
Feature Value: This new feature allows users to define more granular Pod distribution policies, enhancing the availability and stability of services within the cluster. -
Related PR: #3160
Contributor: @EndlessSeeker
Change Log: This PR upgraded the gateway API to the latest version, updated related dependencies, and modified some configuration files to adapt to new features.
Feature Value: By introducing the latest gateway API features, it enhances the system's compatibility and scalability, providing users with more advanced and secure network service functions. -
Related PR: #3136
Contributor: @Wangzy455
Change Log: Added a tool search server based on the Milvus vector database, achieving semantic matching by converting tool descriptions into vectors.
Feature Value: Users can now find the most relevant tools through natural language queries, enhancing the user experience and simplifying the tool search process. -
Related PR: #3075
Contributor: @rinfx
Change Log: This PR refactored the AI security guard plugin to support multimodal input detection and improved security for text and image generation scenarios. It also fixed some boundary case response anomalies.
Feature Value: By introducing multimodal input support and enhanced security detection capabilities, it improves the system's flexibility and security, providing users with more comprehensive content protection in different application scenarios. -
Related PR: #3066
Contributor: @EndlessSeeker
Change Log: Upgraded Istio to version 1.27.1, adjusted higress-core to adapt to the new Istio version, fixed submodule branch pull issues, and corrected integration tests.
Feature Value: This upgrade enhances system stability and compatibility, improves performance, and ensures compatibility with the latest Istio version, providing users with a better service experience. -
Related PR: #3063
Contributor: @rinfx
Change Log: Added the ability to perform cross-cluster and endpoint load balancing based on specific metrics such as concurrency, TTFT, and RT, allowing users to more flexibly configure load balancing strategies.
Feature Value: This feature allows users to choose the appropriate backend service based on custom performance metrics, thereby improving the overall response speed and service quality of the system, enhancing the user experience. -
Related PR: #3061
Contributor: @Jing-ze
Change Log: This PR fixed the implementation issues of theresponse-cacheplugin and added comprehensive unit tests, including cache key extraction logic, interface mismatch issues, and trailing whitespace corrections in configuration validation.
Feature Value: By optimizing the response cache plugin, users can more reliably use the caching feature, improving system performance and response speed while reducing unnecessary resource consumption. -
Related PR: #2825
Contributor: @CH3CHO
Change Log: Added thetraffic-editorplugin, allowing users to edit requests and responses. The plugin provides multiple operation types, including deletion, renaming, and updating, and has an extensible code structure.
Feature Value: This feature enhances the flexibility and functionality of the Higress gateway, allowing users to more freely control the content of HTTP requests and responses, meeting more personalized needs and enhancing the user experience.
-
Related PR: #3448
Contributor: @lexburner
Change Log: Fixed an out-of-bounds error in the Qwen API response handling due to an empty selection array. The fix adds a null check to avoid runtime errors.
Feature Value: This enhancement improves system stability and robustness, preventing service crashes due to abnormal API responses, and enhances the user experience. -
Related PR: #3434
Contributor: @johnlanni
Change Log: Fixed a YAML parsing error in the skill description by adding double quotes around values containing colons, ensuring they are treated as regular characters rather than YAML syntax.
Feature Value: This fix resolves rendering issues caused by special YAML characters, ensuring the skill page displays correctly and enhancing the user experience and document accuracy. -
Related PR: #3422
Contributor: @johnlanni
Change Log: Fixed an issue in themodel-routerplugin where themodelfield in the request body was not updated in auto-routing mode. The correct logic adjustment ensures the model field accurately reflects the routing decision.
Feature Value: This fix ensures that the model name received by downstream services is the value after the correct routing decision, not the defaulthigress/auto, enhancing system consistency and accuracy. -
Related PR: #3400
Contributor: @johnlanni
Change Log: Fixed a duplicate definition of theloadBalancerClassfield inservice.yamlby removing the redundant definition to avoid YAML parsing errors.
Feature Value: This fix resolves YAML parsing errors caused by duplicate fields, ensuring users can configureloadBalancerClasswithout encountering issues, enhancing system stability and the user experience. -
Related PR: #3380
Contributor: @Thomas-Eliot
Change Log: This PR added the setting of the request model context in the request handling function, ensuring that the request model data can be correctly accessed throughout the call chain.
Feature Value: This fix resolves the issue of the request model context not being set, allowing the system to correctly pass and use request model information, improving system stability and data consistency. -
Related PR: #3370
Contributor: @rinfx
Change Log: Fixed an issue in themodel-mappercomponent where the request body was still processed even if the suffix did not match, and added JSON validation for the body to ensure its validity.
Feature Value: This enhancement improves system stability and data processing accuracy, avoiding application anomalies due to invalid or incorrectly formatted request bodies, enhancing the user experience. -
Related PR: #3341
Contributor: @zth9
Change Log: This PR fixed an issue with concurrent SSE connections returning incorrect endpoints, by modifying themcp-sessionplugin configuration and filter logic to ensure that SSE server instances are correctly created for each filter.
Feature Value: This fix resolves endpoint errors that may occur in concurrent SSE connection scenarios, enhancing system stability and reliability, which is a significant improvement for applications relying on SSE for real-time communication. -
Related PR: #3258
Contributor: @johnlanni
Change Log: Fixed the MCP server version negotiation issue to comply with the specification. Updated dependencies to ensure compatibility and stability.
Feature Value: This fix enhances system stability and compatibility, ensuring that the MCP server can correctly negotiate versions with clients, improving the user experience and system reliability. -
Related PR: #3257
Contributor: @sjtuzbk
Change Log: This PR fixed the issue in theai-proxyplugin where thehostwas directly rewritten todifyApiUrlby using thenet/urlpackage to correctly extract the hostname.
Feature Value: After the fix, users can more accurately handle the hostname when configuringdifyApiUrl, avoiding connection issues due to incorrect rewriting, enhancing system stability and the user experience. -
Related PR: #3252
Contributor: @rinfx
Change Log: This PR fixed the error response issue in cross-provider load balancing by adding a penalty mechanism to prevent fast error responses from disrupting service selection and adjusting debug log information.
Feature Value: By improving error response handling and enhancing debugging capabilities, it improves system stability and reliability during load balancing, reducing the risk of service disruptions due to error responses. -
Related PR: #3251
Contributor: @rinfx
Change Log: This PR addressed the situation where content extracted from a specified jsonpath in the configuration is empty. When detecting empty content, it replaces the detected content with[empty content].
Feature Value: By introducing a special handling mechanism for empty content, it ensures that the system can operate normally even in the absence of data, enhancing system robustness and the user experience. -
Related PR: #3237
Contributor: @CH3CHO
Change Log: Increased the request body buffer size for multipart data in themodel-routerto support larger file uploads.
Feature Value: This enhancement improves the system's ability to handle large file uploads, reducing data truncation issues due to small buffers, and enhancing the user experience. -
Related PR: #3225
Contributor: @wydream
Change Log: Fixed the issue wherebasePathHandling: removePrefixdid not work correctly when using theprotocol: originalconfiguration. Adjusted the request header transformation logic in multiple providers to ensure the path prefix is correctly removed.
Feature Value: This fix resolves the path handling failure in specific configurations, ensuring that API calls to over 27 AI service providers work as expected, enhancing system stability and reliability. -
Related PR: #3220
Contributor: @Aias00
Change Log: This PR fixed two issues: 1. Skipping unhealthy or disabled Nacos services; 2. Ensuring theAllowToolsfield is serialized even if it is empty.
Feature Value: By skipping unhealthy or disabled services, it improves system stability and reliability. Additionally, ensuring consistent output of theAllowToolsfield avoids potential configuration issues due to missing fields. -
Related PR: #3211
Contributor: @CH3CHO
Change Log: This PR modified the logic in theai-proxyplugin for determining if a request contains a request body, changing from relying on specific header information to using the newHasRequestBodylogic.
Feature Value: By correcting the request body detection logic, it improves the accuracy and efficiency of handling HTTP requests, reducing misjudgment issues caused by the old logic. -
Related PR: #3187
Contributor: @CH3CHO
Change Log: This PR bypassed the handling of streamable response bodies in MCP to allow progress notifications, resolving the issue of not being able to correctly display progress during data transmission.
Feature Value: By bypassing the response body handling in specific situations, users can more accurately obtain progress information during data transmission, enhancing the user experience. -
Related PR: #3168
Contributor: @wydream
Change Log: Fixed an issue where the query string was incorrectly removed when processing paths with regular expressions. It strips the query string first, performs the match, and then reappends the query string.
Feature Value: This ensures that API requests with regular expression paths are correctly parsed and retain their original query parameters, enhancing system compatibility and the user experience. -
Related PR: #3167
Contributor: @EndlessSeeker
Change Log: Updated multiple submodule references to the latest version and simplified theMakefilecommands related to submodules, reducing redundant code.
Feature Value: By ensuring all submodules are up-to-date and synchronized, this fix improves project stability and maintainability, reducing potential compatibility issues. -
Related PR: #3148
Contributor: @rinfx
Change Log: Removed theomitemptytag from thetoolcall indexfield, ensuring that the default value 0 is correctly passed even if there is no index.
Feature Value: This fix resolves the issue of missingtoolcall indexin the response, ensuring data consistency and integrity, and enhancing system stability and the user experience. -
Related PR: #3022
Contributor: @lwpk110
Change Log: This PR resolved the issue of missing support forgateway.metrics.labelsin the Helm template by adding apodMonitorSelectorto the gateway metrics configuration and setting a default PodMonitor selector label to ensure seamless auto-discovery with the kube-prometheus-stack monitoring system.
Feature Value: This fix enhances Prometheus monitoring integration, allowing users to more flexibly configure and collect gateway metrics data, thereby improving system observability and management efficiency.
-
Related PR: #3462
Contributor: @johnlanni
Change Log: This PR removed the automatic injection of Bash tools in Claude Code mode, including deleting related constants, logic code, and test cases, and updating the documentation.
Feature Value: By removing unnecessary features, it simplifies the codebase and reduces maintenance costs. This change helps improve system stability and reduce potential sources of errors. -
Related PR: #3457
Contributor: @johnlanni
Change Log: This PR primarily updated the version number to 2.2.0, adjusted the Envoy submodule branch, and corrected the package URL pattern in theMakefile.
Feature Value: By updating the version and related configurations, it ensures the consistency and correctness of software builds, avoiding potential build errors due to version mismatches. -
Related PR: [#3155](https
This release includes 18 updates, covering enhancements, bug fixes, and performance optimizations.
- New Features: 7
- Bug Fixes: 10
- Documentation Updates: 1
-
Related PR: #621
Contributor: @Thomas-Eliot
Change Log: Enhanced some interaction capabilities of the MCP Server, including header host rewriting in direct routing scenarios, support for selecting transport, and support for special characters in the DB to MCP Server scenario.
Feature Value: Increased system flexibility and usability, allowing users to more easily customize MCP Server configurations, and resolved previous path confusion issues. -
Related PR: #612
Contributor: @zhwaaaaaa
Change Log: Added hop-to-hop headers to the ignore list, resolving the issue where Grafana pages could not work properly due to the reverse proxy sending thetransfer-encoding: chunkedheader.
Feature Value: Improved system compatibility and stability by adhering to RFC 2616, ensuring that Grafana monitoring pages display correctly when using a reverse proxy. -
Related PR: #608
Contributor: @Libres-coder
Change Log: Added support for displaying AI routing management page plugins, allowing users to view enabled plugins and their status through extended AI routing entries.
Feature Value: Enhanced user experience by allowing users to intuitively see which plugins are activated on the AI routing configuration interface, thus better managing and understanding the AI routing configuration. -
Related PR: #604
Contributor: @CH3CHO
Change Log: Introduced the use of thehigress.io/rewrite-targetannotation to support path rewriting based on regular expressions, involving modifications to the SDK server and frontend localization files.
Feature Value: The new path rewriting capability allows users to define URL routing rules more flexibly, enhancing system configurability and user experience. -
Related PR: #603
Contributor: @CH3CHO
Change Log: Displayed a fixed service port 80 for static service sources on the frontend page, implemented by adding a static constant in the component.
Feature Value: This feature allows users to clearly see the service port number used by static service sources, improving configuration transparency and user experience. -
Related PR: #602
Contributor: @CH3CHO
Change Log: Added support for service search functionality during AI routing configuration, optimizing the frontend interface to make it easier for users to find and select upstream services.
Feature Value: Enhanced user experience, especially when dealing with a large number of services, allowing users to quickly locate the required services, improving efficiency and ease of use. -
Related PR: #566
Contributor: @OuterCyrex
Change Log: Added support for custom Qwen services, including enabling internet search and file ID upload. The main changes were focused on the frontend interface and backend service processing logic.
Feature Value: Provided users with more flexible service configuration options, allowing them to customize Qwen service behavior according to their needs, enhancing system extensibility and user experience.
-
Related PR: #620
Contributor: @CH3CHO
Change Log: Fixed a spelling error in thesortWasmPluginMatchRuleslogic, ensuring that the rule matching function works as expected.
Feature Value: Resolved a potential misoperation issue, improving system stability and user experience. -
Related PR: #619
Contributor: @CH3CHO
Change Log: Removed version information from the data JSON when converting AiRoute to ConfigMap, as this information is already stored in the ConfigMap metadata.
Feature Value: By avoiding redundant storage of version information, reduced redundancy and ensured data consistency, thereby improving system reliability and maintainability. -
Related PR: #618
Contributor: @CH3CHO
Change Log: Refactored the API authentication logic in SystemController by introducing new annotations and modifying existing AOP aspects to eliminate security vulnerabilities.
Feature Value: Resolved security risks in API authentication, enhancing system security and protecting user data from potential threats. -
Related PR: #617
Contributor: @CH3CHO
Change Log: Fixed several errors in the frontend console, including missing unique key attributes for list items, image loading violations of the content security policy, and incorrect type for the Consumer.name field.
Feature Value: By addressing these frontend issues, improved user experience and application stability. Reducing console warnings and errors enhances user trust in the system and ensures the correct execution of functions. -
Related PR: #614
Contributor: @lc0138
Change Log: Corrected the type error in thetypefield of the ServiceSource class and added dictionary value validation to ensure data consistency.
Feature Value: By fixing the type error and introducing dictionary value validation, improved system stability and reliability, avoiding potential data inconsistency issues. -
Related PR: #613
Contributor: @lc0138
Change Log: This PR modified thedocument.tsxfile, adding 15 lines of code, primarily to fix security issues related to the frontend CSP, ensuring the application's security.
Feature Value: Fixed frontend CSP and other security risks, enhancing system security and protecting user data from potential threats, improving user experience and trust. -
Related PR: #611
Contributor: @qshuai
Change Log: Corrected a spelling error in an API title inLlmProvidersController.java, changing 'Add a new route' to a more appropriate description.
Feature Value: Correcting the API documentation title improves code readability and maintainability, ensuring developers can accurately understand each API's function, thus enhancing user experience. -
Related PR: #609
Contributor: @CH3CHO
Change Log: Fixed the type error in thenamefield of the Consumer interface, changing it from a boolean to a string.
Feature Value: Corrected the data type inconsistency in the Consumer.name field, ensuring data consistency and correctness, improving system stability and reliability. -
Related PR: #605
Contributor: @SaladDay
Change Log: Adjusted the regular expression validation rules for AI route names to support periods and unify case restrictions. Also updated the Chinese and English error messages to accurately reflect the new validation logic.
Feature Value: Resolved inconsistencies in route name validation, improving user experience and ensuring that user input conforms to expectations without causing confusion due to misleading prompts. -
Related PR: #552
Contributor: @lcfang
Change Log: This PR added avportattribute to adapt tomcpbridge, solving the issue of route configuration failure due to inconsistent backend service ports. Multiple files were changed, including the addition of the VPort class.
Feature Value: Resolved compatibility issues caused by changes in the service instance ports in the registry, enhancing system stability and user experience, ensuring that services run normally even when ports change.
- Related PR: #610
Contributor: @heimanba
Change Log: Adjusted the required fields for multiple fields in the frontend canary plugin configuration documentation and updated the associated rules to reflect the latest configuration flexibility. Also corrected some descriptive text to ensure document consistency and accuracy.
Feature Value: By increasing the flexibility and compatibility of configuration options, enhanced user experience, allowing users to configure canaries more flexibly; synchronized updates of Chinese and English documents also ensured accurate information dissemination.
- 🚀 New Features: 7
- 🐛 Bug Fixes: 10
- 📚 Documentation Updates: 1
Total: 18 changes
Thanks to all contributors for their hard work! 🎉
- @EndlessSeeker made their first contribution in https://github.com/alibaba/higress/pull/3066
- @YTGhost made their first contribution in https://github.com/alibaba/higress/pull/3200
- @Wangzy455 made their first contribution in https://github.com/alibaba/higress/pull/3136
- @maplecap made their first contribution in https://github.com/alibaba/higress/pull/3244
- @lwpk110 made their first contribution in https://github.com/alibaba/higress/pull/3022
- @wilsonwu made their first contribution in https://github.com/alibaba/higress/pull/3171
- @nixidexiangjiao made their first contribution in https://github.com/alibaba/higress/pull/3255
- @CZJCC made their first contribution in https://github.com/alibaba/higress/pull/3305
- @qshuai made their first contribution in https://github.com/alibaba/higress/pull/3241
- @zth9 made their first contribution in https://github.com/alibaba/higress/pull/3341
- @ThxCode-Chen made their first contribution in https://github.com/alibaba/higress/pull/3384
- @changsci made their first contribution in https://github.com/alibaba/higress/pull/3394
Full Changelog: https://github.com/alibaba/higress/compare/v2.1.9...v2.2.0
v2.1.10
This release includes 84 updates, covering various aspects such as feature enhancements, bug fixes, and performance optimizations.
- New Features: 46
- Bug Fixes: 18
- Refactoring and Optimization: 1
- Documentation Updates: 18
- Testing Improvements: 1
-
Related PR: #3438
Contributor: @johnlanni
Change Log: This PR significantly improves thehigress-clawdbot-integrationskill by adjusting the documentation structure, streamlining content, and adding support for the Clawdbot plugin.
Feature Value: This update allows users to configure plugins more smoothly and ensures true compatibility with Clawdbot, enhancing user experience and system flexibility. -
Related PR: #3437
Contributor: @johnlanni
Change Log: This PR integrates thehigress-ai-gatewayplugin into thehigress-clawdbot-integrationskill, including moving and packaging plugin files and updating the documentation.
Feature Value: This integration makes it easier for users to install and configure the connection between Higress AI Gateway and Clawbot/OpenClaw, simplifying the deployment process and enhancing user experience. -
Related PR: #3436
Contributor: @johnlanni
Change Log: This PR updates the SKILL provider list for Higress-OpenClaw integration and migrates the OpenClaw plugin package fromhigress-standaloneto the main higress repository.
Feature Value: By enhancing the provider list and migrating the plugin package, users can more easily access commonly used providers, improving integration efficiency and user experience. -
Related PR: #3428
Contributor: @johnlanni
Change Log: This PR adds two new skills to the Higress AI Gateway and Clawdbot integration: automatic model routing configuration and gateway deployment via CLI parameters. It supports multilingual trigger words and hot reloading of configurations.
Feature Value: The new features enable users to manage AI model traffic distribution more flexibly and simplify the integration process with Clawdbot, enhancing system availability and usability. -
Related PR: #3427
Contributor: @johnlanni
Change Log: Added theuse_default_attributesconfiguration option, which, when set totrue, automatically applies a set of default attributes, simplifying the user configuration process.
Feature Value: This feature makes theai-statisticsplugin easier to use, especially for common use cases, reducing manual configuration work while maintaining full configurability. -
Related PR: #3426
Contributor: @johnlanni
Change Log: Added the Agent Session Monitor skill, supporting real-time monitoring of Higress access logs and tracking multi-turn conversation session IDs and token usage.
Feature Value: By providing real-time visibility into LLMs in the Higress environment, this helps users better understand and optimize the performance and cost of their AI assistants. -
Related PR: #3424
Contributor: @johnlanni
Change Log: This PR adds support for token usage details to theai-statisticsplugin, including the built-in attribute keysreasoning_tokensandcached_tokens, to better track resource consumption during inference.
Feature Value: By introducing more detailed token usage logging, users can more clearly understand resource usage during AI inference, aiding in model efficiency and cost control. -
Related PR: #3420
Contributor: @johnlanni
Change Log: This PR adds session ID tracking to theai-statisticsplugin, allowing users to track multi-turn conversations through custom or default headers.
Feature Value: The added session ID tracking capability helps better analyze and understand multi-turn conversation flows, enhancing user experience and system traceability. -
Related PR: #3417
Contributor: @johnlanni
Change Log: This PR adds key warnings and guidelines to the Nginx to Higress migration tool, including explicit warnings for unsupported fragment annotations and pre-migration check commands.
Feature Value: By providing clear warnings about unsupported configurations and pre-migration check methods, this helps users identify potential issues and complete the migration from Nginx to Higress more smoothly. -
Related PR: #3411
Contributor: @johnlanni
Change Log: Added a comprehensive skill for migrating from ingress-nginx to Higress in a Kubernetes environment. Includes analysis scripts, migration test generators, and plugin skeleton generation tools.
Feature Value: This feature greatly simplifies the migration process from ingress-nginx to Higress by providing detailed compatibility analysis and automation tools, reducing migration difficulty and enhancing user experience. -
Related PR: #3409
Contributor: @johnlanni
Change Log: This PR adds thecontextCleanupCommandsconfiguration option to theai-proxyplugin, allowing users to define commands to clear conversation context. When a user message exactly matches a cleanup command, all non-system messages before that command will be removed.
Feature Value: This new feature allows users to proactively clear previous conversation records by sending specific commands, thereby better controlling conversation history and enhancing user experience and privacy. -
Related PR: #3404
Contributor: @johnlanni
Change Log: Added the ability for the Claude AI assistant to automatically generate Higress community governance daily reports, including auto-tracking GitHub activities, progress tracking, and knowledge consolidation.
Feature Value: This feature helps community managers better understand project dynamics and issue progress, promoting efficient problem resolution and enhancing overall community governance. -
Related PR: #3403
Contributor: @johnlanni
Change Log: Implemented a new automatic routing feature that dynamically selects the appropriate model to handle requests based on user message content and predefined regular expression rules.
Feature Value: This feature allows users to more flexibly configure services to automatically recognize and respond to different types of messages, reducing the need for manual model specification and enhancing system intelligence. -
Related PR: #3402
Contributor: @johnlanni
Change Log: Added the Claude skill for developing Higress WASM plugins using Go 1.24+. Includes reference documentation and local testing guidelines for HTTP clients, Redis clients, etc.
Feature Value: Provides developers with detailed guidance and example code, making it easier for them to create, modify, or debug WASM plugins based on the Higress gateway, enhancing development efficiency and experience. -
Related PR: #3394
Contributor: @changsci
Change Log: This PR extends the existing authentication mechanism by fetching API keys from request headers, particularly whenprovider.apiTokensis not configured, thus enhancing system flexibility.
Feature Value: This new feature allows users to more flexibly manage and pass API keys, ensuring normal service access even when direct configuration is missing, enhancing user experience and security. -
Related PR: #3384
Contributor: @ThxCode-Chen
Change Log: Added support for upstream IPv6 static addresses in thewatcher.gofile, involving 31 lines of new code and 9 lines of deletions, mainly focusing on handling service entry generation logic.
Feature Value: Adding support for IPv6 static addresses enhances system network flexibility and compatibility, allowing users to configure more types of network addresses, thereby enhancing user experience and service diversity. -
Related PR: #3375
Contributor: @wydream
Change Log: This PR adds Vertex Raw mode support to the Vertex AI Provider in theai-proxyplugin, enabling thegetAccessTokenmechanism when accessing native REST APIs via Vertex.
Feature Value: Enhances support for native Vertex AI APIs, allowing direct calls to third-party hosted model APIs and enjoying automatic OAuth authentication, enhancing development flexibility and security. -
Related PR: #3367
Contributor: @rinfx
Change Log: Updated the wasm-go dependency version and introduced Foreign Function, enabling Wasm plugins to perceive the Envoy host's log level in real time. By checking the log level upfront, unnecessary memory operations are avoided when there is a mismatch.
Feature Value: Enhances system performance, especially when handling large amounts of log data, reducing memory consumption and CPU usage, and improving response speed and resource utilization. -
Related PR: #3342
Contributor: @Aias00
Change Log: This PR implements the functionality of mapping Nacos instance weights to Istio WorkloadEntry weights in the watcher, using the math library for weight conversion.
Feature Value: This feature allows users to more flexibly control traffic distribution between services, enhancing system configurability and flexibility and improving integration with Istio. -
Related PR: #3335
Contributor: @wydream
Change Log: This PR adds image generation support to the Vertex AI Provider in theai-proxyplugin, achieving compatibility with OpenAI SDK and Vertex AI image generation.
Feature Value: The new image generation feature allows users to call Vertex AI services through standard OpenAI interfaces, simplifying cross-platform development and enhancing user experience. -
Related PR: #3324
Contributor: @wydream
Change Log: This PR adds OpenAI-compatible endpoint support to the Vertex AI Provider in theai-proxyplugin, enabling direct invocation of Vertex AI models.
Feature Value: By introducing OpenAI-compatible mode, developers can interact with Vertex AI using familiar OpenAI SDK and API formats, simplifying the integration process and enhancing development efficiency. -
Related PR: #3318
Contributor: @hanxiantao
Change Log: This PR applies the native Istio authentication logic to the debugging endpoint using thewithConditionalAuthmiddleware, while retaining the existing behavior based on theDebugAuthfeature flag.
Feature Value: Adds authentication support for debugging endpoints, enhancing system security and ensuring that only authorized users can access these critical debugging interfaces, protecting the system from unauthorized access. -
Related PR: #3317
Contributor: @rinfx
Change Log: Added two Wasm-Go plugins:model-mapperandmodel-router, implementing mapping and routing functions based on themodelparameter in the LLM protocol.
Feature Value: Enhances Higress's capabilities in handling large language models, allowing flexible configuration to optimize request paths and model usage, enhancing system flexibility and performance. -
Related PR: #3305
Contributor: @CZJCC
Change Log: Added Bearer Token authentication support for the AWS Bedrock provider, while retaining the existing AWS SigV4 authentication method and adjusting related configurations and header processing.
Feature Value: The new Bearer Token authentication method provides users with more flexibility, making it easier to choose the appropriate authentication mechanism when using AWS Bedrock services, enhancing user experience. -
Related PR: #3301
Contributor: @wydream
Change Log: This PR implements Express Mode support in the Vertex AI Provider of theai-proxyplugin, simplifying the authentication process for developers using Vertex AI, requiring only an API Key.
Feature Value: By introducing the Express Mode feature, users can start using Vertex AI more conveniently, without the need for complex Service Account configuration, enhancing developer efficiency and experience. -
Related PR: #3295
Contributor: @rinfx
Change Log: This PR adds MCP protocol support to theai-security-guardplugin, including implementing two response handling methods for content security checks and adding corresponding unit tests.
Feature Value: The new MCP support expands the plugin's application scope, allowing users to use the plugin for API call content security checks in more scenarios, enhancing system security. -
Related PR: #3267
Contributor: @erasernoob
Change Log: Added thehgctl agentmodule, including basic functionality implementation and integration with related services, and updatedgo.modandgo.sumfiles to support new dependencies.
Feature Value: By introducing thehgctl agentmodule, a new management and control method is provided to users, enhancing system flexibility and operability and improving user experience. -
Related PR: #3261
Contributor: @rinfx
Change Log: This PR adds the ability to disable thinking forgemini-2.5-flashandgemini-2.5-flash-liteand includes reasoning token information in the response, allowing users to better control AI behavior and understand its working details.
Feature Value: By allowing users to choose whether to enable the thinking feature and displaying reasoning token usage, system flexibility and transparency are enhanced, helping developers more effectively debug and optimize AI applications. -
Related PR: #3255
Contributor: @nixidexiangjiao
Change Log: Optimized the Lua-based minimum in-flight requests load balancing strategy, addressing issues such as abnormal node preference selection, inconsistent new node handling, and uneven sampling distribution.
Feature Value: Improves system stability and service availability, reduces the fault amplification effect caused by abnormal nodes, and enhances support for new nodes and even traffic distribution. -
Related PR: #3236
Contributor: @rinfx
Change Log: This PR adds support for the claude model invertexand handles the case wheredeltamight be empty, increasing system compatibility and stability.
Feature Value: Adding support for the claude model invertexallows users to leverage a wider range of AI models for development and research, enhancing system flexibility and practicality. -
Related PR: #3218
Contributor: @johnlanni
Change Log: Added an automatic rebuild trigger mechanism based on request count and memory usage, and expanded supported path suffixes, including/rerankand/messages.
Feature Value: These improvements enhance system stability and response speed, allowing effective handling of high loads or low memory situations through automatic rebuilding, while also enhancing support for new features. -
Related PR: #3213
Contributor: @rinfx
Change Log: This PR updates thevertex.gofile, changing the access method from region-specific to global, to support new models that only support global mode.
Feature Value: After adding support for the global region, users can more easily use new models like the gemini-3 series without specifying a specific geographic region. -
Related PR: #3206
Contributor: @rinfx
Change Log: This PR primarily adds support for security checks on prompt and image content in the request body, especially when using OpenAI and Qwen to generate images. Enhanced theparseOpenAIRequestfunction to parse image data and improved related processing logic.
Feature Value: The new security check feature enhances system security when handling image generation requests, helping to prevent the spread of potential malicious content and providing users with a safer and more reliable service experience. -
Related PR: #3200
Contributor: @YTGhost
Change Log: This PR adds support for array content in theai-proxyplugin by modifying the relevant logic in thebedrock.gofile, enabling correct handling whencontentis an array.
Feature Value: Enhances theai-proxyplugin's ability to handle messages, now correctly supporting and converting array-formatted content, making chat tool message transmission more flexible and diverse. -
Related PR: #3185
Contributor: @rinfx
Change Log: This PR adds a rebuild mechanism toai-cache, updatinggo.modandgo.sumfiles and making minor adjustments tomain.goto avoid excessive memory usage.
Feature Value: The newai-cacherebuild mechanism effectively manages memory usage, preventing system performance degradation due to high memory consumption, enhancing system stability and user experience. -
Related PR: #3184
Contributor: @rinfx
Change Log: This PR adds support for user-defined domain names in the Doubao extension, allowing users to configure service access domain names according to their needs. Main changes include adding compilation options in theMakefileand introducing new configuration items indoubao.goandprovider.go.
Feature Value: The new custom domain configuration feature allows users to flexibly set up external service domain names based on actual needs, enhancing system flexibility and user experience. This helps better adapt to the requirements of different deployment environments. -
Related PR: #3175
Contributor: @wydream
Change Log: Added a generic provider for handling requests that do not require path remapping, utilizing shared headers andbasePathtools. Also updated theREADMEfile to include configuration details and introduced relevant tests.
Feature Value: By adding this generic provider, users can more flexibly handle requests from different suppliers without needing to make complex path modifications, lowering the usage threshold and enhancing system compatibility. -
Related PR: #3173
Contributor: @EndlessSeeker
Change Log: This PR adds a global parameter to the Higress Controller for controlling the enablement of the inference scaling feature. Main changes are in thecontroller-deployment.yamlandvalues.yamlfiles, adding new configuration items and documenting them in theREADMEfile.
Feature Value: The new global parameter allows users to more flexibly control the inference scaling feature in the Higress Controller, which is very useful for users who need to adjust behavior based on specific circumstances, enhancing system configurability and adaptability. -
Related PR: #3171
Contributor: @wilsonwu
Change Log: This PR introduces support for topology distribution constraints for the gateway and controller, achieved by adding new fields in the relevant YAML configuration files.
Feature Value: The new support helps users better manage the distribution of pods within the cluster, optimizing resource usage and enhancing system high availability. -
Related PR: #3160
Contributor: @EndlessSeeker
Change Log: This PR upgrades the gateway API to the latest version, involving multiple modifications across several files, includingMakefileandgo.mod, to ensure compatibility with the latest API.
Feature Value: By introducing the latest gateway API support, users can enjoy more stable and feature-rich service mesh characteristics, enhancing system scalability and maintainability. -
Related PR: #3136
Contributor: @Wangzy455
Change Log: Added a tool semantic search function based on the Milvus vector database, allowing users to find the most relevant tools through natural language queries.
Feature Value: This feature enhances the system's search capabilities, enabling users to more accurately locate the required tools, enhancing user experience and work efficiency. -
Related PR: #3075
Contributor: @rinfx
Change Log: Refactored the code to modularize, supporting multimodal input detection and image generation security checks, and fixed response anomalies in boundary conditions.
Feature Value: Enhanced the AI Security Guard's ability to handle multimodal inputs, improving system robustness and user experience, ensuring the security of content generation. -
Related PR: #3066
Contributor: @EndlessSeeker
Change Log: Upgraded Istio to version 1.27.1 and adjustedhigress-coreto adapt to the new version, fixing submodule branch pulling and integration testing issues.
Feature Value: By upgrading Istio and related dependencies, system stability and performance are enhanced, solving problems in the old version and providing users with more reliable services. -
Related PR: #3063
Contributor: @rinfx
Change Log: Implemented cross-cluster and endpoint load balancing based on specified metrics, allowing users to select specific metrics for load balancing in the plugin configuration.
Feature Value: Enhances system flexibility and scalability, allowing users to optimize request distribution based on actual needs (e.g., concurrency, TTFT, RT), thereby enhancing overall service performance and response speed. -
Related PR: #3061
Contributor: @Jing-ze
Change Log: This PR resolves multiple issues in theresponse-cacheplugin and adds comprehensive unit tests. Improved cache key extraction logic, fixed interface mismatch errors, and cleaned up redundant spaces in configuration validation.
Feature Value: By enhancing the functionality and stability of theresponse-cacheplugin, system performance and user experience are improved. Now supports extracting keys from request headers/bodies and caching responses, reducing the processing time for repeated requests. -
Related PR: #2825
Contributor: @CH3CHO
Change Log: Added thetraffic-editorplugin, supporting request and response header editing, providing a more flexible code structure to meet different needs.
Feature Value: Users can use this plugin to perform various types of modifications to request/response headers, such as deletion, renaming, etc., enhancing system flexibility and configurability.
-
Related PR: #3434
Contributor: @johnlanni
Change Log: Fixed a YAML parsing error in the frontmatter section of the SKILL file by adding double quotes to the description value to avoid misinterpreting colons as YAML syntax.
Feature Value: Resolved rendering issues caused by YAML parsing, ensuring that the skill description is displayed correctly, enhancing user experience and document accuracy. -
Related PR: #3422
Contributor: @johnlanni
Change Log: Fixed an issue in themodel-routerplugin where themodelfield in the request body was not updated in the automatic routing mode. Ensured that themodelfield in the request body matches the routing decision after matching the target model.
Feature Value: Ensures that downstream services receive the correct model name, enhancing system consistency and accuracy, avoiding service anomalies or data processing deviations due to using the wrong model. -
Related PR: #3400
Contributor: @johnlanni
Change Log: This PR fixes the issue of duplicate definition of theloadBalancerClassfield in Helm templates, resolving YAML parsing errors by removing the redundant definition.
Feature Value: Fixed the YAML parsing error when configuringloadBalancerClass, ensuring a more stable and reliable service deployment process. -
Related PR: #3370
Contributor: @rinfx
Change Log: This PR fixes the issue of incorrect request body handling in themodel-mapperwhen the suffix does not match, and adds JSON validation for the body content to ensure its validity.
Feature Value: By resolving unexpected request handling issues and enhancing input validation, system stability and data processing security are improved, providing a more reliable service experience to users. -
Related PR: #3341
Contributor: @zth9
Change Log: Fixed the issue of concurrent SSE connections returning the wrong endpoint, ensuring the correctness of the SSE server instance by updating the configuration file and filter logic.
Feature Value: Resolved the concurrent SSE connection issue encountered by users, enhancing system stability and reliability, and improving user experience. -
Related PR: #3258
Contributor: @johnlanni
Change Log: This PR corrects the MCP server version negotiation mechanism to comply with the specification, including updating related dependency versions.
Feature Value: By ensuring that the MCP server version negotiation complies with the specification, system compatibility and stability are enhanced, reducing potential communication errors. -
Related PR: #3257
Contributor: @sjtuzbk
Change Log: This PR fixes the defect in theai-proxyplugin wheredifyApiUrlwas directly used as the host, by parsing the URL to correctly extract the hostname.
Feature Value: The fix enhances the plugin's stability and compatibility, ensuring that users can normally use the plugin when configuring custom API URLs, avoiding service interruptions due to incorrect handling. -
Related PR: #3252
Contributor: @rinfx
Change Log: This PR adjusts the debug log messages and adds a penalty mechanism for error responses, delaying the processing of error responses to avoid interfering with service selection during load balancing.
Feature Value: Enhances the stability and reliability of cross-provider load balancing by delaying error responses to optimize the service selection process, reducing service interruptions caused by quick error returns. -
Related PR: #3251
Contributor: @rinfx
Change Log: This PR handles the case where the content extracted from the configuration's JSONPath is empty by using[empty content]instead, ensuring that the program can continue to execute correctly.
Feature Value: This fix enhances system robustness, preventing potential errors or anomalies caused by empty content, thereby improving user experience and system reliability. -
Related PR: #3237
Contributor: @CH3CHO
Change Log: This PR increases the buffer size for the request body when handling multipart data, resolving the issue of a too small buffer in themodel-routerwhen processing multipart form data.
Feature Value: Increasing the buffer size for handling multipart data ensures stability in scenarios like large file uploads, enhancing user experience. -
Related PR: #3225
Contributor: @wydream
Change Log: Fixed the issue where thebasePathHandlingconfiguration did not work correctly when using theprotocol: originalsetting. This was resolved by adjusting the request header transformation logic for multiple providers.
Feature Value: Ensures that when using the original protocol, users can correctly remove the base path prefix, enhancing the consistency and reliability of API calls, affecting over 27 service providers. -
Related PR: #3220
Contributor: @Aias00
Change Log: Fixed the issue where unhealthy or disabled service instances were improperly registered in Nacos, and ensured that theAllowToolsfield is always present during serialization.
Feature Value: By skipping unhealthy or disabled services, system stability and reliability are improved; ensuring consistent presentation of theAllowToolsfield avoids potential configuration misunderstandings. -
Related PR: #3211
Contributor: @CH3CHO
Change Log: Updated the request body judgment logic in theai-proxyplugin, replacing the old method of determining whether a request body exists based oncontent-lengthandcontent-typewith the newHasRequestBodylogic.
Feature Value: This change resolves the issue of incorrectly judging the presence of a request body under specific conditions, enhancing the accuracy of service request handling and avoiding potential data processing errors. -
Related PR: #3187
Contributor: @CH3CHO
Change Log: This PR enables progress notifications by bypassing the handling of streamable response bodies in MCP. Specifically, it modified thefilter.gofile in the golang-filter plugin, involving small-scale adjustments to data encoding logic.
Feature Value: This change allows users to receive progress updates when using MCP for streaming, enhancing user experience and providing a more transparent data transmission process, especially useful for applications requiring real-time monitoring of transmission status. -
Related PR: #3168
Contributor: @wydream
Change Log: Fixed the issue of query string loss during the OpenAI capability rewrite process, ensuring that query parameters are stripped and re-appended to the original path during path matching.
Feature Value: Resolved the path matching issue caused by query string interference, ensuring the correctness and stability of services like video content endpoints. -
Related PR: #3167
Contributor: @EndlessSeeker
Change Log: This PR updates the references to multiple submodules and simplifies the command logic for submodule initialization and update in theMakefile, deleting 25 lines of code and adding 8 lines.
Feature Value: By fixing submodule update issues and simplifying related scripts, the build efficiency and stability of the project are improved, ensuring users can obtain the latest dependency library versions. -
Related PR: #3148
Contributor: @rinfx
Change Log: Removed theomitemptytag from thetoolcall indexfield, ensuring that the default value is 0 when the response does not contain an index, thus avoiding potential data loss issues.
Feature Value: This fix enhances system stability and data integrity, allowing users who rely on thetoolcall indexto more reliably handle related data, reducing errors due to missing indices. -
Related PR: #3022
Contributor: @lwpk110
Change Log: This PR fixes the issue of missingpodMonitorSelectorin the gateway metrics configuration, adding support forgateway.metrics.labelsin the PodMonitor template and setting a default selector label to ensure automatic discovery by the kube-prometheus-stack monitoring system.
Feature Value: By adding support for custom selectors and setting default values, users can more flexibly configure their monitoring metrics, enhancing system observability and maintainability.
- Related PR: #3155
Contributor: @github-actions[bot]
Change Log: This PR updates the CRD files in thehelmfolder, adding therouteTypefield and its enumeration value definitions.
Feature Value: By updating the CRD configuration, the flexibility and extensibility of the application are enhanced, allowing users to choose different route types as needed.
-
Related PR: #3442
Contributor: @johnlanni
Change Log: Updated thehigress-clawdbot-integrationskill documentation, removing theIMAGE_REPOenvironment variable and retainingPLUGIN_REGISTRYas the single source.
Feature Value: Simplified the user configuration process, reducing the complexity of environment variable settings, and enhancing document consistency and usability. -
Related PR: #3441
Contributor: @johnlanni
Change Log: Updated the skill documentation to reflect the new behavior of automatically selecting the best registry for container images and WASM plugins based on the timezone.
Feature Value: By automating timezone detection to select the best registry, the user configuration process is simplified, enhancing user experience and efficiency. -
Related PR: #3440
Contributor: @johnlanni
Change Log: This PR adds a troubleshooting guide for common errors during Higress AI Gateway API server deployment due to file descriptor limits.
Feature Value: By providing detailed troubleshooting information, users can quickly locate and fix service startup failures caused by system file descriptor limits, enhancing user experience. -
Related PR: #3439
Contributor: @johnlanni
Change Log: This PR adds a guide for choosing geographically closer container image registries in thehigress-clawdbot-integrationSKILL documentation, including a new section on image registry selection, an environment variable table, and examples.
Feature Value: By providing a method to choose the nearest container image registry based on geographical location, this feature helps users optimize the Higress deployment process, reduce network latency, and improve user experience. -
Related PR: #3433
Contributor: @johnlanni \
This release includes 18 updates, covering enhancements, bug fixes, and performance optimizations.
- New Features: 7 items
- Bug Fixes: 10 items
- Documentation Updates: 1 item
-
Related PR: #621
Contributor: @Thomas-Eliot
Change Log: This PR optimizes the interaction capabilities of the MCP Server, including rewriting the header host, modifying the interaction method to support transport selection, and handling special characters like @.
Feature Value: These improvements enhance the flexibility and compatibility of the MCP Server in various scenarios, making it easier for users to configure and use the MCP Server. -
Related PR: #612
Contributor: @zhwaaaaaa
Change Log: This PR adds ignore handling for hop-to-hop headers, particularly for thetransfer-encoding: chunkedheader. It also enhances code readability and maintainability by adding comments at key points.
Feature Value: This feature resolves the issue where the Grafana page fails to work due to specific HTTP headers sent by the reverse proxy server, improving system compatibility and user experience. -
Related PR: #608
Contributor: @Libres-coder
Change Log: This PR adds plugin display support to the AI route management page, allowing users to view enabled plugins and see the "Enabled" label on the configuration page.
Feature Value: This enhancement improves the functional consistency and user experience of the AI route management page, enabling users to more intuitively manage and view enabled plugins in the AI route. -
Related PR: #604
Contributor: @CH3CHO
Change Log: This PR introduces support for path rewriting using regular expressions, implemented through the newhigress.io/rewrite-targetannotation, with corresponding code and test updates in relevant files.
Feature Value: The new feature allows users to flexibly define path rewriting rules using regular expressions, significantly enhancing the flexibility and functionality of application routing configurations, making it easier for developers to customize request paths as needed. -
Related PR: #603
Contributor: @CH3CHO
Change Log: This PR adds a feature to display a fixed service port 80 in the static service source settings, achieved by defining a constant in the code and updating the form component.
Feature Value: Adding the display of a fixed service port 80 helps users better understand and configure static service sources, improving the user experience. -
Related PR: #602
Contributor: @CH3CHO
Change Log: This PR implements search functionality in the process of selecting upstream services on the AI route configuration page, enhancing the interactivity and usability of the user interface.
Feature Value: The added search function enables users to quickly and accurately find the required upstream services, greatly improving configuration efficiency and user experience. -
Related PR: #566
Contributor: @OuterCyrex
Change Log: Adds support for custom Qwen services, including enabling internet search and uploading file IDs.
Feature Value: This enhancement increases the flexibility and functionality of the system, allowing users to configure custom Qwen services to meet more personalized needs.
-
Related PR: #620
Contributor: @CH3CHO
Change Log: This PR fixes a spelling error in thesortWasmPluginMatchRuleslogic, ensuring the correctness and readability of the code.
Feature Value: By correcting the spelling error, the code quality is improved, reducing potential misunderstandings and maintenance costs, and enhancing the user experience. -
Related PR: #619
Contributor: @CH3CHO
Change Log: This PR removes version information from the data JSON when converting AiRoute to ConfigMap. This information is already stored in the ConfigMap metadata and does not need to be duplicated in the JSON.
Feature Value: Avoiding redundant information storage makes the data structure clearer and more reasonable, which helps improve the consistency and efficiency of configuration management, reducing potential data inconsistencies. -
Related PR: #618
Contributor: @CH3CHO
Change Log: Refactors the API authentication logic in the SystemController, eliminating security vulnerabilities. Adds theAllowAnonymousannotation and adjusts theApiStandardizationAspectclass to support the new authentication logic.
Feature Value: Fixes the security vulnerabilities in the SystemController, enhancing system security and protecting user data from unauthorized access. -
Related PR: #617
Contributor: @CH3CHO
Change Log: This PR fixes multiple errors in the front-end console, including missing unique key attributes for list items, issues with loading images that violate the content security policy, and incorrect type for theConsumer.namefield.
Feature Value: By resolving these front-end errors, the stability and user experience of the application are improved. This helps reduce issues encountered by developers during debugging and ensures the application runs as expected. -
Related PR: #614
Contributor: @lc0138
Change Log: Fixes an error in the type of thetypefield in theServiceSourceclass by adding dictionary value validation to ensure the correct type.
Feature Value: This fix improves the stability and data accuracy of the system, preventing service anomalies due to type mismatches and enhancing the user experience. -
Related PR: #613
Contributor: @lc0138
Change Log: This PR strengthens the content security policy (CSP) by modifying the front-end configuration, preventing cross-site scripting attacks and other security threats, ensuring the application is more secure and reliable.
Feature Value: Enhances the security of the front-end application, effectively defending against common web security attacks, protecting user data from unauthorized access or tampering, and improving user experience and trust. -
Related PR: #611
Contributor: @qshuai
Change Log: This PR fixes a spelling error in the controller API title in theLlmProvidersController.javafile, ensuring consistency between the documentation and the code.
Feature Value: Fixing the title spelling error improves the accuracy and readability of the API documentation, helping developers better understand and use the relevant interfaces. -
Related PR: #609
Contributor: @CH3CHO
Change Log: This PR corrects the type of thenamefield in theConsumerinterface from boolean to string, ensuring the accuracy of the type definition.
Feature Value: By fixing the type definition error, the code quality and maintainability are improved, reducing potential runtime errors and enhancing the developer experience. -
Related PR: #605
Contributor: @SaladDay
Change Log: Fixes the AI route name validation rules to support dot characters and unifies them to allow only lowercase letters. Also updates the error messages in both Chinese and English to accurately reflect the new validation logic.
Feature Value: Resolves the inconsistency between the UI prompt and backend validation logic, improving the consistency and accuracy of the user experience, ensuring users can correctly enter AI route names according to the latest rules. -
Related PR: #552
Contributor: @lcfang
Change Log: Adds thevportattribute to fix the issue of route configuration failure when the service instance port changes. By adding thevportattribute in the registry configuration, it ensures that changes to the backend service port do not affect the route.
Feature Value: Solves the compatibility issue caused by changes in the service instance port, enhancing the stability and user experience of the system, ensuring that services remain accessible even if the backend instance port changes.
- Related PR: #610
Contributor: @heimanba
Change Log: Updates the required and associated explanations for the document configuration fields, including changing therewritefields to optional and correcting some description texts.
Feature Value: By adjusting the field descriptions in the documentation, the configuration flexibility and compatibility are improved, helping users better understand and use the front-end canary plugin.
- 🚀 New Features: 7 items
- 🐛 Bug Fixes: 10 items
- 📚 Documentation Updates: 1 item
Total: 18 changes
Thank you to all contributors for their hard work! 🎉
- @EndlessSeeker made their first contribution in https://github.com/alibaba/higress/pull/3066
- @YTGhost made their first contribution in https://github.com/alibaba/higress/pull/3200
- @Wangzy455 made their first contribution in https://github.com/alibaba/higress/pull/3136
- @maplecap made their first contribution in https://github.com/alibaba/higress/pull/3244
- @lwpk110 made their first contribution in https://github.com/alibaba/higress/pull/3022
- @wilsonwu made their first contribution in https://github.com/alibaba/higress/pull/3171
- @nixidexiangjiao made their first contribution in https://github.com/alibaba/higress/pull/3255
- @CZJCC made their first contribution in https://github.com/alibaba/higress/pull/3305
- @qshuai made their first contribution in https://github.com/alibaba/higress/pull/3241
- @zth9 made their first contribution in https://github.com/alibaba/higress/pull/3341
- @ThxCode-Chen made their first contribution in https://github.com/alibaba/higress/pull/3384
- @changsci made their first contribution in https://github.com/alibaba/higress/pull/3394
Full Changelog: https://github.com/alibaba/higress/compare/v2.1.9...v2.2.0