Skip to content

Changelog and Version Policy

Last updated: March 30, 2026

This page defines release note format and versioning policy.

  • Use semantic versioning: MAJOR.MINOR.PATCH.
  • MAJOR: breaking changes.
  • MINOR: backward-compatible feature additions.
  • PATCH: bug and security fixes without API break.
  • Announce deprecations in changelog before removal.
  • Document migration path and target removal version/date.
  • Security fixes are prioritized and may be released outside normal cadence.
  • Customer notice process follows contractual obligations.

For each release, include:

  • version
  • release date (UTC)
  • added
  • changed
  • fixed
  • security
  • Added: enterprise documentation and validation guides.
  • Added: initial changelog baseline entry.
  • Added: initial changelog baseline entry.
  • Added: unified release note template for WordPress, Drupal, Shopify, and builders.
  • Added: assertion-based Shopify extension test coverage for boot and embed consent paths.
  • Changed: production release evidence and support-route governance docs for Google audit readiness.
  • Fixed: Shopify consent mapping now safely handles partial payloads without clobbering omitted categories.
  • Security: bridge message handling is same-origin constrained before dispatching consent actions.