mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-07-18 17:58:23 +00:00
## Summary Bump core dev toolchain (Vue/Vite/Oxlint/Oxfmt/ESLint/pnpm + ecosystem) to latest same-major versions, with the small compat fixes the new versions require. ## Changes - **What**: Catalog bumps in `pnpm-workspace.yaml`: vue 3.5.39, vite 8.1.4, oxlint 1.74, oxfmt 0.59, eslint 10.7, vitest 4.1.10, vue-tsc 3.3.7, tailwindcss 4.3.2, @playwright/test 1.61.1, storybook 10.5.0, knip 6.27, typescript-eslint 8.64, @vueuse 14.3 + assorted ecosystem minors. `packageManager` pnpm 11.3.0 → 11.13.1. - **Compat fixes**: - `defineModel` default-factory param typing in `WidgetSelectDefault.vue`/`WidgetSelectDropdown.vue` (vue 3.5.40+ types it as `Record<string, unknown>`) - `useClipboard` mock in `useCopyToClipboard.test.ts` (vueuse 14.3: `ComputedRef` fields + new `copyPending`) - Removed two knip ignores obsoleted by knip 6.27 (config treats hints as errors) - Renamed invalid CSS ident `--color-dark-elevation-1.5` → `-1-5` (dot is not a valid ident char; unused; oxfmt 0.59 hard-errors on it) - oxfmt 0.59 reformat as a separate commit (small churn, 8 files) - **Held back**: happy-dom pinned at 20.9.0 — 20.10.x throws sync `NotSupportedError` on external `<script>` append, breaking GTM/Typeform loader tests. Majors deferred to individual PRs: typescript 7, pinia 4, vue-router 5, vue-i18n 11, stylelint 17, jsdom 29, globals 17, unplugin-* majors, vite-plugin-dts 5, @types/node 25. - **Dependencies**: version bumps only, no new packages. no `minimumReleaseAgeExclude` exemptions — range floors sit at the newest age-compliant releases (vue 3.5.40, vite 8.1.5, tailwind 4.3.3, storybook 10.5.2 are <24h old and flow in automatically once they pass the gate). ## Review Focus - Unit suite failures match main exactly (previewAny/uploadAudio pre-existing flakes); typecheck, lint, knip, build all green. Desktop-ui typecheck failures are identical on main (pre-existing, untouched). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
GitHub Workflows
Naming Convention
Workflow files follow a consistent naming pattern: <prefix>-<descriptive-name>.yaml
Category Prefixes
| Prefix | Purpose | Example |
|---|---|---|
ci- |
Testing, linting, validation | ci-tests-e2e.yaml |
release- |
Version management, publishing | release-version-bump.yaml |
pr- |
PR automation (triggered by labels) | pr-claude-review.yaml |
api- |
External Api type generation | api-update-registry-api-types.yaml |
i18n- |
Internationalization updates | i18n-update-core.yaml |
Documentation
Each workflow file contains comments explaining its purpose, triggers, and behavior. For specific details about what each workflow does, refer to the comments at the top of each .yaml file.
For GitHub Actions documentation, see Events that trigger workflows.