Repository navigation
1.5.1-1
Release Notes
1. feat(RequestBodyFilter): Normalize Timezone Offsets for RFC 3339 Compliance
Commit: 13a91b0
Date: April 8, 2026
Summary:
The RequestBodyFilter now normalizes timezone offsets in the request body before OpenAPI validation. Java's java.util.Date serialization produces offsets without a colon separator (e.g., +0000, -0530), which are rejected by the date-time format validator. Offsets are now automatically converted to RFC 3339 form (e.g., +00:00, -05:30).
Changes:
- Added
TIMEZONE_OFFSET_PATTERNregex to match bare timezone offsets in date-time strings. - Added private
normalizeTimezoneOffset(String body)method that applies the replacement. - The normalized body is now passed to
ObjectMapperUtil.getObjectMapper().readTree()before validation.
Impact: Requests with date-time fields serialized by Java's default Date formatter will no longer fail OpenAPI schema validation due to missing colon in the timezone offset.
2. feat: Add Support to Disable CustomGatewayFilterCustomizer
Commit: 86689e0
Date: April 8, 2026
Summary:
CustomGatewayFilterCustomizer can now be conditionally disabled via a configuration property. Previously it was always active; it now respects api.registry.custom-gateway-filter.enabled=true and defaults to disabled (matchIfMissing = false).
Changes:
- Added
@ConditionalOnProperty(name = "api.registry.custom-gateway-filter.enabled", havingValue = "true", matchIfMissing = false)toCustomGatewayFilterCustomizer. - Extracted
RouteRefreshConfigintoGatewayConfigand cleaned up configuration classes. - Updated
ApiConfigand related tests accordingly. - Version bumps across pom.xml files.
Impact: Services that do not explicitly set api.registry.custom-gateway-filter.enabled=true will no longer load the CustomGatewayFilterCustomizer bean, reducing unintended side effects for consumers who don't use custom gateway filters.
Full Changelog: 1.5.1...1.5.1.1