Versioning
All content in EventCatalog can be versioned. This allows you to keep historic versions of content which can give context to users why things are changing.
How to version a flow
- Create a
/versioneddirectory inside the/flowsfolder if one is not created already. - Create a new folder with the version number inside the folder.
- Example:
/flows/ProcessingPayments/versioned/0.0.1
- Example:
- Copy contents into the new folder, it at least needs your index.mdx file.
- Example:
/flows/ProcessingPayments/versioned/0.0.1/index.mdx - Note: the version inside this index.mdx file would be
0.0.1
- Example:
- Bump the version of the
index.mdxfile in the route of the domain.- Example
/flows/ProcessingPayments/index.mdx, change theversionto0.0.2
- Example
How to navigate to versions
EventCatalog will automatically create links for you within your latest version of your document. Users will also be able to navigate to any version by adding the version in the url (e.g /docs/flows/ProcessingPayments/1.0.2 would load the 1.0.2 version of this flow).