-
-
For now, least important of the milestone 02 issues. A standard semantic versioning system consists of 3 numbers - for instance, 1.2.3. The first number represents API changes that render it incompati…
-
i have to ignore this package from automatic updates because it doesn't use semver, so if you are going to update it I'd appreciate if you stuck to the same scheme that every other package in the enti…
tubbo updated
2 years ago
-
This repo does not follow semantic versioning and has not published a release in a significant amount of time. This makes it impossible for external consumers to reliably depend on this project.
P…
-
> Decide on API Versioning
>
> Decision Tree
>
> Versioning of resource or suite?
>
> How/where do we version (path, header,...)?`
>
> Which kind of header versioning
>
> HTTP version (…
-
Currently, we state that versions take the form "vX.Y" in the header, but then we have hotfix versions of the form "v1.0a", which does not conform to [semantic versioning](http://semver.org/spec/v2.0.…
buske updated
7 years ago
-
rmuch updated
3 years ago
-
Potentially need to add semver versioning to allow us to use keepachangelog.
Unblocks: #2
-
Thanks for your hard work!
Just wondering if there is any plans to add releases and/or semantic versioning (including CHANGELOG) to this project. These would be really useful, as they'd let others …
-
I've noticed that new tests are often released as part of patch (a.b.X) releases and are enabled by default. For instance, the dev version of Phan 1.1.1 already has 9 new tests and that version hasn't…