Recipes versioning #2

Open
opened 2026-03-15 14:02:53 +00:00 by lukas · 0 comments
Owner

The recipes might change over time.
Thus it makes sense to at least check the version which is specified in the .timber file.

Maybe it is required to keep multiple versions of the recipes.json file eventually. If so, how can we do this? Can we avoid storing the whole full recipes.json for every version?

The recipes might change over time. Thus it makes sense to at least check the version which is specified in the `.timber` file. Maybe it is required to keep multiple versions of the `recipes.json` file eventually. If so, how can we do this? Can we avoid storing the whole full `recipes.json` for every version?
lukas self-assigned this 2026-03-15 14:02:53 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lukas/timberborn_plots#2
No description provided.