Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Visual/config alignment with the new main site: - Title/url -> headstartwp.fueled.com; GA4 (production-only) replaces GTM - Navbar 'About HeadstartWP' CTA; hero lavender wash + lattice treatment - Footer: 3 nav columns + Fueled bottom band mirroring the main site - IBM Plex Sans / Plex Sans Condensed typography, new primary ramp Brand reference pass: - Org-standard Fueled CTA banner (per 10up/classifai) in root+package READMEs - Root README docs links -> headstartwp.fueled.com - philosophy.md says HeadstartWP (pre-rename prose); Fueled credited once - Pages-router quick-tutorial: 'At Fueled (formerly 10up), ...' - Unchanged by design: github.com/10up URLs, js1.10up.com demo backend, @10up/next-redis-cache-provider package name, __10up__HEADLESS_CONFIG Naming: guide section 'Documentation' -> 'Developer Guide' (navbar, footer, home grid); /learn route unchanged.
🦋 Changeset detectedLatest commit: 1c5d2be The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Sep 5, 2026
Closed
Contributor
Author
|
@chriseagle so this branch and #958 which is a superset of this branch are the first step imo. Remove any extra dependencies not core to the library ie: linaria, vanilla extract, storybook Update all packages to their latest stable minor #958 takes some larger important steps. Moves us off of 10up-toolkit to WP-Vite-plugins and updates Next to v16. Still keeping everything on React 18.3 to support the Pages Router but this basically does everything but upgrade to React 19 which to me is the first logical step as we'd still support everything and then have the packages in an updated spot to go to 19 and the focus is exclusively on 19 upgrades |
…nsumers The theme was a private, unpublished dev fixture that nothing depended on, but it declared 19 @wordpress/* packages at exact versions while importing only three (i18n, blocks, block-editor). Those 16 unused pins dictated dependency resolution for the entire monorepo: @wordpress/editor@14.40.2 pulled core-data@7.40.2 -> block-editor@15.13.2 -> dataviews@12.0.1, whose private-API opt-in is rejected by @wordpress/private-apis >= 1.54.0. That is what broke @headstartwp/block-primitives' test suite. WordPress packages now live only where they are imported. block-primitives already declares exactly the four it uses (block-editor, components, data, blob) and resolves them on the current generation, where dataviews no longer depends on private-apis at all. - remove wp/10up-theme and its dev:primitives turbo filter - drop the now-unnecessary @wordpress/private-apis override - repoint the staged phpcs hook at wp/headless-wp, which is where 10up/phpcs-composer actually lives; the theme had no phpcs at all - stop mounting the theme in wp/headless-wp/.wp-env.json - declare @types/react, @types/react-dom and @types/jest at the root so the root tsconfig's typeRoots and Next's own type resolution do not depend on npm hoisting happening to place them there Lockfile drops from 1975 to 1482 packages; @WordPress entries from 452 to 76. React stays on 18.3.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VMatBaQUrPS9AhSJmkF2vF
pdavies88
marked this pull request as ready for review
September 20, 2026 01:23
pdavies88
changed the title
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the Change
devEngines)wp/10up-theme; WordPress deps now live with their consumers@10up/eslint-configwith oxlint via Vite+ (vp lint)vp stagedRelease Order
develop(prerelease@next) →trunk→ merge the Version Packages PR.core1.7.0,next1.6.0,block-primitives1.0.0, plugin 1.4.0, plus patch bumps for packages that depend oncorerelease/1.xfromtrunkat that commit, and push it.trunkintochore/nextjs-16-upgrade. This removes the changesets 1.x already used. If you skip it, the 2.0 changelog will say linaria is both "deprecated" and "removed", andcorewould try to release 1.7.0 a second time.next2.0.0,block-primitives2.0.0,next-redis-cache-provider3.0.0One rule for
release/1.x: only release the three packages that got a new major version in 2.x from it (next,block-primitivesandnext-redis-cache-provider).core,epio-searchand the plugin share one version line across both branches, so acorepatch cut fromrelease/1.xwould clash with version numbers thattrunkpublishes.Before either release
wp-env destroyand the Node 24 floor for local dev.How to test the Change
Changelog Entry
Credits
Props @pdavies88
Checklist: