Skip to content

Release/1.6.2 - Automated Releases - #959

Draft
pdavies88 wants to merge 4 commits into
developfrom
ci/automated-releases
Draft

pdavies88 wants to merge 4 commits into
developfrom
ci/automated-releases

Conversation

@pdavies88

Copy link
Copy Markdown
Contributor

Description of the Change

Closes #

How to test the Change

Changelog Entry

Added - New feature
Changed - Existing functionality
Deprecated - Soon-to-be removed feature
Removed - Feature
Fixed - Bug fix
Security - Vulnerability
Developer - Non-functional update

Credits

Props @username, ...

Checklist:

Before you merge the Release PR

  • On npmjs.com: for each of the five packages, add a trusted publisher under Settings → Trusted publishing (10up / headstartwp / release.yml). Once a release has gone out that way, delete the NPM_TOKEN secret.
  • In repo settings: turn on Settings → Actions → "Allow GitHub Actions to create and approve pull requests" so the workflow can open the Release and back-merge PRs.

github-actions Bot and others added 4 commits April 8, 2026 18:08
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-bot

changeset-bot Bot commented Sep 25, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 34f10b1

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

This PR includes changesets to release 2 packages
Name Type
@headstartwp/core Patch
@headstartwp/next Patch

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

@vercel

vercel Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
headstartwp-app-router Ready Ready Preview Sep 25, 2026 2:33am UTC
headstarwp Ready Ready Preview Sep 25, 2026 2:33am UTC

Request Review

@pdavies88 pdavies88 changed the title Ci/automated releases Release 1.6.2 - Automated Releases Sep 25, 2026
@pdavies88 pdavies88 changed the title Release 1.6.2 - Automated Releases Release/1.6.2 - Automated Releases Sep 25, 2026

This branch was successfully deployed

2 active deployments
Preview – headstarwp — 34f10b1b Deployed Sep 25, 2026 by vercel[bot]
Preview – headstartwp-app-router — 34f10b1b Deployed Sep 25, 2026 by vercel[bot]
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.

3 participants