Skip to content

🚀 chore(release): WP Bones 3.2.0 - #104

Merged
gfazioli merged 1 commit into
mainfrom
release/v3.2.0
Oct 15, 2026
Merged

gfazioli merged 1 commit into
mainfrom
release/v3.2.0

Conversation

@gfazioli

Copy link
Copy Markdown
Contributor

Sync with WP Bones v3.2.0.

  • package.json 3.1.0 → 3.2.0.
  • The 14 boilerplate ZIPs, from the boilerplates' v3.2.0 tags: each checked for the slug wrapper, built public/ assets, vendor/wpbones/wpbones at v3.2.0, and no tests/, PHPUnit or Jest file.
  • Home (WhatsNew.tsx): 366 tests, 1020 assertions (224 unit, 142 console) measured with composer test on the v3.2.0 tag; 20 releases (gh release list, v2.0.0 to v3.2.0); the deploy card gains v3.2.0 and the test suites.
  • public/newsletter/wpbones-3.2.0-deploy-tests.png: a real deploy --wp of the bench, before and after, for the newsletter.

The docs section itself shipped with #103.

yarn test (13 suites, 78 tests) and yarn build pass.

- package.json 3.1.0 → 3.2.0.
- The 14 boilerplate ZIPs rebuilt from their v3.2.0 tags (vendor/wpbones/wpbones v3.2.0, built assets, no test files).
- Home: 366 tests and 1020 assertions at v3.2.0 (224 unit, 142 console, measured with composer test on the tag), 20 releases, the deploy card names the test suites.
- The newsletter image for 3.2.0.
@vercel

vercel Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
wpbones-website-docs Ready Ready Preview Oct 15, 2026 5:05pm UTC

Request Review

@gfazioli
gfazioli merged commit 4a3aebd into main Oct 15, 2026
2 checks passed
@gfazioli
gfazioli deleted the release/v3.2.0 branch October 15, 2026 17:05

This branch was successfully deployed

2 active deployments
Production — 4a3aebd5 Deployed Oct 15, 2026 by vercel[bot]
Preview — 4a3aebd5 Deployed Oct 15, 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.

1 participant