CloudEvents v1.0.2 refines the specification across Primer, Kafka binding, WebHook, and JSON format documents. Two changes affect implementations: the Webhook-Request-Origin header is renamed to Webhook-Allowed-Origin, and JSON serialization now explicitly defaults datacontenttype to application/json. The release also adds protobuf batch format support and clarifies rules for HTTP headers, Kafka partitioning, and data encoding.
breakingWebhook-Request-Origin renamed to Webhook-Allowed-Origin
The Webhook-Request-Origin header is renamed to Webhook-Allowed-Origin in v1.0.2. Applies if you implement or consume the WebHook validation handshake using the old header name.
breakingJSON datacontenttype explicit application/json default
When serializing CloudEvents to JSON, the datacontenttype field now explicitly defaults to application/json. Applies to all JSON serialization paths and clarifies the format specification in v1.0.2.
Key changes (7)
- Webhook-Request-Origin renamed to Webhook-Allowed-Origin (#836)
- JSON serialization now explicitly defaults datacontenttype to application/json (#881)
- Protobuf batch format added (#801)
- C# namespace option added to protobuf format (#937)
- Kafka binding clarifications: partitioning extension role, conflicting sentences removed (#727, #823, #813, #814)
- Repository reorganized; CloudEvents specs translated to Chinese; HTTP header encoding rules clarified (#904, #905, #899, #898, #793, #816)
- Sampled Rate Extension specification cleaned up; WebHook Origin header concept clarified against RFC 6454 (#832, #870)
A weekly email arrives when a release needs action. Like the breaking changes in this release.