ci: automated releases and luarocks uploads #1923
Open
+33
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrcjkb
commented
May 13, 2024
| - uses: google-github-actions/release-please-action@v4 | ||
| with: | ||
| release-type: simple | ||
| token: ${{ secrets.PAT }} |
There was a problem hiding this comment.
This personal access token would need to be added to this repo's secrets.
mrcjkb
commented
Jun 19, 2024
|
@hrsh7th no interest in this? The luarocks package and latest tag being so out of date is a bit of a footgun for luarocks/rocks.nvim users. |
and this days also lazy.nvim |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey 👋
This PR introduces a release-please workflow that automatically opens (or updates) a release PR (which updates a changelog) when a conventional commit is merged into the
mainbranch.Here's an example of what a release PR looks like:
The nice thing about this workflow is that you get to decide when to merge a release PR.
When doing so, the same workflow creates a release tag and publishes a GitHub release, with the (SemVer) version bump determined from the conventional commit messages.
If you add a personal access token to this repo's secrets (I assumed it to be named
PATin this PR), each release will automatically trigger a luarocks upload. I have modified the workflow file to work nicely with this.Important
conventional commit messages. As there has not been a release yet,
it will likely start at version 1.0.0. You can change the initial version with a manifest file.
included in release notes. You could enforce this with a GitHub action. Personally, I haven't ever had a need to do so.