What's New in P4 Code Review 2026.2

Released: June 2026

For a complete list of what’s new and bug fixes in this release, see the release notes.

Checklists for code reviews

Add structured validation to code reviews using checklists. Checklists define a set of items that must be reviewed and tracked before approval, helping enforce consistency and best practices across teams.

Checklist items can be reviewed manually or evaluated automatically using AI. Item status can be updated during reviews, including when adding comments, and may block approval when required conditions are not met.

The P4 Code Review API now includes checklist support.

To learn more, see Checklist definitions

AI-driven code review

Enhance code reviews using AI-powered analysis. Checklist items can be evaluated automatically using AI models based on changelist descriptions, file paths, and code diffs.

P4 Code Review now supports Anthropic Claude and Google Gemini models for AI analysis, enabling improved code explanations and review feedback.

To learn more, see AI for code analysis.

Stronger enforcement of P4 Server protections

P4 Code Review now more consistently enforces P4 Server protections across features.

Notification emails can filter file lists based on each recipient’s access permissions. When dm.protects.allow.admin=1 is set, users only see files they are permitted to access.

Activity feeds and changelist views now also respect depot path protections. Users no longer see activity or changelists for depot paths they cannot access.

Expanded wildcard support in branch paths

Previously, wildcard usage in branch paths was limited. With this release, branch paths support both * and ..., making it easier to define flexible mappings without listing multiple explicit paths.

To learn more, see Use wildcards in branch paths.

Project branch PATCH API improvements

The project branch PATCH API now supports adding and removing individual values for fields such as moderator groups, paths, and default reviewers.

The previous full-replacement behavior is still supported.

API endpoint for changelist details

Previously, it was not possible to retrieve changelist details from P4 Server in a structured format. With this release, a new API endpoint provides changelist information in JSON format for use in external tools and integrations.

PHP 8.5 support

P4 Code Review now supports PHP 8.5. Upgrade scripts automatically update PHP during installation and upgrades.

To learn more, see PHP.

Improved Slack notifications

Slack notifications now include the comment provided when a review state is changed, giving better context for updates.

To learn more, see Slack integration.

Improved traceability for attachments

Previously, comment attachment were recorded without clear information about who uploaded the file or which review it belonged to, making it difficult to trace their origin. With this release, the P4 filelog records the name of the user who uploaded the attachment, making it easier to identify the source of uploaded files.

Review page usability improvements

Several updates improve usability in the review interface:

• The mark-as-read icon has been updated to make read and unread states easier to distinguish.

• Expand and collapse controls have also been improved for better visibility and clarity.

Improved strict trigger error messages

Strict trigger error messages now guide users to update their review and re-obtain approval before submitting, reducing confusion and improving workflow clarity.