chore: update release workflow #37
Merged
Conversation
This file contains hidden or 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
mhanberg
reviewed
Jul 30, 2025
mhanberg
reviewed
Jul 30, 2025
| @@ -0,0 +1 @@ | |||
| 0.1.0 | |||
Member
There was a problem hiding this comment.
Good call on this.
I think there might have to be something done to the release please config in order for it to bump this file.
Also, we probably don't need to set the release-type to elixir anymore, maybe we just need to set it to "simple", but I think that also might bump a "version.txt" file.
I use that method in elixir-tools.nvim here
Collaborator
Author
There was a problem hiding this comment.
Oh I think we can definitely follow that route and use the version.txt instead, it's the same idea
Collaborator
Author
There was a problem hiding this comment.
Noice, that works as expected
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.
We're running out of CI minutes in this org so I tested this workflow on a private org with no actions limits
This is largely based on NextLS release workflow: https://github.com/elixir-tools/next-ls/blob/main/.github/workflows/release.yaml