-
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…
-
https://mestrak.com/blog/semantic-release-with-python-poetry-github-actions-20nn
-
https://github.com/semantic-release/semantic-release
-
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…
-
Probably the current versioning style is already close to it, but I propose to stick more seriously to the succinct specification of [Semantic Versioning (semver) 2.0.0](https://semver.org/). This wil…
acsor updated
5 years ago
-
Inspired by #457, I discovered that the Releases in this repo don't show up in the Github API unless you name them. When I did so to the most recent one to figure this out, it said I did the releasin…
eah13 updated
9 years ago
-
most of composer packages use Semantic Versioning, such as 1.2.3, not 1.2.3.4
![image](https://user-images.githubusercontent.com/4971414/146498279-937a922e-4d40-41a0-8124-8d00a78a182f.png)
docs:…
-
Recently there was a lot of bugs between version 3.5.2 and 3.5.3.
My organisation was also hit due to that because some stuff started to explode at runtime:
```
io.getquill.quotation.QuatException:…
Matzz updated
3 years ago
-
Let's apply the semantic versioning for the new LRV dictionary.
I think I need to do something, but I don't know what!
@drdhaval2785 please advise.
-
Good standard: https://semver.org/