release: v1.8.14 -- WP.org packaging fix, repo hygiene, spec-kit bootstrap - #62
Merged
Conversation
config/feature-registry.json was excluded from every shipped release since commit 48e6d17 (including the live WordPress.org 1.8.13 tag), causing Feature_Registry to silently fall back to Generic_Collector_Adapter for every destination and the admin delivery-adapter/destinations UI to render empty. Remove config/ from .distignore so it ships again. Also add an explicit on-screen warning that the settings backup export contains live, unmasked webhook secrets and CRM tokens (documented in SECURITY-PRIVACY.md), and correct a stale REST-API.md reference to a legacy log controller that no longer exists in the codebase. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude Flow (.claude, .claude-flow, .mcp.json) was local-only tooling with zero tracked files — pure local disk cleanup, no git history impact. Bootstrap GitHub Spec Kit (specify init --here --integration claude --script sh) for structured planning going forward. .claude/skills/speckit-* and .specify/ are tracked in git (matching sibling HugoOS projects) and excluded from the WordPress.org release via .distignore. .gitignore's stale .claude/ and .claude-flow/ blanket-ignore rules are removed since spec-kit's .claude/ output is meant to be committed; .specify/feature.json (the ephemeral active-feature file) is ignored instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…strap Bump CLICUTCL_VERSION and the plugin header to 1.8.14; add the changelog entry to changelog.txt and readme.txt. readme.txt Stable tag stays at 1.8.13 per RELEASING.md -- this release ships to GitHub only, restarting the documented 3-version buffer ahead of WordPress.org. Adds the 2026-08-16 security review plan doc covering shipped fixes, repo-hygiene changes, and the two deferred hardening items (rate-limiter atomicity, attribution field length cap). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Manual security review (2026-08-16) found local
mainwas byte-identical to the live WordPress.org 1.8.13 SVN tag -- zero buffer between GitHub and WP.org despite the documented 3-version policy. This release restarts that buffer: GitHub only, WP.org Stable tag stays at 1.8.13.config/feature-registry.jsonhas been missing from every shipped release (including the live WP.org 1.8.13 tag) since.distignoreexcluded the wholeconfig/directory in48e6d17.Feature_Registryreturned empty adapter classes for every destination, and the admin delivery-adapter/destinations UI rendered empty. Fixed by removingconfig/from.distignore; verified the built 1.8.14 zip now contains the file.SECURITY-PRIVACY.mdnote. Masking behavior itself unchanged (separate product decision).REST-API.mdno longer claims a removed legacy log controller "still exists in the repository"..claude/skills/speckit-*,.specify/), both excluded from the WP.org build via.distignore.Stable tagintentionally stays 1.8.13 perRELEASING.md).docs/PLAN-2026-08-16-security-hardening-and-repo-cleanup.md.Test plan
python3zip-content check confirmsconfig/feature-registry.jsonpresent indist/releases/1.8.14/click-trail-handler-1.8.14.zipgit statusclean after each commit🤖 Generated with Claude Code