Schema versioning
b
bjorn@avo.sh
Currently development code can break if a branch with backwards incompatible changes is merged to main, because avo cli always pulls the latest main/branch code.
By introducing incremental schema versions we could stick to a certain Avo version in the clients and allow different development teams to catch up with analytics in their own pace.
Jeff Golden
Versioning would also help us detect if there have been changes since the last pull, allowing us to check more often and save processing time if Avo hasn't changed.
O
Oleg Polstianko
+1, I was always asking for Git like commits and versioning