Release 2.7.4

[danieliser]

Summary

• use the content-control text domain for requirement notices
• remove obsolete legacy APIs deprecated since version 2.0
• prepare version and changelog for 2.7.4

Validation

• remediation PR Resolve remaining WordPress.org review findings #126 passed PHPCS, PHPStan, assembled artifact verification, and WordPress Plugin Check
• local release tree and ZIP verification passed
• candidate ZIP SHA-256: da5d89c0d61520292cc672dda4da549a733e4db4c908c27d6618519a3eac3a45
• candidate contains composer.json, version 2.7.4, and no removed legacy files or declarations

Summary by CodeRabbit

• Removed

  • Removed legacy APIs and compatibility hooks deprecated since version 2.0.
  • Removed support for deprecated term-related global state.

• Bug Fixes

  • Corrected prerequisite messages to use the plugin’s translation domain, improving localization consistency.

• Chores

  • Updated the plugin and package version to 2.7.4.
  • Updated the changelog and project metadata for the 2.7.4 release.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 1b225eac-f6c8-4c4e-80bd-cac2b5a92787

📥 Commits

Reviewing files that changed from the base of the PR and between e4332f4 and 48f6214.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (12)

• .phpcs.xml.dist
• CHANGELOG.md
• bin/psalm-autoloader.php
• classes/Plugin/Prerequisites.php
• content-control.php
• inc/deprecated.php
• inc/deprecated/class.is.php
• inc/deprecated/class.restrictions.php
• inc/functions/query.php
• inc/functions/rule-callbacks.php
• package.json
• readme.txt

 __________________________________________________________________
< Ah yes, the classic pattern: 'parse first, ask questions never'. >
 ------------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 48f62142a9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep the recently deprecated term global synchronized

When an extension still reads the global $cc_term while Content Control evaluates a term query, this now leaves that global unset or pointing at a previous term while only the managed term value is updated, so custom conditions can evaluate against the wrong taxonomy term. This compatibility global was only deprecated in 2.7.1, whereas the 2.7.4 release notes say only APIs deprecated since 2.0 are being removed; retain the synchronization until a suitably announced breaking release.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Regenerate the API stub after removing legacy declarations

Removing the deprecated loader here leaves bin/stubs/content-control.php inconsistent with the runtime: it still declares JP_Content_Control, JP\CC\Is, JP\CC\Site\Restrictions, and jp_content_control() (for example at lines 4256–4323 and 5757–5764). IDEs and static-analysis consumers using this tracked generated stub will therefore accept calls that now fail at runtime, so the stub should be regenerated as part of this API removal.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-21T03:22:42.068061Z	48f6214	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.