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.
Replace the separate @latest/@next release workflows (and the dead trunk2/develop2 plugin deploy workflows) with .github/workflows/release.yml: - trunk -> @latest, develop -> @next (prerelease mode), one workflow so npm trusted publishing needs a single configuration per package - npm trusted publishing (OIDC) with provenance; NPM_TOKEN is only an optional fallback during the switch-over - plugin release is gated on whether its version is already tagged in 10up/headstartwp-plugin (no more pushes on every trunk commit), and now also creates a @headstartwp/headstartwp GitHub Release - after a stable release, open a trunk -> develop back-merge PR - current action majors (checkout/setup-node v7), Node 24, npm >= 11.5.1 Also: - release-check.yml dry-runs versioning, plugin version sync and npm pack on every PR to trunk/develop - `npm run version` refreshes package-lock.json so Release PRs keep it in sync - harden scripts/version-plugin.sh (fail loudly if the plugin header or constant isn't updated) - add `repository` to published packages (required for provenance) and publishConfig.access=public to epio-search - rewrite RELEASING.md for the automated flow + one-time npm setup - changeset: patch for @headstartwp/core (1.6.2) and @headstartwp/next (1.5.3) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015TQ1wfynjEp6wpqDuuozdg
🦋 Changeset detectedLatest commit: 34f10b1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 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 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
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
Closes #
How to test the Change
Changelog Entry
Credits
Props @username, ...
Checklist:
Before you merge the Release PR