Benjamin LuandGitHub b71d714485 Treat missing requirements as upgrade instead of error (#1429) ...

## Summary
- in `hasRequirements`, treat missing/changed known packages as
`package-upgrade` instead of `error`
- add/adjust unit tests for `hasRequirements` to reflect the upgrade
flow behavior (missing packages => package-upgrade, not maintenance)

## Context
During validation, a dry-run detected older
comfyui-workflow-templates/comfyui-embedded-docs and returned
`pythonPackages: error`, sending users to maintenance. The dry-run
output matched the known upgrade path, so it should trigger the package
upgrade flow, not a fatal error.

## Testing
- Unit tests updated for `hasRequirements` (tsc/lint via lint-staged)

2025-11-22 15:35:15 -08:00

..

troubleshooting.spec.ts-snapshots

Update integration tests for v0.5 compatibility (#1369)

2025-10-09 05:29:25 -07:00

troubleshootingServerStart.spec.ts-snapshots

Revert yarn/node migration attempt (#1422)

2025-11-22 07:32:15 -08:00

troubleshootingVenv.spec.ts-snapshots

Update integration tests for v0.5 compatibility (#1369)

2025-10-09 05:29:25 -07:00

troubleshooting.spec.ts

Update integration tests for v0.5 compatibility (#1369)

2025-10-09 05:29:25 -07:00

troubleshootingServerStart.spec.ts

Fix intermittent CI failures - race against app launch (#1337)

2025-09-23 23:52:19 -07:00

troubleshootingVenv.spec.ts

Treat missing requirements as upgrade instead of error (#1429)

2025-11-22 15:35:15 -08:00