Skip to content

chore: deprecate @faustwp/block-editor-utils - #2643

Open
theodesp wants to merge 3 commits into
canaryfrom
deprecate/block-editor-utils
Open

theodesp wants to merge 3 commits into
canaryfrom
deprecate/block-editor-utils

Conversation

@theodesp

@theodesp theodesp commented Oct 9, 2026

Copy link
Copy Markdown
Member

Summary

  • Deprecates the @faustwp/block-editor-utils package per RFC RFC: Deprecate @faustwp/block-editor-utils #2640
  • Adds deprecation notices to the package README and docs page, pointing users to @wordpress/create-block and the archive/block-editor-utils branch
  • Removes the package from npm workspaces and build/test/format scripts (code remains in the repo)
  • Removes the block-b example that was the only consumer of the package
  • Fixes the showdown vulnerability by upgrading @wordpress/block-library to ^11.2.0 (which uses @wordpress/blocks@^16.2.0 that dropped showdown)
  • Upgrades @changesets/cli to ^3.0.3 and adds overrides for braces and js-yaml to reduce audit vulnerabilities from 92 → 46
  • Removes the block-support/package-lock.json which contained stale vulnerable transitive dependencies

Test plan

  • Verify npm audit no longer reports showdown vulnerabilities
  • Verify npm run build succeeds without block-editor-utils workspace
  • Verify the block-support example still works without block-b
  • Verify deprecation notice appears in the package README
  • Confirm the faustwp-getting-started example works with @wordpress/block-library@^11.2.0

Closes #2640

🤖 Generated with Claude Code

…bility

Deprecate the @faustwp/block-editor-utils package per RFC #2640.
The package code remains in the repo but is removed from the workspace
and marked as deprecated in its README and docs page.

- Remove block-editor-utils from npm workspaces and build/test/format scripts
- Add deprecation notices to package README and docs page
- Remove block-b example usage (only consumer of block-editor-utils)
- Remove @faustwp/block-editor-utils devDependency from block-support example
- Remove block-support/package-lock.json (contained showdown vulnerability)
- Upgrade @wordpress/block-library to ^11.2.0 (drops showdown dependency)
- Upgrade @changesets/cli to ^3.0.3 (fixes braces/sprintf-js vulnerabilities)
- Override braces to >=3.0.3 and js-yaml to >=5.4.3

Closes #2640

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@theodesp
theodesp requested review from a team, colinmurphy and josephfusco as code owners October 9, 2026 10:14
@theodesp

theodesp commented Oct 9, 2026

Copy link
Copy Markdown
Member Author

@copilot resolve the merge conflicts in this pull request

Copilot AI commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

@copilot resolve the merge conflicts in this pull request

I checked the repository’s default branch (canary): it is already an ancestor of this PR branch, so the branch is up to date and Git reports no merge conflicts. No merge commit was needed.

Keeps canary's js-yaml 4.3.2 override (GHSA-2883-xcg3-v3hh), its removal of
@changesets/cli and @next/bundle-analyzer, and its @babel/helpers bump.
Keeps this branch's @wordpress/block-library ^11.2.0 (drops showdown) and
its removal of block-editor-utils from the test scripts. Drops the braces
override, which pinned the version already installed.
@josephfusco

Copy link
Copy Markdown
Member

Resolved the merge conflicts with canary (the branch was 106 commits behind). Kept canary's js-yaml 4.3.2 override and its removal of changesets and the bundle analyzer, kept this branch's @wordpress/block-library ^11.2.0, and dropped the braces override, which pinned the version already installed. Also excluded block-editor-utils from ESLint, since it's no longer a workspace and lint failed once CI could run.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with resolving the merge conflicts, regenerating the lockfile, and verifying the build, tests, lint and audit.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RFC: Deprecate @faustwp/block-editor-utils

3 participants