Closed st-- closed 2 years ago
@tpapp would be great if you could merge this & register a new release!
Apologies, I missed the first notification. Thanks for the PR and the friendly bump. Will merge and release now.
I have to update some dependencies too, will finish this when things propagate through the registry, hopefully soon. Thanks for your patience.
Thanks! Just so I understand correctly, you are not following the ColPracs then? They seemed to advocate that for version>=1 each feature should lead up a minor version bump (patch bump exclusively for bugfixes) and compatibility with a new different version of another package counts is explicitly counted as a new feature the.
The other again I had is what does the ^ before the 0.9 add?
IMO supporting another version of a dependency is not a feature addition in the API this package exposes. I never understood the reasoning behind that recommendation, but that said I am open to suggestions (and reading up on stuff if there is a discussion I did not follow).
The ^
is upward-compatibility, a no-op in this case since it is the default, just so that I could make change and trigger CI.
I agree that I would have tended to what you're saying, but e.g. the SciML ColPrac are very explicit about this... And SemVer also specifies that patch version for >1 is only for bugfixes. Might it be worth opening an issue on the ColPrac repo asking for clarification ?
Otherwise our downstream code keeps getting CompatHelper PRs re LogDensityProblems, but we can't actually check that it works as DynamicHMC keeps back the version.