Is your feature request related to a problem? Please describe.
Yes. In our project, trigger.dev@4.4.6 currently resolves a CLI dependency path of c12@1.11.2 -> giget@1.2.5 -> tar@6.2.1, which triggers security alerts.
We need the resolved tar version to be at least 7.5.11.
Describe the solution you'd like to see
Please update the CLI dependency chain to use c12 >=3.3.4 (the first c12 version that uses giget ^3.2.0), or otherwise ensure the resolved tar version is >=7.5.11 in downstream installs.
Describe alternate solutions
N/A
Additional information
Current resolved path in our lockfile:
trigger.dev@4.4.6 -> c12@1.11.2 -> giget@1.2.5 -> tar@6.2.1
Version notes:
c12@3.3.3 still uses giget ^2.0.0c12@3.3.4 starts using giget ^3.2.0 (which moves to tar@7.x)
Is your feature request related to a problem? Please describe.
Yes. In our project,
trigger.dev@4.4.6currently resolves a CLI dependency path ofc12@1.11.2 -> giget@1.2.5 -> tar@6.2.1, which triggers security alerts.We need the resolved
tarversion to be at least7.5.11.Describe the solution you'd like to see
Please update the CLI dependency chain to use
c12 >=3.3.4(the first c12 version that usesgiget ^3.2.0), or otherwise ensure the resolved tar version is>=7.5.11in downstream installs.Describe alternate solutions
N/A
Additional information
Current resolved path in our lockfile:
trigger.dev@4.4.6 -> c12@1.11.2 -> giget@1.2.5 -> tar@6.2.1Version notes:
c12@3.3.3still usesgiget ^2.0.0c12@3.3.4starts usinggiget ^3.2.0(which moves totar@7.x)