You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix auto indexer resolution to always mean PHP (#77)
Root cause: HealthChecker and IndexerResolver probed for the Pagefind
binary when indexer was set to 'auto', reporting binary as active.
This contradicts the design rule that auto always means PHP. The binary
pipeline requires explicit 'indexer: binary' configuration.
Fixes: HealthChecker.check() now reads the configured indexer setting
instead of probing binary availability. IndexerResolver.resolve()
returns 'php' for auto without binary probe (dead code but corrected
for consistency). Tests updated to assert the correct auto=php behavior.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,8 @@ This project uses [Semantic Versioning](https://semver.org/). Major versions are
6
6
7
7
## [Unreleased]
8
8
9
-
_No changes yet._
9
+
### Fixed
10
+
-**`auto` indexer now always means PHP on all code paths.**`HealthChecker::check()` now reads the configured `indexer` setting instead of probing binary availability when reporting `indexer_active` — it previously reported `binary` whenever the Pagefind binary was present on disk, even when the setting was `auto` or `php`. `IndexerResolver::resolve()` likewise returns `php` for `auto` without probing the binary. The binary pipeline requires explicit `indexer: binary` configuration.
0 commit comments