Skip to main content

Changelog

All notable changes to the Tenant Configuration Schema are documented here.

Release 1.12.0 (2026-05-08)​

info

This release introduces list references — named lists of values that can be defined once and referenced across match conditions using {"{{list.<key>}}"} syntax. Lists can be defined locally in a tenant config or shared across tenants via a common config file.

Release Highlights​

Top-Level Configuration:

  • Lists - New lists property for defining named value lists referenced in match rules via {"{{list.<key>}}"}

Match Conditions:

  • List References - All match conditions now accept {"{{list.<key>}}"} references as standalone values, in mixed arrays, and in header/query objects

Common Configuration:

Schema Changes:

  • Added lists top-level property with string array values
  • Added {"{{list.<key>}}"} pattern as a valid match value across all match conditions
  • Added shared schema definitions (match_value_string, match_value_paths, match_value_header)
  • Refactored match condition value schemas to $ref references (no user-facing behavior change)

📖 View Full Release Details​

For complete documentation including examples and migration guides, see the Release 1.12.0 Details page.

Release 1.11.0 (2026-02-09)​

info

This release adds new response match conditions for origin timeout detection and status code matching, introduces respondWith support in the onClientResponse event handler, deprecates the http2 and http3 features, adds geographic match conditions (continent, region, city), and introduces GRN interpolation support.

Release Highlights​

New Match Conditions:

  • Origin Timeout - New response match condition to detect and handle origin connection timeouts with origin_timeout and !origin_timeout
  • Response Status Code - New response match condition to match on HTTP status codes with status and !status (supports integers, ranges, and classes)
  • Geographic Match Conditions - Added continent, region, and city match conditions (with geo_* aliases) for granular location-based routing

Delivery Configuration:

Deprecations:

  • http2 and http3 - Transport protocol features deprecated; managed at platform level

Schema Changes:

  • Added origin_timeout, !origin_timeout, status, and !status to match_condition_response
  • Added respondWith feature to onClientResponse event handler
  • Added continent, region, and city geographic match conditions with geo_* aliases
  • Added {{grn}} interpolation variable
  • Deprecated http2 and http3 features

📖 View Full Release Details​

For complete documentation including examples and migration guides, see the Release 1.11.0 Details page.

Release 1.10.3 (2025-12-16)​

info

This release introduces significant enhancements including 15+ new delivery features, enhanced security capabilities, 28 new configuration examples, and comprehensive documentation updates.

This release requires a new delivery configuration (v1.10.3) to take advantage of the latest features.

Release Highlights​

Delivery Configuration Features:

  • HTTP Method Control - Control allowed HTTP methods (POST, PUT, DELETE, PATCH) with rule-based conditions
  • Downstream Caching - Configure client-side cache control policies with flexible behaviors
  • HSTS - HTTP Strict Transport Security headers for enforcing secure connections
  • Origin Timeouts - Configure timeout values (read, first byte, connect) for origin connections
  • Transport Protocols - Enable HTTP/2, HTTP/3, and WebSocket support
  • Header Management - Enhanced header handling with removal support using null values
  • Additional Features - Tiered distribution, origin IP ACL, breadcrumbs, and compression enhancements

Security Configuration Features:

Top-Level Configuration:

  • Tenant ID - New tenant_id property for improved tenant identification in logging

Schema Changes:

  • Added null type support for header removal
  • Increased field length constraints (200 → 500 chars for generic fields, up to 1000 for headers)
  • Enhanced ASN exception support
  • 15+ new configuration options

Deprecations:

  • tenantTag feature deprecated in favor of top-level tenant_id (still functional)

📖 View Full Release Details​

For complete documentation including examples, migration guides, and detailed feature descriptions, see the Release 1.10.3 Details page.

Resources​

note

Questions or feedback? Please refer to the documentation or contact support.