Skip to content

chore: staging/pfv6 - #3134

Open
zeroedin wants to merge 79 commits into
mainfrom
staging/pfv6
Open

chore: staging/pfv6#3134
zeroedin wants to merge 79 commits into
mainfrom
staging/pfv6

Conversation

@zeroedin

@zeroedin zeroedin commented May 8, 2026

Copy link
Copy Markdown
Collaborator

What I did

Testing Instructions

Notes to Reviewers

@changeset-bot

changeset-bot Bot commented May 8, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: afd8d0a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@patternfly/elements Major
@patternfly/pfe-tools Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@netlify

netlify Bot commented May 8, 2026

Copy link
Copy Markdown

Deploy Preview for patternfly-elements ready!

Name Link
🔨 Latest commit 2da5be7
😎 Deploy Preview https://deploy-preview-3134--patternfly-elements.netlify.app/

To edit notification comments on pull requests, go to your Netlify site settings.

@github-actions github-actions Bot added the AT passed Automated testing has passed label May 8, 2026
@github-actions

github-actions Bot commented May 8, 2026

Copy link
Copy Markdown
Contributor

SSR Test Run for a4a106a: Report

* chore(tools): update tooling config for v6 prefix

- Generalize eslint ignore glob for icon demo path to match both
  pf-v5-icon and pf-v6-icon directories
- Update eslint no-missing-package-exports rule to match only pf-v6-*
  element directories
- Remove all pf-v5-* export entries from elements/package.json since
  v6 release will not ship v5 elements
- Bump elements package version to 6.0.0-next.0

Audited and confirmed no changes needed in:
- tsconfig files (no v5-specific paths)
- web-test-runner.config.js (generic globs)
- playwright.config.ts (generic globs)
- commitlint.config.js (already handles both prefixes dynamically)

Closes #3130

Assisted-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: custome-element.json output location

* chore: add settings.local.json to gitignore

* chore: remove extra cem config

* chore: revert package.json version

* chore: revert eslint config

* chore: remove no-missing-package-exports altogether

* chore: splat exports

* docs: delete migration plan

it's now in the issue body for epic #3110

* chore: update cem configs

* chore: update cem

---------

Co-authored-by: Benny Powers <web@bennypowers.com>
@github-actions

Copy link
Copy Markdown
Contributor

SSR Test Run for dd4ee41: Report

bennypowers and others added 2 commits May 11, 2026 20:33
Assisted-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
chore(deps): bump @pwrs/cem to 0.10.5
@github-actions

Copy link
Copy Markdown
Contributor

SSR Test Run for ea95c87: Report

* chore: remove v5 element after update

* docs: apply suggestion from @bennypowers

---------

Co-authored-by: Benny Powers <bennypowers@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

SSR Test Run for d19c3ec: Report

@github-actions

Copy link
Copy Markdown
Contributor

SSR Test Run for 3380d11: Report

@github-actions

Copy link
Copy Markdown
Contributor

SSR Test Run for 2a2e7a2: Report

bennypowers and others added 3 commits May 14, 2026 15:55
Add Phase 8 (README) to create-element and update-element skills,
instructing agents to produce a divergences-from-React document for
each element. Three tables: not implemented, changed API, and added.
Includes accuracy rules to prevent false claims about shadow DOM.

References elements/pf-v6-tooltip/README.md as example.

Assisted-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
docs(create-element): add README phase to element skills
@github-actions

Copy link
Copy Markdown
Contributor

SSR Test Run for 8156a2c: Report

@zeroedin zeroedin changed the title staging: pfv6 feat: staging/pfv6 May 14, 2026
@zeroedin zeroedin changed the title feat: staging/pfv6 chore: staging/pfv6 May 14, 2026

@zeroedin zeroedin left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pf-tokens.css CSS rules are loaded in the cem serve ui chroming. Visual testing needs to be done with ?rendering=chromeless, as this query param removes the pf-tokens.css present in the full Chrome UI. Because these are ultimately the same tokens, even though loaded for CEM UI and not for pf6 development, they overlap and leak in. However, components should be more fault-tolerant and include the styles they need to look the way we want independently of that file's existence through failovers and setting font rules necessary per component.

@github-actions

Copy link
Copy Markdown
Contributor

SSR Test Run for 2da5be7: Report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AT passed Automated testing has passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants