new GitHub release upon every new ingest

[arjunsavel]

t technically is a "new version" of the database once more data is added, but all the functionality is the same.

[arjunsavel]

suggestion from @kelle : N.yyyy.m, where N is the structure version and yyyy.m is for data updates

[arjunsavel]

@kelle is this something we want to automate? I could imagine the following workflow:

• user ingests new data
• user updates tests so that they pass with new data
• user pushes to github
• github action waits for tests to pass, then, if there's new data, automatically makes a release

thoughts? is this overengineered?

[kelle]

An action which automatically makes a new release when there's new data is not a terrible idea. It makes less work for us! I don't have enough experience to know if it's over-engineering. I'm not sure if that's industry standard or not? @dr-rodriguez ?