1.1.0
<ul>
<li>New: Planning Center group leaders now sync to CP Groups. Group Leader gets every leader's name. Group Leader Email gets the group's contact email, or the email of the first leader who has one. On CP Groups 1.2 or later, leaders are saved as Group Leaders rows instead, each with that leader's own email. The contact email is used only when no leader has one. If the leaders cannot be loaded, the leaders already stored are kept.</li>
<li>Fixed: If Planning Center cannot return groups or tag groups, the groups sync now stops and records an error in the log, instead of treating that failure as an empty list and removing group types and tag filters. Events and sermons in the same run still sync.</li>
<li>Fixed: Church Community Builder groups are no longer all marked full. Church Community Builder sends "false" as text, which was being read as yes.</li>
<li>Fixed: Saving, disconnecting, and loading Church Community Builder credentials no longer fails on hosts that do not have the PHP sodium extension.</li>
<li>Fixed: Syncs and background processes no longer start when someone opens a web address on the site. They run only from the schedule or from the Pull buttons on the settings screen.</li>
<li>Improved: Corrections to the introduction, What's New, how-to and settings pages, the Groups Synchronization steps, and Data Mapping.</li>
</ul>
1.0.0
<ul>
<li>Security: CCB API credentials are now encrypted at rest (libsodium with OpenSSL fallback, keyed from your site&#039;s WordPress salts). Existing plain-text credentials keep working and are re-encrypted on the next save.</li>
<li>Security: The CCB subdomain is validated everywhere it is used — malformed values are rejected with a clear error instead of being built into API URLs.</li>
<li>Security: OAuth callback tokens and all settings saved over the REST API are now sanitized per field, driven by the new settings schema.</li>
<li>Security: Added missing permission checks to the PCO option-lookup REST endpoints (they now require an administrator, matching every other settings route).</li>
<li>Security: Raised minimum versions of bundled HTTP libraries past known advisories (Guzzle 7.15.1+).</li>
<li>New: Reset tool under Settings → Advanced (and <code>wp cp-sync reset</code>) with five levels — clear a stuck sync queue, force a full re-import, delete imported content, remove the ChMS connection, or reset everything. Destructive levels require typed confirmation.</li>
<li>New: Per-post sync lock — a &quot;Prevent sync from updating this post&quot; checkbox on every imported post&#039;s edit screen. Locked posts are never overwritten or removed by a sync, so manual customizations are preserved; unchecking resumes syncing on the next run.</li>
<li>New: Sermon syncing from Planning Center Publishing to CP Sermons — episodes published to your Church Center library import as CP Sermons sermons with series, speakers, media URLs, and artwork. Includes a Sermons settings tab with filtering, and a Sync Sermons toggle on the Connect tab.</li>
<li>New: Groups and Events sync can be enabled or disabled per ChMS with toggles on the Connect tab. When a required companion plugin (CP Groups or The Events Calendar) is not active, the toggle is disabled with an explanation, the corresponding settings tab is hidden, and scheduled syncs skip that feed.</li>
<li>New: Optional &quot;Delete all data on uninstall&quot; toggle (Settings → Advanced). Off by default, so uninstalling the plugin keeps your data; turn it on to have WordPress permanently remove all CP Sync settings, the ChMS connection, sync state, and imported content when the plugin is deleted.</li>
<li>Enhancement: The settings screen was rebuilt on the WordPress component library for a native wp-admin look and feel, dramatically smaller page weight, and reliable browser-tab URLs for each settings tab.</li>
<li>Enhancement: Settings screens are now declared in PHP as a schema and rendered by a single form engine — new integrations and fields no longer require custom UI code.</li>
<li>Enhancement: Sync filter conditions no longer crash when no comparison options are available, correctly reset their value when switching between comparison types, and use collision-proof identifiers.</li>
<li>Bug Fix: Fixed a crash when reading a settings field from a group that had not been saved yet.</li>
<li>Bug Fix: Fixed duplicate saves when switching the active ChMS.</li>
<li>Bug Fix: Image-cache error messages were never translatable due to a placeholder text domain.</li>
<li>Removed: The unfinished Ministry Platform settings UI has been removed while MP support is completed; PCO and CCB are unaffected.</li>
<li>Developer: New fast unit-test suite (<code>composer test</code>, 83 tests) and security-focused PHPCS gate (<code>composer lint</code>); <code>composer verify</code> runs both.</li>
<li>Developer: The legacy secondary build system (wpackio) was removed — <code>npm run build:wp</code> is now the only build.</li>
</ul>

0.3.1
<ul>
 	<li>Bug Fix: Fixed incomplete venues created during initial import — venue creation now deferred to enrichment phase where full address data is available.</li>
 	<li>Bug Fix: Fixed stale venue associations persisting when a location is removed in CCB.</li>
 	<li>Enhancement: Two-phase enrichment strategy for CCB events — always enriches new events, then uses modified timestamps to detect changes on subsequent syncs.</li>
 	<li>Enhancement: Eliminated duplicate API calls during CCB event re-enrichment (single `event_profile` call instead of two).</li>
 	<li>Enhancement: Added session-based venue deduplication to prevent redundant updates when multiple events share a venue.</li>
 	<li>Enhancement: Added shimmer loading skeleton to settings page while JS bundle loads.</li>
 	<li>Documentation: Documented CCB event enrichment behavior, the new `cp_sync_{$type}_update_item_after` action hook, and updated venue/location guidance in the troubleshooting and TEC integration guides.</li>
</ul>
0.3.0
<ul>
 	<li>New Feature: CCB event enrichment — automatically fetches full venue addresses and event images from the `event_profile` endpoint after initial import.</li>
 	<li>Enhancement: CCB venue import now supports full location data (street address, city, state, zip).</li>
 	<li>Enhancement: Custom XML parser preserves CCB API attributes for reliable event ID extraction.</li>
 	<li>Enhancement: Graceful enrichment failure handling — errors don't block event import.</li>
</ul>
0.2.0
<ul>
 	<li>Breaking Change: CCB now uses Basic Authentication (username/password) instead of OAuth. Existing users will need to reconnect with API credentials.</li>
 	<li>New Feature: Added WP-CLI commands for CCB debugging (`wp cp-sync ccb test-connection`).</li>
 	<li>New Feature: Added configurable date range for CCB event sync with multiple preset options.</li>
 	<li>New Feature: Added option to remove events outside the configured date range.</li>
</ul>
0.1.7
<ul>
 	<li>Enhancement: Added comprehensive logging to PCO registration event import process</li>
 	<li>Enhancement: Improved debugging capabilities for troubleshooting import issues</li>
 	<li>Enhancement: Added detailed logging for API responses, filtering, and event processing</li>
 	<li>Bug Fix: Fixed OAuth redirect URL construction for admin pages</li>
</ul>
0.1.6
<ul>
 	<li>Enhancement: to the CCB sync</li>
 	<li>Enhancement: better image importing</li>
 	<li>Enhancement: add security check to api endpoints</li>
 	<li>Bug Fix: Update api endpoints</li>
</ul>
0.1.5
<ul>
 	<li>Rebuild assets</li>
</ul>
0.1.4
<ul>
 	<li>Rebuild assets</li>
</ul>
0.1.3
<ul>
 	<li>Initial commit</li>
</ul>