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
That would make it much easier for packages that depend on this one here to use semver compat bounds in Project.toml. The problem is that pre 1.0.0, every minor update is considered breaking, whereas starting with 1.0.0 one can use the full semver semantics, which make everything easier.
Also, it seems that this package is so widely used with the current API, that one might as well declare what we have as stable and done, right?
The text was updated successfully, but these errors were encountered:
Could we tag a version 1.0.0?
That would make it much easier for packages that depend on this one here to use semver compat bounds in Project.toml. The problem is that pre 1.0.0, every minor update is considered breaking, whereas starting with 1.0.0 one can use the full semver semantics, which make everything easier.
Also, it seems that this package is so widely used with the current API, that one might as well declare what we have as stable and done, right?
The text was updated successfully, but these errors were encountered: