Remove SQLite from continue-on-error in functional tests

[Copilot]

SQLite compatibility across WP-CLI repositories has matured to the point where SQLite test failures should be treated as real failures rather than silently ignored.

Change

Drops inputs.dbtype == 'sqlite' from the continue-on-error expression in reusable-functional.yml:

# Before
continue-on-error: ${{ inputs.dbtype == 'sqlite' || inputs.dbtype == 'mariadb' || inputs.php == 'nightly' || startsWith( inputs.os, 'windows' ) || startsWith( inputs.os, 'macos' ) }}

# After
continue-on-error: ${{ inputs.dbtype == 'mariadb' || inputs.php == 'nightly' || startsWith( inputs.os, 'windows' ) || startsWith( inputs.os, 'macos' ) }}

SQLite runs will now block on failure like standard MySQL runs. MariaDB, PHP nightly, Windows, and macOS remain as allowed-to-fail.

[Copilot]

Pull request overview

Updates the reusable functional GitHub Actions workflow so SQLite functional test failures are no longer treated as allowed-to-fail, reflecting improved SQLite compatibility across WP-CLI repositories.

Changes:

• Removes inputs.dbtype == 'sqlite' from the continue-on-error expression in the functional test job.
• Keeps existing allowed-to-fail conditions for MariaDB, PHP nightly, Windows, and macOS.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.