More frequent releases? #1083
Comments
diraol
added a commit
to diraol/prezto
that referenced
this issue
Jun 3, 2024
Although it has tags, the release flow it is not well estabilished, so it fall behind quite recurrently, thus why I'm updating it aginst the master branch (it was already out of the latest tag anyway). Ref: zsh-users/zsh-completions#1083
indrajitr
pushed a commit
to sorin-ionescu/prezto
that referenced
this issue
Jun 3, 2024
Although it has tags, the release flow it is not well estabilished, so it fall behind quite recurrently, thus why I'm updating it aginst the master branch (it was already out of the latest tag anyway). Ref: zsh-users/zsh-completions#1083
prsquee
pushed a commit
to prsquee/prezto
that referenced
this issue
Jun 5, 2024
Although it has tags, the release flow it is not well estabilished, so it fall behind quite recurrently, thus why I'm updating it aginst the master branch (it was already out of the latest tag anyway). Ref: zsh-users/zsh-completions#1083
kharvd
pushed a commit
to kharvd/prezto
that referenced
this issue
Jun 16, 2024
Although it has tags, the release flow it is not well estabilished, so it fall behind quite recurrently, thus why I'm updating it aginst the master branch (it was already out of the latest tag anyway). Ref: zsh-users/zsh-completions#1083
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First of all, thank you for maintaining
zsh-completions! ❤️The repo is quite active with a few commits every other week, but releases are very infrequently.
Because most packages refer to the latest release and not to the latest commit, users of these packages are a fair bit behind users using plugin managers that just pull from master:
Therefore, I would suggest to release more frequently either manually (after a PR has been merged, and the last release is older than ~1 month) or automatically (e.g., using GitHub actions).
If you are interested in the automatic approach, I could give it a try and open a PR. 🙂
The text was updated successfully, but these errors were encountered: