Specify minimum required task verison. #872
Labels
type: bug
Something not working as intended.
Comments
|
I came here looking for this feature as well. I have a workaround that works for my use case, but it's not the prettiest: # Specify your desired major version
version: 3
vars:
TASK_MINOR_VERSION:
# Store the current minor version of task in an environment variable
sh: echo "{{.TASK_VERSION}}" | awk -F. '{print $2}'
tasks:
default:
preconditions:
# Ensure we have at least version 3.28
- sh: 'test {{.TASK_MINOR_VERSION}} -ge 28' |
|
Note, that if you try this: version: 3.28You get this error: |
|
Is this a duplicate of #796 ? |
Merged
|
Since #796 is closed, I'd just like to note that this issue is still not fixed. |
|
wonderful, thank you @vmaerten ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While the
version:key is nice to specify the Taskfile schema version, it would be nice to have some option to define a minimum required task version to run a task.For example, a recent change introduced
.ROOT_DIR, which is incredibly handy for how I leverage task for my team, but many of my devs are stumbling over that as they haven't bothered to upgrade task yet.I propopse that in in taskfiles, the
version:key be expanded to check for minimum task version.Example:
would be compatible with all 3.x taskfile releases, but...
would cause
taskto exit non-zero if the task version isn't at least 3.15.2.The text was updated successfully, but these errors were encountered: