Changelog and Version Policy
Last updated: March 30, 2026
This page defines release note format and versioning policy.
1. Versioning Policy
Section titled “1. Versioning Policy”- Use semantic versioning:
MAJOR.MINOR.PATCH. MAJOR: breaking changes.MINOR: backward-compatible feature additions.PATCH: bug and security fixes without API break.
2. Deprecation Policy
Section titled “2. Deprecation Policy”- Announce deprecations in changelog before removal.
- Document migration path and target removal version/date.
3. Security Patch Policy
Section titled “3. Security Patch Policy”- Security fixes are prioritized and may be released outside normal cadence.
- Customer notice process follows contractual obligations.
4. Changelog Format
Section titled “4. Changelog Format”For each release, include:
- version
- release date (UTC)
- added
- changed
- fixed
- security
5. Web SDK
Section titled “5. Web SDK”1.0.0 - 2026-02-18
Section titled “1.0.0 - 2026-02-18”- Added: enterprise documentation and validation guides.
6. iOS SDK
Section titled “6. iOS SDK”1.0.0 - 2026-02-18
Section titled “1.0.0 - 2026-02-18”- Added: initial changelog baseline entry.
7. Android SDK
Section titled “7. Android SDK”1.0.0 - 2026-02-18
Section titled “1.0.0 - 2026-02-18”- Added: initial changelog baseline entry.
8. CMS Integrations
Section titled “8. CMS Integrations”1.0.0 - 2026-02-18
Section titled “1.0.0 - 2026-02-18”- Added: unified release note template for WordPress, Drupal, Shopify, and builders.
Shopify Integration - 2026-03-30
Section titled “Shopify Integration - 2026-03-30”- 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.