@hunterowens tagging you because this steps the version down from what it was previously "published" as (I was trying to represent the MDS version, not the version of mds-provider). I don't know if this has implications for your usage of the library.
I want to tag releases using semver, so starting from the very beginning seemed logical. But I can always start at 0.2.0 if this presents a problem. I think in a system like npm (not sure about pypi) something like this -- releasing an earlier version than the "current" -- isn't allowed; but we aren't there yet with #26, and my processes won't care either way.
No issues from us, we have been using the master builds. The thought here is to decouple mds-provider (the python library) from mds_provider_implementation (the spec). I give this idea a 👍
Separate from the MDS version.
@hunterowens tagging you because this steps the version down from what it was previously "published" as (I was trying to represent the MDS version, not the version of
mds-provider
). I don't know if this has implications for your usage of the library.I want to tag releases using semver, so starting from the very beginning seemed logical. But I can always start at
0.2.0
if this presents a problem. I think in a system like npm (not sure about pypi) something like this -- releasing an earlier version than the "current" -- isn't allowed; but we aren't there yet with #26, and my processes won't care either way.