v1.6.2 — fix asset cache-busting

Fixed

• CCC_VERSION constant was stuck at 1.6.0 — a separate string from the plugin header's Version: field, and it's the one that actually drives the ?ver= cache-busting query on every enqueued asset (banner.css, consent.js, open-cookie-db.json). Because it never got bumped, the v1.6.1 outline-border fix shipped under a URL byte-identical to the cached 1.6.0 asset — so most visitors would not have received it without an edge/browser cache purge, even after the file changed on disk.

No functional or visual change beyond what v1.6.1 already shipped — this release exists purely to make that fix actually reach browsers.

Full Changelog: v1.6.1...v1.6.2

v1.6.1 — light-theme banner fix

Fixed

• Outline button (Reject) was invisible on the default light theme. .ccc-btn--outline had a hard-coded border: 2px solid rgba(255,255,255,0.35), written for a dark banner. Since the plugin's default palette is light (--ccc-bg: #f4f4f4), the border rendered white-on-near-white on every default install — contrast ratio ~1.0, no visible affordance. The border now derives from the button's own text colour (color-mix(in srgb, currentColor 40%, transparent), with an rgba fallback for older browsers), so it works on light and dark palettes alike. Same fix applied to the hover state and to #ccc-modal.

No settings, markup, or JS behaviour changed — CSS only.

Deployment note

Sites still running a versioned plugin folder (coma-cookie-consent-X.Y.Z/, from a manual zip install rather than the deploy pipeline) are skipped by the automated rollout and won't receive this release until renamed to the unversioned coma-cookie-consent/. Versioned folders also mean every upgrade changes every asset URL, and browsers cache old-path 404s for up to 30 days — if a site's banner is unstyled after an update, check for this first.

Full Changelog: v1.6.0...v1.6.1

v1.6.0

v1.6.0: light default theme + auto-detect privacy link

- Default banner palette is now light (light background, dark text); sites that
  set their own Background/Text keep their custom palette unchanged.
- Privacy "Learn more" link falls back to WordPress' native Privacy Policy page
  (WPML/Polylang-localized) when no per-language URL is configured.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>