Phase 0.2: Rename tooling and config for v6 prefix
Part of the v6 migration (#3110). Tooling and config need updating so that pf-v6-* elements are recognized, and pf-v5-* exports are removed since the v6 release will not ship v5 elements.
Tasks
Notes
commitlint.config.js already normalizes scopes dynamically via regex (pf-(?:v\d+-)?), so no changes needed there
tsconfig, web-test-runner, and playwright configs don't appear to have hardcoded v5 globs currently, but should be verified as elements are ported
- This can be done incrementally as v6 elements land, or as a batch once enough elements exist
Related
Phase 0.2: Rename tooling and config for v6 prefix
Part of the v6 migration (#3110). Tooling and config need updating so that
pf-v6-*elements are recognized, andpf-v5-*exports are removed since the v6 release will not ship v5 elements.Tasks
eslint.config.jsignore globs — currently hardcoded topf-v5-icondemo path (line 16), needs to includepf-v6-icon(or generalize)elements/package.jsonexports — replace allpf-v5-*export entries with theirpf-v6-*equivalents. The v6 release will not contain pf-v5 elements, so these should be updated, not duplicatedtsconfigpaths for any v5-specific entriesweb-test-runner.config.jsandplaywright.config.tsglobs if neededcommitlint.config.jshandles both prefixes (currently stripspf-v\d+-dynamically — looks fine already)Notes
commitlint.config.jsalready normalizes scopes dynamically via regex (pf-(?:v\d+-)?), so no changes needed theretsconfig,web-test-runner, andplaywrightconfigs don't appear to have hardcoded v5 globs currently, but should be verified as elements are portedRelated
.claude/V6-MIGRATION-PLAN.md(Phase 0.2)