-
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…
-
The BPX standard has semantic versioning (_major.minor.patch_), so the current version is `0.4.0`. However, the `["Header"]["BPX"]` field is constrained to `float` by the schema. `0.4.0` is not and ca…
-
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…
-
It would be better to switch to semantic versioning, where application version is controlled automatically via GitHub.
One point is missing on my side, though. The documentation clearly explains ho…
-
**What would you like to be added**:
The macOS Build has not a proper version for `CFBundleVersion` and `CFBundleShortVersionString` since the v5.0.2 release. Is there a chance to change it back li…
-
Hi can we move to 0.1.0-SNAPSHOT?
The git tag versioning doesn't seem to be the best way to do it.
Stu
-
https://semver.org/
Concerning going from version 5.0.x to 5.1.x....
If you make major changes in you code that is not backward compatible, please consider changing the major version.
-
Please consider assigning version numbers and tagging releases. Tags/releases
are useful for downstream package maintainers (in [Debian](http://debian.org) and other distributions) to export source ta…
-
Hello everyone (and a happy new year to all),
I have been using `python-semantic-release` for 2 months now, and I still encounter problems setting it up for my current work flow.
I have a python…