v6.7.1

Bug Fixes

• @byline/client: Public search returns provider totals and facets again (reverts a 6.7.0 regression). In 6.7.0, every public search (status: 'published', the default) through client.collection(path).search() and client.search({ zone }) changed two things. Its total counted only the hits on the current page, and the provider's facets were dropped. The intent was to guard against stale index entries for withdrawn translations. In practice it broke the main search use case for downstream sites. A paginator built on total always showed one page, so results after the first were unreachable, and facet panels lost their counts. It also left providers that report capabilities.facets: true, such as a Solr driver, with no way to return facets to an anonymous reader. 6.7.0 shipped this breaking change as a minor release, noted in one line of an i18n changeset. It should not have. Public searches now pass the provider's total and facets through. Public locale eligibility is the same for every reader, and indexing already applies that rule, so the provider's aggregate already is the public aggregate. The per-hit exact-locale re-check stays: a stale index entry, such as a translation unchecked since the last reindex, is still dropped from the page. The client now logs a warning naming the collection, document id and locale, so you can reindex that document. Until then, total may count a hit the page no longer shows. Searches restricted by the reader keep the page-local total with no facets: a collection with an active beforeRead predicate, or a zone search that excludes member collections the actor can't read. No migration is required.

All other @byline/* packages bumped to 6.7.1 in lockstep with no behavioural changes this cycle.