v0.0.22 — delete-post-meta ability + protected-meta fix + main-menu 0.0.33

Highlights

Three rolled into one release: a new content ability, a docblock/behaviour fix on an existing one, and a shared-menu dependency bump.

New — acrossai/delete-post-meta ability (PR #106)

Deletes a single post meta row via WordPress core delete_post_meta(). Mirrors the input shape of acrossai/update-post-meta for consistent client ergonomics.

• Input: post_id + key (with WP-core-native meta_key alias), optional value (with meta_value alias). When a value is supplied, only rows matching that value are removed; otherwise every row for the given key is removed.
• Output: { success, deleted, message }.
• Access: manage_options capability. Annotations: destructive: true, idempotent: true.
• Registered under the acrossai-abilities-manager-content category alongside get-post-meta and update-post-meta.

Fixed — acrossai/update-post-meta no longer rejects protected meta keys (#99, PR #105)

The pre-0.0.22 execute() short-circuited with success: false whenever is_protected_meta( $key, 'post' ) returned true, contradicting the class docblock ("Works for ANY meta key"). The ability now writes any key that the manage_options gate allows through — the capability check remains the sole access boundary. The registered description was also updated to match ("Works for any meta key, including protected keys.").

Composer bump — acrossai-co/main-menu 0.0.30 → 0.0.33 (PR #107)

Rolls three shared-menu library releases into one hop. composer.lock regenerated to reference e17e1e8.

No breaking changes

• No ability slug rename.
• No REST endpoint change.
• No option-shape change.
• No new required capability.
• Existing 218 abilities behave identically.
• Safe upgrade from 0.0.21.

Composer

"acrossai-co/main-menu": "0.0.33"

Full Changelog: 0.0.21…0.0.22