Skip to content

🚀 chore(release): v2.0.11 - #67

Merged
gfazioli merged 1 commit into
mainfrom
release/v2.0.11
Sep 25, 2026
Merged

gfazioli merged 1 commit into
mainfrom
release/v2.0.11

Conversation

@gfazioli

Copy link
Copy Markdown
Contributor

Docs and demos for WPBones v2.0.11.

  • Eloquent ORM gets a MySQL and SQLite section. Since 2.0.11 Eloquent connects to the SQLite file WordPress uses on Playground, Studio and the SQLite Database Integration plugin. There, tables still have to be created through WordPress: a table made with Eloquent's schema builder isn't listed by SHOW TABLES or DESCRIBE (measured on a local Playground, SQLite Database Integration 3.0.2).
  • WordPress environments → Playground says Playground runs on SQLite and that the Database demo works there.
  • package.json 2.0.11.
  • The 14 boilerplate ZIPs, rebuilt on v2.0.11. Checked in every ZIP: the vendored Eloquent.php is byte-identical to v2.0.11, wpbones v2.0.11 and wpkirk-helpers 2.0.13 in installed.json, Stable tag 2.0.11, public/ present, no phpunit. The Database ZIP was run in npx @wp-playground/cli from a blueprint: all 11 Eloquent examples return their values.
  • public/newsletter/wpbones-2.0.11-eloquent-sqlite.png: that page, captured from the local Playground.

yarn test and yarn build pass.

- Eloquent ORM: a "MySQL and SQLite" section. Since 2.0.11 Eloquent
  connects to WordPress's SQLite file on Playground, Studio and the SQLite
  Database Integration plugin; tables still belong to WordPress there.
- WordPress environments: Playground runs on SQLite, and the Database demo
  works there too.
- The 14 boilerplate ZIPs, rebuilt on WPBones v2.0.11.
- The newsletter image: the Eloquent ORM demo page on a local Playground.
@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
wpbones-website-docs Ready Ready Preview Sep 25, 2026 8:11am UTC

Request Review

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🔵 Needs a closer look

Regenerated boilerplate ZIPs or corrected release scope are needed before approval.

Review effort: Lite
Findings: None

What changed in this PR

Updates WPBones v2.0.11 release documentation, version metadata, and SQLite/Eloquent guidance.

Changes:

  • Bumps the package version to 2.0.11.
  • Documents SQLite support and Playground behavior.
  • Refreshes release documentation and associated artifacts.
File Summary
package.json Updates the release version; boilerplate artifacts do not match the stated release contents.
content/​getting-started/​wordpress-environments.mdx Documents Playground’s SQLite environment.
content/​database-orm/​eloquent-orm.mdx Adds MySQL/SQLite Eloquent guidance and schema limitations.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@gfazioli

Copy link
Copy Markdown
Contributor Author

Re the Copilot overview ("boilerplate artifacts do not match the stated release contents", no finding attached): the 14 ZIPs are binary, so the review can't open them. They were checked outside it, one by one: the committed blobs are the files verified above, each vendors Eloquent.php byte-identical to v2.0.11, installed.json has wpbones v2.0.11 and wpkirk-helpers 2.0.13, and Stable tag is 2.0.11. The Database one ran in a local Playground with all 11 Eloquent examples returning their values. Merging.

@gfazioli
gfazioli merged commit af191e7 into main Sep 25, 2026
3 checks passed
@gfazioli
gfazioli deleted the release/v2.0.11 branch September 25, 2026 08:14

This branch was successfully deployed

2 active deployments
Production — af191e76 Deployed Sep 25, 2026 by vercel[bot]
Preview — af191e76 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.

2 participants