Description
I don't believe this is a feature yet, apologies if I missed it.
What I'm looking for is a way to avoid manually changing the pin myself each time a plugin cuts a new official release. Instead, I would like to use a key in my zsh_plugins.txt file so that antidote only updates a plugin if the repo has an official release. Then it should update to the commit of that release. Maybe the key would be release-only:true or something like that?
Using mattmc3/antidote as an example, it would be auto-pinned to the latest release (2.3.0, hash 9bb69ab). The previous auto-pin would've been 2.2.2, hash 4c02192. So on and so forth.
edit: I have discussed this in more depth in #261, which seems a better home for it.
Description
I don't believe this is a feature yet, apologies if I missed it.
What I'm looking for is a way to avoid manually changing the pin myself each time a plugin cuts a new official release. Instead, I would like to use a key in my zsh_plugins.txt file so that antidote only updates a plugin if the repo has an official release. Then it should update to the commit of that release. Maybe the key would be
release-only:trueor something like that?Using mattmc3/antidote as an example, it would be auto-pinned to the latest release (2.3.0, hash 9bb69ab). The previous auto-pin would've been 2.2.2, hash 4c02192. So on and so forth.
edit: I have discussed this in more depth in #261, which seems a better home for it.