Requires returns inconsistent results for dynamic variables depending upon whether or not enum is specified

[mmiddletonatua]

Description

Running the task as defined in the example results in the error:

task: Task "init_env" cancelled because it is missing required variables:
  - ENVIRONMENT has an invalid value : '' (allowed values : [dev stage prod])

Changing the requires section to:

    requires:
      vars: [ENVIRONMENT]

results in the expected behavior:
task: [init_env] echo ENVIRONMENT is dev
ENVIRONMENT is dev

This appears to be a regression as things previously behaved as expected.

Version

3.41.0

Operating system

Ubuntu 22.04.1

Experiments Enabled

No response

Example Taskfile

version: '3'

vars:
  ENVIRONMENT:
    sh: basename a/directory/named/dev

tasks:
  init_env:
    cmds:
      - echo ENVIRONMENT is {{.ENVIRONMENT}}

    requires:
      vars:
      - name: ENVIRONMENT
        enum: [dev, stage, prod]

[trulede]

@mmiddletonatua @vmaerten I think commit d64df3f broke this. The required check was moved to a location before a Task is compiled, and as a result, the sh command is not evaluated at the time of the require check. The code here

task/requires.go

Line 22 in 3aee0a0

value, isString := value.Value.(string)

has an empty string value, and the following check fails.

With version 3.40.0, your taskfile works.