Dependency trace: test-exclude -> glob@7 -> inflight remains in Jest transform chain

Summary - We upgraded promotion-worker to Jest 30 and migrated from ts-jest to @swc/jest. - Tests pass locally, but glob@7 and inflight remain pulled into projects via Jest internals. Dependency trace (from npm ls) @jest/transform -> babel-plugin-istanbul -> test-exclude -> glob@7.2.3 -> inflight@1.0.6 Local validation - npm ci --ignore-scripts (success) - npm test --silent (12/12 passing) - npm ls inflight glob (shows trace above) Why this matters - glob@7 and inflight are deprecated and produce supply-chain warnings in downstream projects. - Projects upgrading to Jest 30 still surface these deprecation warnings because they are inside the transform stack. Request - Can the Jest transform chain be updated to avoid glob@7 (for example, by updating test-exclude or replacing the dependency with a maintained alternative)? - If there is a recommended mitigation (e.g., supported overrides or a timeline for a fix), please share it. Repro 1. Create a minimal repo using jest@30 and run npm ls glob inflight 2. Observe the trace above Links - https://github.com/DIRTYBOXING/Data-Fight-Central/pull/35 - https://github.com/DIRTYBOXING/Data-Fight-Central/pull/36