Current dataset versioning requires knowing in advance which future minari version will support the current dataset.
With this PR we change the behavior, adding the Minari version that generated the dataset as metadata attribute and we list the supported dataset version in every Minari release.
Type of change
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist:
[x] I have run the pre-commit checks with pre-commit run --all-files (see CONTRIBUTING.md instructions to set it up)
[x] I have run pytest -v and no errors are present.
[x] I have made corresponding changes to the documentation
[x] I solved any possible warnings that pytest -v has generated that are related to my code to the best of my knowledge.
[x] New and existing unit tests pass locally with my changes
Description
Current dataset versioning requires knowing in advance which future minari version will support the current dataset. With this PR we change the behavior, adding the Minari version that generated the dataset as metadata attribute and we list the supported dataset version in every Minari release.
Type of change
Checklist:
pre-commitchecks withpre-commit run --all-files(seeCONTRIBUTING.mdinstructions to set it up)pytest -vand no errors are present.pytest -vhas generated that are related to my code to the best of my knowledge.