Versioning

Per-Event-Type Versioning

Medallion versions each event type independently. The version is the final component of the event type name:

payer_enrollment.request.in_progress.v1
                                     ^^

Multiple versions of the same event type may be active simultaneously. You subscribe to specific versions and receive only those.

What Triggers a New Version

Change typeVersion bump?
Adding a new fieldNo
Removing a fieldYes
Renaming a fieldYes
Changing a field typeYes

Deprecation Policy

When a new version of an event type is introduced:

  1. The previous version continues to be delivered during the deprecation period
  2. Advance notice is provided before the old version is retired
  3. After retirement, the old version stops firing

Subscribe to new versions when they become available and migrate your handler before the deprecation deadline.


What’s Next