zbirenbaum
SemVer support
I am using Lazyvim, and one of the recent major update changed a lot of things, breaking the distro.
It would be much better if we get versioning like copilot.vim, as we can know if an update has breaking change or not.
Thank you for your hard work always!
Fair 🙂 it's been on a long wishlist of mine to add versioning, I'll bump it up the list
In the past, I've created a Neovim plugin template. Following suggestions in https://github.com/nvim-neorocks/sample-luarocks-plugin , I've been using these two workflows:
- release-github: makes use of the action release-please. A separate branch ready to merge into main will be created and will accumulate changes and compute SemVer based on a commit with a conventional-commit message.
- release-luarocks: is triggered when a new tag is released (by the release-github action) and publishes the plugin to Luarocks (maybe there are some other files to add to publish on Luarocks).
I've tested this CD setup in several plugins development and I find it quite productive: it enforces SemVer without getting in the way (the repo owner decides when it's time to merge the release branch into main and create a new version).
I think that it's easier to add a new CI/CD workflow for the owner/maintainers (e.g., set up repo secrets), so I'm not opening a PR and just provide some references in this comment.
Thank you I will definitely look at your template, as for the secrets you are right, though I unfortunately cannot add them myself either (hence why tests are not currently working on this repo). Hopefully I won't need to add one for this 😂
@zbirenbaum, I will need your assist for this one as well, as it requires a PAT token to be configured: See action here
@zbirenbaum I do not mind putting my own creds in but I would need the security clearance 😉