Changelog
SoundSync Developer Platform Changelog
Current documentation review and preserved historical product release entries.
October 5, 2026 documentation update
Updated JUCE 0.7.0 guidance covers processor-owned enforcement, editor attachment, serial and account activation, online startup renewal, and immediate local deactivation. New references cover whole-product checkout refunds, original affiliate/collaborator share recovery, program agreements and live consent, growth-flow operations, and versioned subscription bundle billing.
Commercial guidance distinguishes SoundSync-managed processing from external reseller collections and explains the dedicated payout account. Keep-your-products documentation separates paid-invoice ownership from recurring access and unpaid trials. Earlier dated entries remain historical.
October 2, 2026 content review
Guidance now reflects JUCE 0.6.0 processor-owned online licensing, separate HISEScript/native installation, WooCommerce fulfillment, custom-domain GA4, current promotions, product media/files, customer operations, and marketing settings. Older dated entries below are retained as historical release records, not new verification of those releases.
Current source review does not establish new runtime proof for every host, API fixture, provider, or financial workflow. Package-specific compatibility and testing requirements remain in the integration guides.
SoundSync
Verified platform releases
Dates are tied to current repository report timestamps rather than invented historical dates.
2026-07-25
Plugin credential contract documentation, JUCE licensing examples, API final release audit, OpenAPI expansion, and release gates verified.
2026-07-25
Team Accounts production release, product-scoped RBAC, and session revocation verified.
2026-07-25
Subscription Bundle checkout, upgrades and downgrades, proration, scheduled subscription changes, and customer library bundle states verified.
2026-07-24
Commerce, marketplace, operations, marketing, storefront/embed, webhooks, billing, and API documentation coverage backfilled from verified Phase 4 reports.