Task variable level overrides no longer work in recent releases about task HOT 3 OPEN

This is relating to import/included tasks. Where are the default values defined? Variables specified at the inclusion have a fairly low priority:
https://taskfile.dev/usage/#variables

My own experiment show that this behavior is not working as expected. Global variables take precedence over variables defined at inclusion.

Taskfile

version: "3"
 
# should only be used if var not declared _anywhere_ else (BUG)
vars: 
  FOO: "FUBAR" 
 
includes:
  a:    
    taskfile: ./a/Taskfile.yml
    vars:
      FOO: "BAR"
  b:  
    taskfile: ./a/Taskfile.yml
    vars:
      FOO: "RAB"
      
tasks:
  one:
    cmds:
      - task a:two 
      - task b:two

a/Taskfile

version: "3"

# overrides variables defined on the inclusion of this Taskfile (OK)
#vars:
# FOO: "FOO"  

tasks:
  two:
    # overrides variables defined on the inclusion of this Taskfile (OK)
    #    vars:
    #      FOO: "BAR"
    cmds:
      - echo {{.FOO}}

$ ~/go/bin/task one
task: [one] task a:two
task: [a:two] echo FUBAR
FUBAR
task: [one] task b:two
task: [b:two] echo FUBAR
FUBAR

I don't think this is covered by the tests (global vars or environment vars). Seems like a bug. But is it the problem you observe?

from task.

Yes @trulede, you are correct. These are top-level variables that previously I was able to override at inclusion time. Now the global variables are taking precedence over the variables set at inclusion time.

This is definitely a bug/regression that has been introduced in the last several versions. Task is not honoring the precedence contract described in https://taskfile.dev/usage/#variables

from task.