You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current way the database version is checked breaks many kli invocations that are not expecting database migration errors. To reduce some of this confusion then when a new identifier is created with kli init then the database version, instead of being set to None, should be set to the current code version performing the kli init.
The text was updated successfully, but these errors were encountered:
Feature request description/rationale
The current way the database version is checked breaks many
kli
invocations that are not expecting database migration errors. To reduce some of this confusion then when a new identifier is created withkli init
then the database version, instead of being set toNone
, should be set to the current code version performing thekli init
.The text was updated successfully, but these errors were encountered: