feat: introduce a `compatible_since` field into `metadata` table
As well as the changelog between versions of the dmd
CLI in use, and the Slack community, it would be useful to indicate to consumers of the dmd
CLI, and the database it produces, what the minimum version of the tooling is compatible.
This could also improve the ability for automated tools to know if they're going to be able to work with a generated DB.
This would have interesting considerations:
- How should
dmd-web
report inconsistencies in versions? - How can a consumer understand the
compatible_since
? - Will this be a version constraint?
- What happens when a new feature is added that can't be used against the old DB? Does that indicate a bump?
- A breaking change will definitely indicate a bump
This will need to be source-tracked due to the need to allow for install-from-source.
Edited by Jamie Tanna