Repository navigation
Add support for semantic versioning - #93
Conversation
|
No objections to this, but we should meet some time over jitsi so you can show me how to work this feature. the year of horror is coming to a close for me... |
|
fwiw this change makes elpaca complain about org-noter version:
This is because version-to-list craps out when supplied the version string prefixed with "v". I don't think it's an invalid format though, going from melpa's recipe format spec (https://github.com/melpa/melpa#recipe-format). Seems like their default regex deals with this. The error occurs because elpaca checks the version using elpaca--check-version with its own regex. They could fix the regex I guess. But from a quick grep seems like the prefix is quite uncommon in the package header, at least in the packages I have installed: |
Thank you, I updated the version in the latest master. |
Problem
We've been stuck on version 1.5.0 since last year.
Solution
Use svu to manage org-noter's semantic version along with a few Makefile changes.
Steps to Test
make bump-patchormake bump-minorto increment the appropriate version.git tag -l);;Versionheader inorg-noter.el.