You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is currently totally opaque what is happening with this library between versions, including when it is safe to upgrade. Or even if the version numbers follow semantic versioning convention or are just randomly incrementing.
For example, I once used 2.0.6, what will change if I upgrade to 2.0.20? Any breaking changes? Any bugs fixed? Any new features I should consider?
Please do introduce release notes or change log of some kind.
As an addition it would be a welcome practice to tag releases in codebase should anyone need to compare specific issues and do have commits linked to issues they are related to.
The text was updated successfully, but these errors were encountered:
Totally valid point. Since there are usually few changes across versions, and they increment based on commit count, it should be fairly easy to compare, but the fact that I'm not exposing the commit info anywhere in the package makes it harder than it needs to be.
I'll add build metadata so you can at least compare one version's sha to another and get a commit list, which should be self-describing for the most part.
It is currently totally opaque what is happening with this library between versions, including when it is safe to upgrade. Or even if the version numbers follow semantic versioning convention or are just randomly incrementing.
For example, I once used 2.0.6, what will change if I upgrade to 2.0.20? Any breaking changes? Any bugs fixed? Any new features I should consider?
Please do introduce release notes or change log of some kind.
As an addition it would be a welcome practice to tag releases in codebase should anyone need to compare specific issues and do have commits linked to issues they are related to.
The text was updated successfully, but these errors were encountered: