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 would be really appreciated if semantic version was followed in this repo. Both 0.4.5 and 0.4.6 included breaking changes and it is cumbersome to have to manually update this library and keep track of what it is doing instead of consuming what should have been non breaking changes.
The text was updated successfully, but these errors were encountered:
We are implementing the CBOREncodable Protocol so when a method is changed, like what happened in 0.4.5 and 0.4.6, our code is no longer able to compile.
Yes I realize the legal reason as to why you are keeping this at 0.x.x, but it would still be appreciated if some semblance of semantic versioning was followed to where incrementing the bug fix number is not a breaking change.
It would be really appreciated if semantic version was followed in this repo. Both 0.4.5 and 0.4.6 included breaking changes and it is cumbersome to have to manually update this library and keep track of what it is doing instead of consuming what should have been non breaking changes.
The text was updated successfully, but these errors were encountered: