First release candidate. Same code as 1.0.0-beta2; the version bump signals "no known bugs, ready for stable" pending soak. This is the build to deploy to production unless soak surfaces a regression.
What's in 1.0.0-rc1
Identical to 1.0.0-beta2. No code changes. The candidate represents the cumulative state of:
Recommended upgrade for all 1.0.0-beta1 users. Fixes a security-relevant correctness bug surfaced by field testing on TubeSpanner Portal: the response subscriber was emitting X-LiteSpeed-Cache-Control: public,max-age=N and X-LiteSpeed-Tag on responses that Drupal had explicitly marked uncacheable (admin pages, authenticated user pages, anything with Cache-Control: private, no-cache, or no-store).
First beta release. Same code as 1.0.0-alpha4, with the version bump signalling API freeze and asking operators to soak the module on production-shape sites. No new features expected before 1.0.0 stable; only bug fixes from production use.
Why beta now
The module has been through four alphas of field testing on TubeSpanner Portal (Drupal 11 / LiteSpeed / Cloudflare). Every bug surfaced during that testing has been fixed:
Two bug fixes from alpha3 field testing on TubeSpanner Portal. The status report's .htaccess diagnostic was lying when directives were appended past the first 8KB; the recommended purge_host example failed silently for any site behind a CDN. Both shipped together.
Bug fix release driven by alpha2 field testing on TubeSpanner Portal. Fixes the CLI/cron purge host resolution bug that made invalidation fail in alpha2 (the dominant operational pattern for tag-based purging), and adds an admin-visible diagnostic for the .htaccess directives the module requires.
## What changed since 1.0.0-alpha2
### Critical fix: HTTP purger works under cron processing
Field-driven release. Alpha1 emitted the right LSCache headers but LSWS refused to store any responses (confirmed via 10 consecutive direct-to-origin requests all returning miss). Alpha2 fixes that, lands the actual HTTP purger, and removes most of the post-install configuration friction.
## What changed since 1.0.0-alpha1
### Caching now works
Three changes addressed the miss-on-every-request symptom, identified by comparing alpha1 against the LiteSpeed-published `lite_speed_cache` source:
First release of LSCache, a Drupal.org-native integration for LiteSpeed Cache, built around Drupal's native cache tag system and the Purge framework.
This is a scaffold alpha. It covers the module's core responsibility of emitting cache-tag headers on cacheable responses and sets up the architecture for the invalidation and advanced features that follow in subsequent releases.
First release of LSCache — a Drupal.org-native integration for
LiteSpeed Cache, built around Drupal's native cache tag system and
the Purge framework.
This is the scaffold alpha. It covers the module's core
responsibility — emitting cache-tag headers on cacheable
responses — and sets up the architecture for the invalidation and
advanced features that land in subsequent releases.
