-
Present tag $MAJOR_VERSION (in this case: v1) pointing to the last released version. In that case all action consumers can stick to the v1 version, without needing to keep track of version changes wit…
-
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…
-
Hi there - We've been using ccxt as great solution to some of our trading operations. Thank you for all the effort!
Given fast releases and essential patches coming in continuously for exchange upd…
-
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.
-
https://mestrak.com/blog/semantic-release-with-python-poetry-github-actions-20nn
-
I would like to have a standardized way to generate changelog(s) and doing semantic versioning.
There are (attention: opinionated !) 2 concurrent solutions to discuss :
- use commitizen conform…