Skip to content

Commit 90506c0

Browse files
committed
removing info about what happened prior to event versioning
1 parent 3e08576 commit 90506c0

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

src/protocols/tracking-plan/create.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -192,8 +192,6 @@ For example, say you want to add `subtotal` as a required property to your `Orde
192192

193193
![Two screenshots edited together. The first screenshot shows all the properties in an Order Completed event with none highlighted, and the second screenshot shows the subtotal property selected.](../images/breaking_change_event_versioning.png)
194194

195-
Before Segment introduced event versioning, you would need to add the change to your Tracking Plan and any non-compliant events would generate violations, and possibly be blocked depending on your [event blocking settings](/docs/protocols/enforce/schema-configuration/).
196-
197195
### Create a new event version
198196
With event versioning, you can now create multiple versions of the event definition as shown in the example below. To create a new event version, click into the overflow menu for an event and select **Add Event Version**.
199197

0 commit comments

Comments
 (0)