Inconsistent variable evaluation order in included taskfiles.

[WinkelCode]

Project structure:

$ tree
.
├── Taskfile.yml
├── Taskfile_A.yml
└── Taskfile_B.yml

$ cat Taskfile.yml
version: "3"

includes:
  TaskfileA:
    taskfile: "./Taskfile_A.yml"
  TaskfileB:
    taskfile: "./Taskfile_B.yml"

tasks:
  default:
    cmds:
      - "echo {{ .VAR2 }}"

$ cat Taskfile_A.yml 
version: "3"

vars:
  VAR1: "value1"

$ cat Taskfile_B.yml 
version: "3"

vars:
  VAR2: "{{ .VAR1 }} plus value2"

Demonstrating the issue

$ task
task: [default] echo value1 plus value2
value1 plus value2
$ task
task: [default] echo  plus value2
plus value2
$ task
task: [default] echo value1 plus value2
value1 plus value2

The order in which the variables of included Taskfiles are evaluated is non-deterministic. This poses a hard-to-debug problem in cases where a variable references one in a different Taskfile.

Expected behavior would be that the variables are evaluated in the order in which the Taskfiles are included.

Version

$ task --version
Task version: 3.41.0 ()

Operating system

macOS Sequoia 15.3.1

Experiments Enabled

None

---

Similar issue involving the dotenv functionality: #1847

[WinkelCode]

Effectively duplicate of this: #2046

Work to address issue is part of this: #2035