v1.2.8

Bug Fixes

• Exclude deleted content from Reader Insights: Deleted and trashed articles are excluded from insights lists and overview totals.
• Correct Code Snippet Insights: Analytics associated with deleted or trashed articles and snippets are excluded from interaction counts, questions, line explanations and article counts.
• Validate content before generating AI insights: Prevent insight generation for trashed or invalid content.
• Preserve historical analytics: Existing analytics records are retained; invalid content is filtered from insights rather than unnecessarily deleting historical data.

Improvements

• Use WordPress content records to validate analytics associations, preventing orphaned analytics from appearing in insights reports.
• Improve consistency between Reader Insights and Code Snippet Insights.

Notes

This release addresses reporting accuracy when articles or Code Snippets have been deleted or moved to the bin.

v1.2.7

What's Changed

• Corrected the plugin version metadata across all release files.
• Updated the WordPress plugin header to 1.2.7.
• Updated the Stable tag in readme.txt to 1.2.7.
• Updated package.json and package-lock.json to reflect version 1.2.7.
• Prepared a consistent version for the next release following v1.2.6.

Upgrade Notes

This release corrects version information used for plugin identification and release management. No new features are introduced in this release.

v1.2.6

What's New in v1.2.6

• Canonical Code Snippets: Make reusable Code Snippets the default workflow for creating and managing code.
• Standalone block conversion: Prompt authors to convert legacy standalone blocks into canonical snippets while preserving existing code and settings.
• Improved snippet management: Update editor and REST API references to use the code_snippet post type consistently.
• Flexible reuse: Continue supporting canonical snippets that are not yet linked to an article.

v1.2.5

Release Notes — v1.2.5

Improvements

• Expose Reader Insights in the WordPress REST API: Register _ica_reader_insights as REST-accessible post metadata, including the generated summary, friction points, recommendations, suggested FAQs, generation timestamp and interaction count.
• Clearer Code Snippets identifier: Replace the internal ica_code_example post type identifier with code_snippet, while retaining the user-facing Code Snippets name.
• Simplified Reader Insights endpoint: Rename the AI insights endpoint to a clearer, more user-friendly route and update its plugin callers.
• Preserve existing functionality: Maintain access to saved Code Snippets and generated insights when upgrading.

Notes

• Back up your site before upgrading.
• Verify existing Code Snippets and their associated analytics after updating.
• Generate Reader Insights and confirm the _ica_reader_insights field appears in the relevant WordPress REST API response.

v1.2.4

Version 1.2.4

Fixes

• Fixed HTML code being incorrectly escaped in code blocks after saving and reopening posts.
• Improved code text normalisation to preserve literal HTML and entity characters.
• Improved handling of multiline code and legacy line-break formatting.
• Updated code snippet editor normalisation to keep linked snippets consistent.
• Improved saved snippet readiness consistency by preserving code content correctly.

Compatibility

• Maintains support for existing code snippets and legacy content.
• Includes updated block metadata and normalisation logic for more reliable code preservation.

Testing

• Build and lint checks passed.

v1.2.3

What's New in 1.2.3

Improvements

• Improved code explanation status reporting and validation against the current article context.
• Improved handling of reusable code snippets linked to articles.
• Refined sidebar status styling and wording for clearer explanation readiness.
• Improved consistency between article-level and individual code snippet status indicators.

Release and Build

• Aligned plugin, npm package, lockfile, and WordPress readme version metadata.
• Updated the release workflow to automatically create the GitHub release and attach the built plugin ZIP when a version tag is pushed.

Upgrade

Download wp-intelligent-code-assistant.zip from the release assets and update the plugin in WordPress.

v1.2.2

Merge pull request #20 from michael-bertram/fix/canonical-assistance-…

v1.2.1

Improved AI Explanation Verification and Sidebar UX

This release improves the reliability of saved AI explanations and makes their verification status clearer throughout the Intelligent Code Assistant.

What's Changed

• More reliable explanation status: Saved explanations are checked before being marked as ready.
• Improved article-context validation: Linked code snippets are handled more accurately when reused across articles, helping prevent misleading stale-status warnings.
• Clearer status messages: Consistent wording makes it easier to distinguish verified explanations from those requiring validation or updating.
• Enhanced sidebar experience: Code fingerprint readiness is more visible, with improved styling, spacing, and readability.
• Consistent status indicators: The editor sidebar, individual code blocks, and article workspace now communicate readiness more consistently.

Benefits

These improvements help authors understand whether their saved explanations are ready for readers, need verification in the current article context, or require updating after code changes.

Testing

The changes have been manually tested in WordPress, including explanation status handling, article-context verification, and the updated sidebar presentation.

v1.2.0

🚀 What’s New

Persistent Reader Insights & Code Snippets: Reader Insights and Code Snippets are now saved as post meta data, ensuring your data and state remain intact when refreshing or reopening the application.

v1.1.4

Update Version naming