[JanJakes]

Release 3.1.3

Version bump and changelog update for release 3.1.3.

Changelog draft:

• Fix BINARY and VARBINARY column defaults (#596)
• Quote SQLite identifiers in LOCK TABLES, SHOW TABLES, and compound primary key indexes (#599)
• Name lexer tokens after the MySQL grammar and default to MySQL 8.4.10 (#607)
• Fix MySQL lexer correctness issues (#584)
• Require MySQL proxy authentication and default to loopback (#540)
• Speed up PHPUnit and avoid E2E setup timeouts (#579)
• Fix reserved prefix checks for case variants and foreign keys (#580)

Full changelog: v3.1.2...release/v3.1.3

Next steps

1. Review the changes in this pull request.
2. Push any additional edits to this branch (release/v3.1.3).
3. Merge this pull request to complete the release.

Merging will automatically build the plugin ZIP, create a GitHub release, and deploy to WordPress.org.

Summary by CodeRabbit

• Bug Fixes
  • Improved handling of binary column defaults and SQLite identifier quoting.
  • Corrected MySQL lexer tokens, defaults, and lexer behavior.
  • Updated MySQL proxy authentication and loopback defaults, test timing, and reserved-prefix checks.
• Release
  • Updated the plugin and driver version to 3.1.3.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The plugin and SQLite driver release metadata advances from 3.1.2 to 3.1.3. The readme adds a 3.1.3 changelog entry covering database, lexer, proxy, and test updates.

Changes: 3.1.3 Release Metadata

Layer / File(s)	Summary
Release version and notes packages/mysql-on-sqlite/src/version.php, packages/plugin-sqlite-database-integration/load.php, packages/plugin-sqlite-database-integration/readme.txt	The driver version, plugin header version, and stable tag change to 3.1.3. The new changelog entry lists database, lexer, proxy, and test updates.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Possibly related PRs

• WordPress/sqlite-database-integration#578: Sets the prior 3.1.2 release metadata that this release advances.
• WordPress/sqlite-database-integration#596: Its binary-default changes are listed in the 3.1.3 changelog.
• WordPress/sqlite-database-integration#607: Its lexer token and MySQL version changes are listed in the 3.1.3 changelog.

Merge Risk: Minimal · up to fd34b

The release metadata consistently identifies version 3.1.3. No merge-blocking issue was identified; the change is ready for normal release checks.

Pre-merge checks: 4 · 1

Failed checks: 1 inconclusive

Check name	Status	Explanation	Resolution
Title check		The title "Release 3.1.3" is vague and generic. It names a version number but does not describe the changes in the release. The changeset does bump the version to 3.1.3 in version.php, load.php, and r…	Rewrite the title to name the main content of the release, for example "Release 3.1.3: fix binary defaults, identifier quoting, and MySQL lexer and proxy issues". Alternatively, keep the version name and accept that the title only identifie…

Passed checks: 4 passed

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 2 files. (1 skipped: 1 unsupported.)

Full details: Title check

Explanation

The title "Release 3.1.3" is vague and generic. It names a version number but does not describe the changes in the release. The changeset does bump the version to 3.1.3 in version.php, load.php, and readme.txt and adds a changelog entry, so the title refers to a real part of the change. It does not say what the release contains, though the PR objectives list the fixes (binary column defaults, SQLite identifier quoting, MySQL lexer and proxy fixes, test timing, reserved-prefix checks).

Resolution

Rewrite the title to name the main content of the release, for example "Release 3.1.3: fix binary defaults, identifier quoting, and MySQL lexer and proxy issues". Alternatively, keep the version name and accept that the title only identifies a version bump.

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 84944154-6ad0-47a3-9f35-35a43cc76172

Commits

Reviewing files that changed from the base of the PR and between ef4abde and fd34b53.

Files selected for processing: 1

• packages/plugin-sqlite-database-integration/readme.txt

Files skipped from review as they are similar to previous changes: 1

• packages/plugin-sqlite-database-integration/readme.txt

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review.