I'm somewhat new to NR and working with open-source projects in general. I've created an open-source project, which I am sharing via Github.
It has occurred to me that if someone downloads a specific version, and I make updates later on which they then download, the new flows might reference SQLite tables and/or columns that they don't have, as it was added subsequent to the version they are updating their flows from.
What would be the correct way to handle schema changes between flow versions for production users?
A bit of research suggests that normally in software development, one would use database versioning, and then have scripts for each upgrade path to the latest version. Would that be the correct way to do it using NR as well? If so, can someone give me some pointers on how to achieve this in NR?