Root --force flag not invalidating cache is subtasks defined in extended turbo.json configs inside other packages.

[ivancuric]

Summary

Workspace root:

turbo.json

{
  "$schema": "https://turbo.build/schema.json",
  "tasks": {
    "build": {
      "dependsOn": ["^build"],
      "outputs": ["dist/**", "types/**"],
      "outputLogs": "new-only"
    }
 }

package.json task:

"build": "turbo build"

Workspace package

turbo.json

{
  "$schema": "https://turbo.build/schema.json",
  "extends": ["//"],
  "tasks": {
    "build:wasm": {
      "inputs": ["scripts/build.mts", "binding/**/*.cpp", "binding/**/*.hpp"],
      "outputs": ["dist/**", "build/**", "!build/**/generators/**"],
      "env": ["DEV_PROJECT"],
      "dependsOn": ["configure"]
    },
    "generate:size-manifest": {
      "cache": false,
      "dependsOn": ["build:wasm"]
    },
    "build:types": {
      "inputs": ["src/**/*.ts", "tsconfig.json"],
      "outputs": ["types/**"]
    },
    "configure": {
      "inputs": [
        "scripts/configure.mts",
        "CMakeLists.txt",
        "binding/**/*.cmake"
      ],
      "env": ["DEV_PROJECT"],
      "outputLogs": "new-only",
      "outputs": ["build/**"]
    }
  }
}

package.json task:

 "build": "turbo run build:types build:wasm generate:size-manifest",

The idea is that I want to separately cache tasks in the package. So build:wasm, configure, build:types and generate:size-manifest, but I want to trigger the whole sequence by running the build task from the root package.

The problem appears when using the --force flag from the root package, like pnpm run build --force

All workspace packages get their caches invalidated, except for this one. Subtasks, such as build:wasm gladly report "replaying logs".

Is there a way to forward the --force flag to every subtask? Or is the catch that the turbo task name must match the name defined in the package.json?

Additional information

I'll add a short example ASAP

Example

No response