Script names differ in every frontend package
envgap__kestra-io__kestra-19210
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
581f26ea07af4550e210f55dddc97442390792e6- Manifest
ui/packages/design-system/package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
kestra-io/kestra #19210 · read the original issue
The same four jobs are spelled differently depending on which package you are in. `ui/` and `ui-ee/` use `test:unit`, `test:storybook`, `test:lint` and `check:types`. The design system and topology use `unit:test`, `storybook:test`, `lint:test` and `typecheck`, and `lint:fix` where the app packages say `lint`. Three more packages (slot-contracts, kestra-sdk, hey-api-plugin) only have `typecheck`. So the command that worked in the directory you just left is wrong in the next one, and CI has to know both spellings. The design system also carried two identical type-check scripts, `typecheck` and `types:test`. One convention, taken from the app packages since they are where most work happens. The design-system workflow in kestra-io/actions calls three of the old names, so it needs the matching change and the old names have to stay as aliases for one step, until that workflow is updated.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]