Skip to content
CAI
Software that uses CAICheck a score

phacility/phabricator

32.0

Weak · 14 November 2026

511k

lines of production code

PHP

primary language

5

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add 'Mark All Read' and 'Send Test Notification' capabilities to the notification system

Users can now clear all unread notifications at once via a new 'Mark All Read' button in the notification panel, which triggers a confirmation dialog (with serious-business mode phrasing) and updates the cache. Additionally, a 'Send Test Notification' button has been added to allow users to verify that their notification settings and server connection are working correctly by generating a test alert.

src/applications/notification/controller · high confidence

Add Almanac engine extensions for search attachments and property management

This change introduces a suite of new engine extension classes in the Almanac application to support advanced search capabilities and programmatic property management. It adds search engine attachments (AlmanacSearchEngineAttachment and its subclasses) that allow queries to retrieve detailed Almanac bindings, properties, interfaces, devices, and networks, with support for filtering by active bindings. Additionally, it implements EditEngine extensions (AlmanacPropertiesEditEngineExtension) and corresponding edit types (AlmanacSetPropertyEditType, AlmanacDeletePropertyEditType) that enable setting and deleting Almanac properties via Conduit and edit operations. The change also includes a DestructionEngine extension for cleaning up Almanac properties and a CacheEngine extension for discovering linked objects to manage cache invalidation when Almanac data changes.

src/applications/almanac/engineextension · high confidence

Add Application PHID type for meta application

A new PHID type class for the 'Application' meta-application has been added, defining the 'APPS' type constant, providing a globe icon, and implementing logic to load handles and query application objects by their PHIDs.

src/applications/meta/phid · high confidence

Add Applications management interface

Introduces a new 'Applications' meta-application that provides a user-facing interface for exploring, viewing details of, editing, installing, and uninstalling other Phabricator applications. This includes dedicated routes for listing applications, viewing individual application details, managing application configurations via panels, and handling mail commands associated with specific applications.

src/applications/meta/application · high confidence

Add CLI workflows for calendar notifications and import reloading

Users can now manage calendar events via the command line using two new workflows. The \calendar notify\ workflow allows administrators to test and debug upcoming event notifications by publishing them immediately for a specified time window (defaulting to 15 minutes). The \calendar reload\ workflow enables manual re-importing of specific calendar events by ID, which is useful for testing importers or correcting data without waiting for scheduled updates.

src/applications/calendar/management · high confidence

Add Content type and Rule type fields to Herald rules

Herald rules now include two new configuration fields: 'Content type' and 'Rule type'. The 'Content type' field allows rules to be filtered based on the content type of the object, using the HeraldAdapterDatasource to provide available options. The 'Rule type' field enables filtering based on the type of the rule itself, utilizing the HeraldRuleTypeDatasource. These fields are grouped under 'Rule Fields' in the rule configuration interface.

src/applications/herald/field/rule · high confidence

A new \DifferentialRemarkupRule\ class has been introduced to handle Remarkup rendering for Differential revisions. This rule enables the system to resolve and display links to Differential revisions (identified by the 'D' prefix) within text, utilizing a viewer context to securely query and load the corresponding revision objects.

src/applications/differential/remarkup · high confidence

Add Diffusion commit custom fields for email notifications

New custom fields are now available to include additional context in commit notification emails: 'Branches' lists the branches a commit appears on, 'Tags' lists associated tags, 'Repository' displays the repository name and monogram, and 'Merged Commits' (disabled by default) lists changes included in merge commits. These fields allow users to see more detailed repository information directly in their email alerts without needing to visit the web interface.

src/applications/repository/customfield · high confidence

Add Doorkeeper application integration

Users can now connect to external software via the new Doorkeeper application, which registers itself under the 'Connect to Other Software' section with a recycle icon and provides routing for tag management at /doorkeeper/tags/.

src/applications/doorkeeper/application · high confidence

Add Duo API integration future

Introduces the PhabricatorDuoFuture class, which handles asynchronous communication with the Duo Security API. This component manages HTTP request construction, HMAC-SHA1 signature generation using integration and secret keys, and JSON response parsing, paving the way for Duo support in multi-factor authentication flows.

src/applications/auth/future · high confidence

Add FIGlet 2.2.5 source code to externals

The project now includes the full source code for FIGlet version 2.2.5 in the externals/figlet directory. This addition brings in the C source files, build scripts (Makefile), font data, and documentation, enabling the application to generate large ASCII art text using the FIGlet engine.

externals/figlet · high confidence

Differential now supports full-text search for revisions via the Ferret engine. This change introduces the \DifferentialRevisionFerretEngine\ and \DifferentialRevisionFulltextEngine\ classes, which configure the search scope for 'differential' revisions and define how revision documents are built, including indexing titles, authors, and reviewer relationships.

src/applications/differential/search · high confidence

Add Herald action to require document signatures

Users can now use a new Herald action called 'Require signatures' to automatically apply the 'needs signature' edge to Legalpad documents. This action is available for non-personal rules and integrates with the Legalpad application, allowing administrators to enforce signature requirements on specific documents based on rule triggers.

src/applications/legalpad/herald · high confidence

Add Herald actions to mark and remove flags

Users can now use Herald rules to automatically apply or remove flags on flaggable objects. This change introduces two new Herald actions: 'Mark with flag', which creates a user-specific flag with a selected color, and 'Remove flag', which deletes an existing flag if it matches the specified color. These actions allow for automated flagging workflows based on personal rules.

src/applications/flag/herald · high confidence

Add Herald field for Space association

A new Herald field has been introduced to allow rules to check or filter based on the Space to which an object belongs. This field supports objects implementing PhabricatorSpacesInterface, retrieves the object's space PHID via PhabricatorSpacesNamespaceQuery, and provides the PhabricatorSpacesNamespaceDatasource for rule configuration.

src/applications/spaces/herald · high confidence

Add Herald integration for Calendar events

Users can now create Herald rules that react to Calendar events being created or updated. This change introduces the necessary adapter and field classes (including a 'Name' field) to allow automation rules to inspect and trigger actions based on Calendar event data.

src/applications/calendar/herald · high confidence

Add Herald integration for Ponder questions

Users can now create Herald rules that trigger when Ponder questions are created or updated. This new adapter allows global and personal rules to react to PonderQuestion objects, enabling automated notifications or actions based on question activity.

src/applications/ponder/herald · high confidence

Add Herald support for Pholio Mocks

Users can now create Herald rules that react to the creation or update of Pholio Mocks. This change introduces a new Herald adapter and specific fields (Name, Description, Author) for Pholio Mocks, allowing automation rules to trigger based on mock metadata.

src/applications/pholio/herald · high confidence

Add Herald support for projects

Users can now create Herald rules that react to project creation and updates. This change introduces a new Herald adapter for projects, along with fields to check which projects are being edited, which project tags were added or removed, and actions to automatically add or remove projects from objects.

src/applications/project/herald · high confidence

Add Legalpad document typeahead datasource

Users can now search for Legalpad documents using the typeahead input field. This change introduces the LegalpadDocumentDatasource, which queries existing Legalpad documents and displays them in the typeahead results, allowing for easier reference and linking of documents within the application.

src/applications/legalpad/typeahead · high confidence

Add Maniphest Remarkup Rule for Task References

A new remarkup rule class has been introduced to handle references to Maniphest tasks (prefixed with 'T'). This rule enables the rendering of task links by loading the corresponding task objects using a viewer-provided context, allowing users to see formatted links to tasks within remarkup content.

src/applications/maniphest/remarkup · high confidence

Add Nuance application controllers for console, items, queues, and sources

Introduces the controller layer for the Nuance application, providing the entry points for the Nuance Console, as well as list, view, edit, and work interfaces for Queues, Items, and Sources. The NuanceItemActionController implements the command execution flow, supporting both immediate local actions and background processing via workers, while the NuanceQueueWorkController provides a dedicated interface for staff to work through open items in a queue.

src/applications/nuance/controller · high confidence

Add Nuance management CLI commands for importing and updating items

This change introduces new command-line management workflows for the Nuance application, allowing administrators to manage data ingestion and item states directly from the terminal. The \nuance import\ command enables users to import data from a specified source, with the ability to target specific import cursors or process all available cursors for that source. Additionally, the \nuance update\ command allows users to schedule updates or route specific items by providing their ID or PHID. These commands rely on new \NuanceSourceQuery\ and \NuanceItemQuery\ classes to resolve sources and items by ID, PHID, or name.

src/applications/nuance/management · high confidence

Add Owners application configuration options

The Owners application now exposes configuration options for managing package fields. Users can select and reorder package fields via the 'owners.fields' setting and define custom field mappings using 'owners.custom-field-definitions', which supports custom field types like 'remarkup' for adding descriptive content to packages.

src/applications/owners/config · high confidence

Add PEAR Text\_Figlet library for ASCII art rendering

The externals/pear-figlet directory now includes the PEAR Text\_Figlet library, enabling the application to render text as ASCII art using standard Figlet fonts. This addition supports loading various font formats, including plain, gzip-compressed (.flf.gz), and ZIP-archived fonts, and is compatible with PHP 8.

externals/pear-figlet · high confidence

Add PHID type definitions for Config, Legalpad, Paste, Phlux, and Slowvote

New PHID type classes have been added to support object identification and handling for several applications. This includes PhabricatorConfigConfigPHIDType for configuration entries, PhabricatorLegalpadDocumentPHIDType for legal documents, PhabricatorPastePastePHIDType for pastes, PhluxVariablePHIDType for Phlux variables, and PhabricatorSlowvotePollPHIDType for slowvote polls. Each class defines the specific type constant, name, icon (where applicable), and query logic required to load and display these objects within the system.

(repo-wide) · high confidence

Add PHID type definitions for Differential Revisions, Diffs, and Changesets

This change introduces new PHID type classes for the Differential application, enabling the system to recognize and handle Differential Revisions (DREV), Diffs (DIFF), and Changesets (DCNG) as distinct object types. Users will now see properly formatted handles for these objects, including monograms, titles, and URIs, and Differential Revisions will correctly display a closed status when applicable. This allows these objects to be resolved via global search and referenced consistently across the platform.

src/applications/differential/phid · high confidence

Add PHID type definitions for Diviner Books and Atoms

New PHID type classes (DivinerBookPHIDType and DivinerAtomPHIDType) are introduced to register Diviner Books and Atoms within the global object system. These types provide specific icons (fa-book and fa-cube), define how handles are loaded (including names, titles, and URIs), and link to their respective query classes, enabling these entities to be properly identified and displayed in global search and object handles.

src/applications/diviner/phid · high confidence

Add PHID type definitions for Phortune entities

This change introduces PHID type handlers for the Phortune application, enabling the system to recognize and generate handles for key entities including Accounts, Merchants, Payment Methods, Payment Providers, Carts, Charges, Products, Purchases, Subscriptions, and Account Emails. By defining these types, the application can now properly reference and display these objects within the platform's object graph.

src/applications/nuance/phid, src/applications/phortune/phid · high confidence

Add PHID type for Image Macros

A new PHID type class (PhabricatorMacroMacroPHIDType) has been added for the Macro application, enabling Image Macros to be referenced by PHID. This implementation defines the type constant as 'MCRO', associates it with the PhabricatorMacroApplication, and provides the necessary logic to load macro objects, generate handles with names and URIs, and display them with an 'Image Macro' label and icon in the UI.

src/applications/macro/phid · high confidence

Add PHID type handlers for Almanac entities

This change introduces PHID type handlers for Almanac entities, including Devices, Interfaces, Networks, Services, Namespaces, and Bindings. These handlers enable the system to properly identify, query, and display handles for these new Almanac objects, integrating them into the broader Phabricator object model.

src/applications/almanac/phid · high confidence

Add PHID type handlers for Dashboards, Panels, and Portals

This change introduces the PHID type definitions for Dashboard entities, enabling the system to recognize, query, and display handles for Dashboards, Panels, and Portals. Users will now see proper handles (including names, URIs, icons, and monograms for panels) when these items are referenced elsewhere in the application, and the system can resolve named objects like panels by their monogram identifiers.

src/applications/dashboard/phid · high confidence

Add PHID type registration for Countdown objects

Introduces the PhabricatorCountdownCountdownPHIDType class to register the 'CDWN' monogram for Countdown objects. This enables the system to resolve, query, and display handles for Countdowns using their PHIDs, including support for loading named objects via their numeric ID suffix.

src/applications/countdown/phid · high confidence

Add PHID type support for Phurl URLs

Introduces the PhabricatorPhurlURLPHIDType class, enabling the system to recognize, handle, and load Phurl URLs via PHIDs. This change allows Phurl URLs to be treated as first-class objects within the Phabricator object graph, supporting operations like handle loading and named object resolution.

src/applications/phurl/phid · high confidence

Add PHID type support for Policies

Users can now resolve and display handles for Policy objects via their PHIDs. This new \PhabricatorPolicyPHIDType\ class enables the system to load policy details and generate user-friendly names and URIs when policies are referenced in other parts of the application.

src/applications/policy/phid · high confidence

Add PHID type support for Ponder questions and answers

Users can now reference Ponder questions and answers via PHIDs in typeahead searches and handle rendering. This change introduces \PonderQuestionPHIDType\ and \PonderAnswerPHIDType\ classes, enabling proper linking and display of these items within the application's object system.

src/applications/ponder/phid · high confidence

Add PHID type support for Tokens

Users can now reference and display tokens using the PHID system. A new \PhabricatorTokenTokenPHIDType\ class has been added to map tokens to the 'TOKN' type constant, enabling token objects to be queried and handled consistently with other Phabricator entities.

src/applications/tokens/phid · high confidence

Add PHID type support for Transactions and Edit Engine Configurations

Users can now reference and resolve PHIDs for application transactions (XACT) and edit engine configurations (FORM). This change introduces the PhabricatorApplicationTransactionTransactionPHIDType and PhabricatorEditEngineConfigurationPHIDType classes, enabling the system to load, query, and generate handles for these specific transaction-related objects, thereby improving the ability to link and display transaction history and configuration details within the application.

src/applications/transactions/phid · high confidence

Add Phabricator repository configuration options

A new configuration class for the Phabricator repository application has been introduced, allowing administrators to manage repository settings. This includes setting the default local path for storing repository copies (defaulting to /var/repo/) and organizing the configuration under the 'apps' group with a 'Repositories' label and hard-disk icon in the UI.

src/applications/repository/config · high confidence

A new PhortuneCartReplyHandler class has been introduced to manage email replies associated with Phortune carts. This handler validates that the mail receiver is a PhortuneCart instance and identifies the object with the 'CART' prefix, enabling the system to process incoming emails specifically related to cart transactions.

src/applications/phortune/mail · high confidence

Add Phrequent time tracking actions to the UI

The Phrequent application now injects 'Start Tracking Time' and 'Stop Tracking Time' actions into the UI for any object implementing the PhrequentTrackableInterface. These actions are conditionally displayed based on whether the user is currently tracking time for that object, and are disabled for logged-out users. The implementation listens to the UI action rendering event to dynamically add these menu items.

src/applications/phrequent/event · high confidence

Add Phrequent time tracking to object curtains

A new PhrequentCurtainExtension has been added to display time-tracking information directly within object curtains. For any object implementing PhrequentTrackableInterface, the curtain now shows a 'Time Spent' panel that lists users currently working on, interrupted, or not working on the object, along with the total duration tracked in high precision.

src/applications/phrequent/engineextension · high confidence

Users can now use the \((...))\ syntax in Phabricator comments and descriptions to create links to short URLs (Phurls). This new remarkup rule supports linking by numeric ID, alias, or Phabricator object monogram (e.g., \U123\). The generated links open in a new tab and include \rel="noreferrer"\ for security. In text-only contexts, such as email notifications, the links are rendered as plain text with the display name and the full absolute URL.

src/applications/phurl/remarkup · high confidence

Add Phurl URL query and search infrastructure

Introduces the query and search engine classes for Phurl URLs, enabling users to retrieve and search for shortened URLs by ID, PHID, name, alias, long URL, or author. The new search engine provides built-in queries for 'All URLs' and 'Authored' URLs, supports filtering by name substrings and aliases, and displays results in a list format with links to the individual URL pages.

src/applications/phurl/query · high confidence

Add Phurl URL typeahead datasource for Remarkup

Users can now search for and insert existing Phurl URLs directly within Remarkup text areas using the typeahead interface. This change introduces a new datasource that queries available Phurl URLs, allowing users to select a URL by name or alias, which is then automatically formatted into the Remarkup syntax ((alias)) for easy reference.

src/applications/phurl/typeahead · high confidence

Add Remarkup rule for embedding Countdown objects

Users can now embed Countdown objects directly in text using Remarkup syntax. This new rule parses handles prefixed with 'C', loads the corresponding countdown entities, and renders them using the standard countdown view, allowing for richer integration of countdown data within Phabricator's text content.

src/applications/countdown/remarkup · high confidence

Add SFTP-based filesystem interface for Drydock

Users can now use SFTP as a storage backend for Drydock resources. This change introduces the DrydockFilesystemInterface abstract class and the DrydockSFTPFilesystemInterface implementation, enabling file read, write, and save operations over SFTP using passphrase-protected SSH private keys.

src/applications/drydock/interface/filesystem · high confidence

Add SMS messaging support and mail stamp routing

The mail engine now supports sending SMS messages in addition to email, allowing users to receive notifications on their mobile devices via primary contact numbers. The engine also introduces a mail stamp system that allows applications to attach routing metadata to messages, which is added as an 'X-Phabricator-Stamps' header to improve client-side mail routing. This change includes new engine classes for SMS delivery and an extension interface for applications to define stamp templates.

src/applications/metamta/engine · high confidence

Add Subscribe, Mute, and Subscribers UI for subscribable objects

Users can now subscribe to and mute notifications for objects that implement the new PhabricatorSubscribableInterface. The UI adds 'Subscribe/Unsubscribe' and 'Mute/Unmute Notifications' actions to the object actions list; these actions are disabled for logged-out users, and objects with automatic subscription rules show a disabled 'Automatically Subscribed' indicator instead. Additionally, a 'Subscribers' property is rendered on object property lists to show who is subscribed, with the exception that Diffusion commit property lists intentionally omit this property (along with Projects and Tokens) to keep the view focused on build status.

src/applications/subscriptions/events · high confidence

Add Subscribers policy rule for subscribable objects

Users can now grant access to objects based on subscription status via a new 'Subscribers' policy rule. This rule applies to any object implementing the subscribable interface, allowing subscribers (and members of subscribed projects) to perform actions. The implementation uses an omnipotent viewer to load project memberships to avoid recursive policy checks and supports transaction hints for predicting policy state during edits.

src/applications/subscriptions/policyrule · high confidence

Add Task Author policy rule for Maniphest tasks

Users can now apply a specific policy rule to Maniphest tasks that restricts actions to the task's author. This new rule, identified as 'maniphest.author', allows the task creator to perform designated actions on their own tasks, providing a granular control option within the task's policy settings.

src/applications/maniphest/policyrule · high confidence

Add Typeahead application entry point

A new Typeahead application has been added to the system, providing a dedicated entry point for typeahead functionality. This application registers routes for browsing typeahead classes and accessing function help documentation, and is configured as a non-launchable, non-uninstallable component within the application registry.

src/applications/typeahead/application · high confidence

Add UIExamples application as a developer prototype

A new 'UIExamples' application has been added to the Developer group, providing a gallery of modern art-style UI examples. This application is marked as a prototype and is accessible at the '/uiexample/' base URI, with routes handling both the main index and specific class views via the PhabricatorUIExampleRenderController.

src/applications/uiexample/application · high confidence

Add XHProf sample storage schema

Introduces the database schema and data access object for XHProf profile samples, enabling the system to store and retrieve sampled profiling data with fields for sample rate, total microseconds, hostname, request path, controller, and user association.

src/applications/xhprof/storage · high confidence

Add assignee filtering for Diffusion commits

Users can now filter Diffusion commits by assignee. This change introduces a new edit field and search field component that allow users to select specific users when editing or searching for commits, leveraging the existing DiffusionIdentityAssigneeDatasource to provide user suggestions.

src/applications/diffusion/editfield, src/applications/diffusion/searchfield · high confidence

Add badge.edit and badge.search Conduit API methods

The Conduit API now exposes two new methods for managing badges: \badge.edit\ allows users to create or modify badges by applying transactions, while \badge.search\ enables reading badge information. These new endpoints integrate with the existing edit and search engine frameworks to provide programmatic access to badge data.

src/applications/badges/conduit · high confidence

Add basic PDF document generation capability

The Phortune application now includes a new PDF generation library in the \src/applications/phortune/pdf\ directory. This addition introduces a suite of classes (including \PhabricatorPDFGenerator\, \PhabricatorPDFObject\, and various fragment handlers) that enable the construction and serialization of PDF documents. Users can now generate PDF output, such as catalogs, utilizing a structured object model that handles PDF headers, cross-reference tables, and content streams.

src/applications/phortune/pdf · high confidence

Add basic email support to Pholio

Pholio now supports receiving emails to interact with mock objects. This change introduces PholioMockMailReceiver to handle incoming mail for Pholio mocks (identified by the 'M' prefix) and PholioReplyHandler to process replies, enabling users to update or manage mocks via email.

src/applications/pholio/mail · high confidence

Add calendar event icon selection options

Users can now choose from a specific set of icons when creating or editing calendar events. The new PhabricatorCalendarIconSet provides a curated list of 16 icons mapped to common event types, including 'Default', 'Party', 'Travel', 'Health / Appointment', 'Sabbatical / Leave', 'Working From Home', 'Holiday', 'Staycation', 'Coffee Meeting', 'Movie', 'Meeting', 'Meal', 'Pet Activity', 'Official Business', 'Field Trip', and 'Conference'.

src/applications/calendar/icon · high confidence

Add chatlog query classes for channel and event data

Introduced two new query classes, PhabricatorChatLogChannelQuery and PhabricatorChatLogQuery, to support the new chatlog application. PhabricatorChatLogChannelQuery enables fetching chat channels by name or ID with cursor-based pagination, while PhabricatorChatLogQuery retrieves chat log events filtered by channel IDs and a maximum epoch, also with pagination. The event query includes logic to attach associated channel objects to each event for richer context.

src/applications/chatlog/query · high confidence

Add config entry and transaction queries

New query classes have been added to the configuration application to support retrieving configuration entries and their associated transactions. PhabricatorConfigEntryQuery allows fetching config entries by ID or PHID with standard paging and policy checks, while PhabricatorConfigTransactionQuery provides a template for loading configuration transaction history.

src/applications/config/query · high confidence

Add configuration panel for application email addresses

Users can now manage application email addresses directly from the application settings. A new 'Application Emails' panel has been added to the configuration interface, allowing authorized users to view, add, edit, and delete email addresses associated with the application. This panel integrates with the existing application configuration structure and supports linking emails to specific spaces.

src/applications/metamta/applicationpanel · high confidence

Add constants for Phortune account email statuses and payment error codes

This change introduces new constant classes to the Phortune application to standardize status values and error handling. PhortuneAccountEmailStatus defines constants for account email states (active, disabled, unsubscribed) and provides a default status, while PhortuneErrCode establishes specific error codes for credit card validation failures (invalid number, CVC, and expiry). These additions support the scaffolding for ad-hoc email addresses and payment method management by providing a centralized source of truth for these values.

src/applications/phortune/constants · high confidence

Add controller and view scaffolding for the Packages application

This change introduces the HTTP controller and view layer for the new Packages application, enabling users to browse and manage publishers, packages, and versions. It adds abstract base controllers and concrete list, edit, and view handlers for each entity, wiring them to their respective search and edit engines. The views provide public-facing listing pages and detail pages that display entity information, associated items (such as a package's versions or a publisher's packages), and transaction timelines, along with edit actions where the user has permission.

src/applications/packages/controller · high confidence

Add credit card expiry date picker control

Introduces PhortuneMonthYearExpiryControl, a new form control that renders month and year dropdowns for credit card expiry dates. The component defaults to the current month and a 20-year range of future years, using AphrontFormSelectControl to generate the select tags with specific sigils for identification.

src/applications/phortune/control · high confidence

Add developer-only debug actions for object handles and hovercards

When developer mode is enabled, a new 'Advanced/Developer...' menu item appears in the UI actions for objects with a PHID. This menu provides quick links to view the object's handle details, open its hovercard, and (for Differential revisions) view the affected path index, aiding in debugging and inspection.

src/applications/system/events · high confidence

Add edge types for Asana and Jira integrations

New edge type classes have been added to the doorkeeper application to support relationships with Asana and Jira. Specifically, this introduces bidirectional edges for Asana tasks and subtasks (linking objects to Asana tasks and subtasks) and for Jira issues (linking objects to Jira issues). These changes enable the system to track and manage associations between internal objects and external Asana/Jira entities.

src/applications/doorkeeper/edge · high confidence

Add edge types for mute, contributor, and subscription relationships

New edge types are introduced to support muting, contributing, and subscription management. The system now tracks mute relationships via PhabricatorMutedEdgeType and PhabricatorMutedByEdgeType, allowing users to mute and unmute subscribable objects. Contributor relationships are tracked with PhabricatorContributedToObjectEdgeType and PhabricatorObjectHasContributorEdgeType, which provide transaction and feed strings for adding, removing, and editing contributors. Subscription and unsubscription actions are handled by PhabricatorObjectHasSubscriberEdgeType, PhabricatorSubscribedToObjectEdgeType, PhabricatorObjectHasUnsubscriberEdgeType, and PhabricatorUnsubscribedFromObjectEdgeType, enabling users to subscribe to and unsubscribe from objects with corresponding activity feed updates.

src/applications/transactions/edges · high confidence

Add edit engines and editors for Packages, Publishers, and Versions

This change introduces the backend edit infrastructure for the Packages application, enabling users to create and modify Packages, Publishers, and Versions. It adds specific edit engines (PhabricatorPackagesPackageEditEngine, PhabricatorPackagesPublisherEditEngine, PhabricatorPackagesVersionEditEngine) that define the UI fields for these entities, such as requiring a Publisher when creating a Package, or enforcing unique keys for Publishers and Packages. It also adds corresponding editors (PhabricatorPackagesPackageEditor, etc.) that handle transaction types, feed stories, and validation for duplicate keys, ensuring that users can manage these resources through a consistent edit interface.

src/applications/packages/editor · high confidence

Add editors and edit engines for Nuance items, queues, and sources

Users can now create and edit Nuance Items, Queues, and Sources through dedicated transaction editors and edit engines. This change introduces the backend infrastructure (NuanceItemEditor, NuanceQueueEditor, NuanceSourceEditor, and their corresponding EditEngine classes) that enables the UI to manage these entities, including setting names, default queues, and view/edit policies.

src/applications/nuance/editor · high confidence

Add email-based subscribe and unsubscribe commands

Users can now manage their subscriptions to objects by sending specific email commands. The new \!subscribe\ command allows adding users or projects as subscribers by specifying their usernames or project hashtags (e.g., \!subscribe alincoln \#ios\), while the \!unsubscribe\ command removes the sender from the subscriber list. These commands are supported for any object implementing the subscribable interface and can also be triggered using the \cc\ alias for subscribing.

src/applications/subscriptions/command · high confidence

Add embedded Slowvote poll view

Introduced SlowvoteEmbedView, a new view component that renders a Slowvote poll in an embedded context. This view displays the poll question, description, and voting options, handling user selection state and result visibility rules (such as hiding results until voting or restricting them to the author). It also includes a footer with a submission button and contextual hints, allowing polls to be interacted with directly within other pages rather than requiring a full page load.

src/applications/slowvote/view · high confidence

Add emoji and macro typeahead datasources

Users can now search for emojis and macros using the typeahead interface. New datasources have been added to support autocomplete for emoji names (displaying the emoji character alongside the name) and macro names (including status indicators for disabled macros), enhancing discoverability within the Macro application.

src/applications/macro/typeahead · high confidence

Add example SSH configuration and hook script for Phabricator VCS integration

Added example files for configuring an SSH daemon to handle Phabricator version control connections. The new \sshd\_config.phabricator.example\ provides a hardened OpenSSH configuration (port 2222, no root login, no password auth) that uses \AuthorizedKeysCommand\ to delegate authentication. The accompanying \phabricator-ssh-hook.sh\ script validates the connecting user and executes Phabricator's \bin/ssh-auth\ binary, enabling secure, non-interactive VCS access.

resources/sshd · high confidence

Add external portal for viewing invoices, receipts, and order details

Users can now access a public-facing view of their Phortune payment account history via unique email-based links. This new external portal allows account holders to view a list of invoices and receipts, inspect individual order details, and print order summaries. The feature also includes an unsubscribe mechanism that permanently disables access for the specific email address, and handles credential rotation by invalidating old access links while providing updated ones for users with existing permissions.

src/applications/phortune/controller/external · high confidence

Add fact management CLI workflows

This change introduces a new set of command-line management tools for the Fact application, allowing administrators to interact with fact data directly. Users can now analyze facts manually via the 'analyze' command (with options to target specific iterators or skip aggregates), view and reset processing cursors using the 'cursors' command, list available fact engines with 'list', and permanently destroy all stored fact data using the 'destroy' command. These workflows extend the base management workflow class to provide consistent access to the underlying fact daemon and cursor infrastructure.

src/applications/fact/management · high confidence

Add fact management script

A new \manage\_facts.php\ script is introduced in the \scripts/fact\ directory to allow users to manage and debug Phabricator data extraction, storage, and configuration used to compute statistics. The script utilizes \PhutilClassMapQuery\ to dynamically locate and register workflows that extend \PhabricatorFactManagementWorkflow\, providing a command-line interface for fact-related operations.

scripts/fact · high confidence

Add feed story rendering for token awards

Users will now see structured feed entries when a token is awarded to an object. This change introduces the \PhabricatorTokenGivenFeedStory\ class, which defines how these events appear in the feed, including the trophy icon, the link to the awarded object, and a text summary stating who awarded which token to whom.

src/applications/tokens/feed · high confidence

Add flag actions to UI event listeners

Introduces a new event listener that injects flag-related actions into the UI action list for objects implementing the PhabricatorFlaggableInterface. Users can now see and interact with flag options directly from the action menu: logged-in users can flag an object for later or remove an existing flag, while unauthenticated users see the flag action disabled.

src/applications/flag/events · high confidence

Add framework for external symbol search with PHP and Python support

This change introduces a new infrastructure for resolving symbols from external sources, allowing Diffusion to display information about built-in language constructs alongside code defined in the repository. It adds a query class that accepts filters for language, type, name, path, line, repository, and character position, along with an abstract source interface. Concrete implementations are provided for PHP (resolving internal functions and classes with links to php.net) and Python (resolving standard library built-ins for both Python 2 and 3 with links to official documentation), enabling users to see external documentation references when navigating code.

src/applications/diffusion/symbol · high confidence

Add full-text search support for repositories, commits, and identities

Users can now search for repositories, commits, and repository identities using full-text search engines. The system indexes repository names, slugs, and descriptions, as well as commit messages, titles, and author relationships. This enables more comprehensive discovery of code and repository metadata through the search interface.

src/applications/repository/search · high confidence

Add garbage collection for Herald transcripts and webhook requests

New garbage collectors have been introduced for Herald transcripts and webhook requests to automatically clean up historical data. Herald transcripts are retained for 30 days before being cleared, while webhook request records are retained for 7 days. This ensures that these specific data types do not accumulate indefinitely in the database.

src/applications/herald/garbagecollector · high confidence

Add generator for Differential Revisions in Lipsum

The Lipsum tool now includes a new generator for creating sample Differential Revisions. This addition allows users to populate their instance with realistic test data, including revisions with attached diffs, reviewers, and CCs, facilitating better testing and demonstration of the Differential application.

src/applications/differential/lipsum · high confidence

Add infrastructure for sending SMS via AWS SNS and Twilio

This change introduces new asynchronous future classes to support sending SMS messages through AWS SNS and Twilio. PhabricatorAmazonSNSFuture provides a parameterized interface for AWS SNS calls, while PhabricatorTwilioFuture handles Twilio API interactions by managing account credentials, method parameters, and timeouts. These components enable the application to integrate with these external SMS providers.

src/applications/metamta/future · high confidence

Add modular transaction types for Space namespaces

This change introduces a new modular transaction system for Space namespaces, allowing users to track and manage changes to space properties through specific transaction types. The new implementation includes transaction handlers for archiving/activating spaces, setting the default space, updating descriptions, and renaming spaces. Each transaction type provides appropriate user-facing titles, feed updates, and validation rules (such as ensuring spaces have names and respecting name length limits). The description transaction also supports change detail views and remarkup diffs for better visibility of content changes.

src/applications/spaces/xaction · high confidence

Add multipart/form-data parser for handling file uploads

The application now includes a new \AphrontMultipartParser\ and \AphrontMultipartPart\ classes in the \src/aphront/multipartparser\ directory to parse \multipart/form-data\ requests. This enables the system to correctly process HTTP uploads containing both form variables and file attachments, extracting headers, filenames, and temporary file paths for further handling. A corresponding test case has been added to verify the parsing logic against sample multipart data.

src/aphront/multipartparser · high confidence

Add policy data to search results via Conduit API

The PhabricatorPolicySearchEngineExtension now exposes a 'policy' field in search results for objects implementing PhabricatorPolicyInterface. This allows Conduit API consumers to retrieve a map of capabilities to their current access policies directly from search queries, eliminating the need for separate API calls to fetch policy details for each result.

src/applications/policy/engineextension · high confidence

Add portal management menu item to profile dashboard

Users can now see and access a 'Manage Portal' item within their profile menu. This new menu item, keyed as 'portal', displays a pencil icon and links to the portal editing interface. It is configured to be non-hideable and non-defaultable, ensuring it remains a consistent part of the profile navigation for users with edit capabilities on the associated portal.

src/applications/dashboard/menuitem · high confidence

Add post lifecycle management and header image support

Users can now archive, publish, unpublish, and move Phame posts to different blogs, with clear visibility indicators for draft and archived states. The post view now supports a hero header image that can be uploaded or deleted, and includes navigation links to adjacent posts in the blog.

src/applications/phame/controller/post · high confidence

Add project membership policy rules

Users can now restrict access to projects based on membership status. New policy rules allow granting permissions to members of specific projects ("members of any project" or "members of all projects") or to members of a particular project. This enables more granular control over who can perform actions within project contexts.

src/applications/project/policyrule · high confidence

Add query and search engines for Dashboards, Panels, and Portals

This change introduces the data-access layer for the new Dashboard application, adding dedicated query classes and search engines for Dashboards, Dashboard Panels, and Portals. Users can now search and filter Dashboards by status, author, and editability; filter Panels by type, status (active/archived), and author; and browse Portals. These components enable the underlying dashboard and portal features by providing the necessary database queries and search result rendering.

src/applications/dashboard/query · high confidence

Add query and search engines for Fund initiatives and backers

This change introduces the data-access layer for the new Fund application, adding query classes and search engines for Fund initiatives and backers. Users can now search and filter Fund initiatives by owner or status (open, owned, all) and view backers associated with specific initiatives, including their contribution amounts and dates. The implementation includes \FundInitiativeQuery\, \FundInitiativeSearchEngine\, \FundBackerQuery\, \FundBackerSearchEngine\, and corresponding transaction queries, enabling the backend support for browsing and managing fund-backed projects.

src/applications/fund/query · high confidence

Add query and search infrastructure for Spaces

This change introduces the backend query and search components for the new Spaces application, enabling users to retrieve, filter, and search policy namespaces. It adds PhabricatorSpacesNamespaceQuery to support fetching spaces by ID, PHID, default status, or archive state, along with caching mechanisms for viewer-specific and global space lists. PhabricatorSpacesNamespaceSearchEngine integrates these queries into the application search UI, allowing users to filter spaces by active status and view them in object item lists with indicators for default and archived states. PhabricatorSpacesNamespaceTransactionQuery provides the foundation for querying transaction history on space objects.

src/applications/nuance/query, src/applications/spaces/query · high confidence

Add query and search support for Packages, Publishers, and Versions

This change introduces the backend query and search engine classes for the Packages application, enabling users to find and filter Packages, Publishers, and Package Versions. Specifically, it adds \PhabricatorPackagesPackageQuery\, \PhabricatorPackagesPublisherQuery\, and \PhabricatorPackagesVersionQuery\ to handle database retrieval with filters like IDs, PHIDs, keys, and name ngrams. It also adds corresponding search engines (\PhabricatorPackagesPackageSearchEngine\, etc.) that allow users to search by name substring and related entities (e.g., searching packages by publisher or versions by package). Transaction queries for these entities are also added to support activity streams.

src/applications/packages/query · high confidence

Add query and search support for Passphrase credentials

Users can now search and filter Passphrase credentials using the standard application search interface. This change introduces a new query class (\PassphraseCredentialQuery\) and a search engine (\PassphraseCredentialSearchEngine\) that enable filtering by credential name, status (active vs. destroyed), and type. The search results display credential details including username and type, with destroyed credentials marked and disabled. A new transaction query class is also added to support querying changes to credentials.

src/applications/passphrase/query · high confidence

Add search and mail integration for Spaces

Users can now search for objects filtered by their associated Space, and objects within Spaces will automatically receive a 'Space' mail stamp. This is enabled by new engine extensions that expose a 'spacePHIDs' search field (aliased as 'space' or 'spaces') for filtering queries, defaulting to active spaces the user can view, and provide Conduit API support for querying by space PHID.

src/applications/spaces/engineextension · high confidence

Add search engine configuration panel to application settings

A new configuration panel has been added to the application settings for search-enabled applications, displaying a table of available search engines along with their read and write capabilities. This panel provides users with visibility into the current search engine status and directs them to the cluster search configuration documentation for further setup.

src/applications/search/applicationpanel · high confidence

Add storage engine configuration panel to Files application

A new configuration panel has been added to the Files application that displays a table of all available storage engines. The panel lists each engine's key, class name, writability status, and file size limit, highlighting those that are configured as writable or chunk engines to help administrators verify the current storage setup.

src/applications/files/applicationpanel · high confidence

Add storage layer for Packages, Publishers, and Versions

This change introduces the database storage objects (DAOs) and transaction classes for the new Packages application. It adds persistent storage for Packages, Publishers, and Versions, including their schema definitions, validation rules, and support for search indexing via ngrams.

src/applications/packages/storage · high confidence

Add structured object destruction and destruction log workflows

Introduces a new \bin/remove\ command suite for the permanent destruction of objects. The \destroy\ subcommand allows administrators to permanently delete specified objects (those implementing \PhabricatorDestructibleInterface\) with a mandatory confirmation prompt and detailed warnings about data loss and potential side effects, or bypass the prompt using the \--force\ flag. A companion \log\ subcommand displays a history of previously destroyed objects, including their class, PHID, and monogram, sourced from the system destruction log.

src/applications/system/management · high confidence

Add support for custom fields in the Owners application

The Owners application now supports custom fields. This change introduces a new base class, PhabricatorOwnersCustomField, which extends the standard custom field infrastructure and defines storage objects for string and numeric indexes. It also adds PhabricatorOwnersConfiguredCustomField, which implements the standard custom field interface to allow owners-specific custom fields to be defined and built via environment configuration.

src/applications/owners/customfield · high confidence

Add system storage schema for action and destruction logs

Introduced a new base \PhabricatorSystemDAO\ class and two concrete storage classes, \PhabricatorSystemActionLog\ and \PhabricatorSystemDestructionLog\, to persist system-level events. The action log tracks actor identities, specific actions, and scores indexed by epoch, while the destruction log records the class, PHID, and monogram of objects being destroyed, also indexed by epoch. These changes provide the underlying data structures required for structured object destruction and system activity auditing.

src/applications/system/storage · high confidence

Add typeahead datasources for Almanac interfaces, services, and service types

Users can now search for and select Almanac interfaces, services, and service types using typeahead fields. This change introduces three new datasources: \AlmanacInterfaceDatasource\ allows browsing interfaces by device name; \AlmanacServiceDatasource\ enables searching services with optional filtering by service type; and \AlmanacServiceTypeDatasource\ provides a list of available service types for selection.

src/applications/almanac/typeahead · high confidence

Add typeahead search for Dashboards, Panels, and Portals

Users can now use typeahead fields to quickly find and select Dashboards, Dashboard Panels, and Portals. This change introduces three new datasources that leverage Ferret search to index and retrieve these items by name, allowing for faster navigation and configuration within the Dashboard application.

src/applications/dashboard/typeahead · high confidence

Add typeahead search for Herald rules, adapters, rule types, and webhooks

Users can now use typeahead search to quickly find Herald rules, adapters, rule types, and webhooks when configuring automation. The new typeahead datasources allow searching by name or, for rules, by their monogram (e.g., 'H123'). Disabled or archived items are clearly marked in the search results to help users identify their status.

src/applications/herald/typeahead · high confidence

Add typeahead support for filtering transactions by object type and form

Users can now filter transaction searches using typeahead fields for specific object types and forms. This change introduces two new typeahead datasources: one that allows selection by transaction object type (derived from application transaction queries) and another that enables selection by form (derived from edit engine configurations), enhancing the ability to narrow down transaction results.

src/applications/transactions/typeahead · high confidence

Add webhook creation and global rule management permissions

Users can now manage permissions for creating webhooks and managing global Herald rules. New policy capabilities have been introduced: 'herald.webhooks' allows users to create webhooks, and 'herald.global' allows users to manage global rules. These capabilities provide granular control over who can perform these specific actions within the Herald application.

src/applications/herald/capability · high confidence

Added DoorkeeperMissingLinkException class

A new exception class, DoorkeeperMissingLinkException, has been introduced to handle specific missing link scenarios within the Doorkeeper application.

src/applications/doorkeeper/exception · high confidence

Added JsShrink external library for JavaScript minification

The JsShrink library has been added to the externals directory, providing a PHP-based tool to remove spaces and comments from JavaScript code. This introduces a new capability for JavaScript minification within the application, serving as an alternative to other tools like jsxmin or Google Closure Compiler.

externals/JsShrink · high confidence

Added Lipsum generator for creating synthetic paste test data

The Lipsum application now includes a new test data generator for pastes, allowing users to create synthetic paste objects for testing purposes. This generator creates pastes with randomized titles (using a context-free grammar for filename generation), content (supporting PHP and Java code snippets or generic lipsum text), and language highlighting settings. It integrates with the existing PhabricatorPasteEditor to create pastes with appropriate transactions for title, language, and content.

src/applications/paste/lipsum · high confidence

Added PHP QR Code library for TOTP token generation

The \externals/phpqrcode\ directory now contains the phpqrcode library (version 1.1.4), enabling the generation of QR codes for TOTP tokens. This addition includes the merged PHP source file (\phpqrcode.php\), configuration constants, and supporting license and documentation files, providing the necessary functionality to encode TOTP secrets into scannable QR images.

externals/phpqrcode · high confidence

Added Phabricator file test data generator

A new test data generator for files has been introduced in the Lipsum application. This generator creates mock JPEG images with random names and associates them with a user, allowing users to populate their test environments with file objects for development and testing purposes.

src/applications/files/lipsum · high confidence

Added Pholio mock data generator

A new test data generator for Pholio mocks has been added, allowing users to automatically generate mock projects with titles, descriptions, and images. The generator creates mock objects using modern initialization methods, assigns author and cover image PHIDs, and applies transactions for name, description, and policy changes, while also handling image sequence and CC assignments.

src/applications/pholio/lipsum · high confidence

Added PhrequentTrackableInterface

A new interface, PhrequentTrackableInterface, has been introduced in the Phrequent application interface layer. This empty interface serves as a marker or contract for classes that participate in the Phrequent time tracking functionality, allowing for type-hinting and polymorphic behavior within the application's architecture.

src/applications/phrequent/interface · high confidence

Added Porter Stemmer library

The project now includes the Porter Stemmer library (externals/porter-stemmer), providing a PHP implementation of the Porter stemming algorithm. This addition includes the core Porter class for reducing words to their root forms, along with the associated MIT license and usage documentation.

externals/porter-stemmer · high confidence

Added XHProf profiling library

This change introduces the XHProf library (version 0.9.2 from Facebook) into the project under externals/xhprof. It includes the core library file xhprof\_lib.php, which provides utility functions for collecting, parsing, and analyzing PHP execution profiles (such as wall time, CPU time, and memory usage), along with the Apache 2.0 license file. This enables the application to use XHProf for performance profiling and debugging.

externals/xhprof · high confidence

Added backup CSRF write guard mechanism

Introduced AphrontWriteGuard as a backup layer for CSRF validation to prevent unvalidated writes from escaping detection. This mechanism requires explicit calls to AphrontWriteGuard::willWrite() before executing writes against new storage engines, ensuring that CSRF tokens are validated. It also provides a scoped mechanism (AphrontScopedUnguardedWriteCapability) for temporarily disabling this protection in rare cases, such as logging, while ensuring the guard is restored even if exceptions occur.

src/aphront/writeguard · high confidence

Added badge data generators for test environments

New test data generators have been added to the Badges application to facilitate the creation of realistic test data. The 'Badges' generator now creates badge objects with randomized names, descriptions, quality levels, and icons using a context-free grammar for loot-style naming. Additionally, a new 'Badges Award' generator has been introduced to create award transactions between random users and badges, allowing testers to populate the system with award history.

src/applications/badges/lipsum · high confidence

Added common password blacklist

Added a common password blacklist (password.lst) sourced from the Openwall Project, containing 3,546 frequently used passwords. This list can be used to identify and reject weak or commonly compromised passwords during authentication or password creation processes.

externals/wordlist · high confidence

Added email invitation worker

A new PhabricatorAuthInviteWorker has been introduced to handle sending email invitations. This worker processes invite tasks by validating the author, creating or regenerating invite codes, and sending a formatted email to the invitee with a link to accept the invitation.

src/applications/auth/worker · high confidence

Added example update script for Phabricator maintenance

A new example script, scripts/install/update\_phabricator.sh, has been added to help administrators upgrade their Phabricator installation. The script automates the process of pulling the latest code for arcanist and phabricator, stopping web servers and daemons (including php-fpm and the notification server if used), running the database schema upgrade, and restarting services.

scripts/install · high confidence

Added flag selection control UI

A new PhabricatorFlagSelectControl view component has been introduced to render a multi-select interface for flags. This component displays a list of checkboxes, each associated with a specific flag color (red, orange, yellow, green, blue, pink, purple, and checkered), allowing users to select multiple flag attributes simultaneously within the application.

src/applications/flag/view · high confidence

Added garbage collection for sent and received MetaMTA mail

Users can now automatically clean up old MetaMTA mail records. Two new garbage collectors have been introduced: one for received mail (deleting records directly from the database) and one for sent mail (using the destruction engine). Both collectors are configured with a default retention policy of 90 days, meaning mail records older than this threshold will be purged during garbage collection runs.

src/applications/metamta/garbagecollector · high confidence

Added mock timeline engine for Pholio

A new PholioMockTimelineEngine class has been introduced to handle timeline rendering for Pholio mocks. This engine queries associated Pholio images and their inline comments, attaches them to the mock object, and renders the transaction view, providing a dedicated mechanism for displaying mock-related timeline data.

src/applications/pholio/engine · high confidence

Added project search field supporting slug-based prefilling

A new PhabricatorProjectSearchField component has been introduced to handle project selection in search contexts. This field allows users to prefill search results using project slugs (e.g., via URL parameters like ?projects=slug) in addition to standard PHID-based selection. It automatically resolves provided slugs to their corresponding project PHIDs and supports function tokens for dynamic evaluation, ensuring that both explicit project identifiers and programmatic queries are handled correctly within the search interface.

src/applications/project/searchfield · high confidence

Added reply handler for Fund Initiative emails

A new reply handler class has been introduced to support email interactions with Fund Initiatives. This handler validates that incoming mail is directed to a Fund Initiative object and assigns the 'I' prefix to associated objects, enabling users to reply to emails regarding fund initiatives.

src/applications/fund/mail · high confidence

Added specific exception classes for Differential field parsing and validation

Two new exception classes, DifferentialFieldParseException and DifferentialFieldValidationException, have been introduced in the Differential application. These classes extend the base Exception class to provide specific error handling for field parsing and validation issues within the Differential workflow.

src/applications/differential/exception · high confidence

Added subscriber query capability for objects

Introduced PhabricatorSubscribersQuery to allow retrieving the list of subscribers for specific objects via their PHIDs. This new query class enables applications to efficiently fetch subscriber relationships by leveraging the existing edge storage system, supporting both broad retrieval for multiple objects and filtered retrieval for specific subscribers.

src/applications/subscriptions/query · high confidence

Added timezone mapping generation and daemon executor script

The system now includes a script to generate a JSON map of Windows timezone identifiers to IANA timezone names, sourced from CLDR data, and a new daemon executor script that manages the lifecycle of PhutilDaemon instances. The executor accepts configuration via stdin, supports debug tracing and verbose logging, and handles process session creation and signal management for running background daemons.

resources/timezones, scripts/daemon/exec · high confidence

Added transaction editor for Passphrase Credential policies

A new editor class for Passphrase Credentials has been introduced, enabling users to modify view and edit policies for these credentials. This change supports the modular transaction system by registering the specific policy transaction types (TYPE\_VIEW\_POLICY and TYPE\_EDIT\_POLICY) and enabling search functionality for the created objects.

src/applications/passphrase/editor · high confidence

Added typeahead datasources for Drydock blueprints, leases, and resources

Users can now use typeahead search fields to quickly select Drydock blueprints, leases, and resources. New datasource classes (DrydockBlueprintDatasource, DrydockLeaseDatasource, DrydockResourceDatasource) provide autocomplete suggestions: blueprints show names with a 'Disabled' status indicator if applicable, leases support exact-match ID entry, and resources show names. This improves the search experience within the Drydock application by allowing users to find and select these entities more efficiently.

src/applications/drydock/typeahead · high confidence

Added user account generation capability to the lipsum tool

The lipsum command-line tool now supports generating realistic user accounts. A new \PhabricatorPeopleTestDataGenerator\ class handles this by creating users with randomized real names, usernames, and email addresses (using the example.com domain), allowing administrators to populate the system with test user data.

src/applications/people/lipsum · high confidence

Allow Drydock blueprints to define and use custom fields

Drydock blueprints can now define and use custom fields. This change introduces a new custom field infrastructure for Drydock, including a base abstract class \DrydockBlueprintCustomField\ and a core implementation \DrydockBlueprintCoreCustomField\ that integrates with the standard custom field system to read, write, and display blueprint-specific data.

src/applications/drydock/customfield · high confidence

Almanac application controllers and capability definitions

This change introduces the core controller layer and policy capabilities for the Almanac application. It adds controllers for managing Devices, Services, Networks, Namespaces, Interfaces, and Bindings, including list, view, edit, and delete operations. The controllers implement the new UI patterns (PHUITwoColumnView, EditEngine) and expose functionality for managing device properties, SSH keys, and service bindings. Additionally, it defines granular policy capabilities (e.g., 'almanac.devices', 'almanac.services') to control user permissions for creating and managing these resources.

src/applications/almanac/controller · high confidence

Almanac application entry point and routing configuration

The Almanac application is now registered as a distinct utility within the system, accessible via the '/almanac/' base URI. This entry point defines the navigation structure and permissions for managing service directories, including dedicated routes for listing, editing, and viewing services, devices, interfaces, bindings, networks, and namespaces. It also establishes the default administrative policies for creating these resources and restricts cluster service management to admins only.

src/applications/almanac/application · high confidence

Almanac query and search engine implementation

This change introduces the query and search engine classes for the Almanac application, enabling users to browse and filter devices, services, interfaces, bindings, namespaces, and networks. Devices can now be searched by name, status (Active or Disabled), and cluster membership, with a default view for active devices. Services support filtering by type, name, and bound devices, while bindings can be queried by service, device, interface, and active status. Interfaces, namespaces, and networks are also searchable by name or associated entities, providing a comprehensive foundation for managing infrastructure resources.

src/applications/almanac/query · high confidence

Automated email notifications for upcoming calendar events

The calendar application now automatically sends email reminders to attendees for upcoming events. This new notification engine scans for events starting within a configurable window (defaulting to 15 minutes) and sends notifications only to attendees who are confirmed as attending and are valid users, excluding imported or disabled accounts. The notification view renders event times in the recipient's local timezone to ensure clarity.

src/applications/calendar/notifications · high confidence

Automated subscription billing via new worker

A new PhortuneSubscriptionWorker has been added to automatically bill subscriptions when a payment method is available. The worker checks if an invoice should be generated for the current billing period and skips billing if the calculated cost is zero or negative. It selects a valid, non-disabled account member to act as the billing actor; if all members are disabled or no members exist, it logs a permanent failure. The worker creates a cart with the 'isInvoice' flag set, charges the subscription's default active payment method, and handles errors by recording issues on the cart rather than failing silently.

src/applications/phortune/worker · high confidence

Automatic cleanup of expired auth challenges, sessions, and temporary tokens

The system now automatically purges expired authentication data to keep the database clean. Three new garbage collectors handle the deletion of expired MFA challenges, expired user sessions, and expired temporary tokens (used for SMS, TOTP, and reset codes). These collectors run automatically in small batches, removing records that have passed their respective expiration times.

src/applications/auth/garbagecollector · high confidence

Calendar application controllers for event management, imports, and exports

This change introduces the controller layer for the new Calendar application, providing the backend routing and request handling for core calendar features. It adds controllers for viewing and editing events (including support for recurring series and imported events), managing event availability and RSVPs (join/decline), and handling drag-and-drop rescheduling. It also implements the full workflow for importing events via .ics file drops and configuring external sources, as well as exporting events to .ics files with public and privileged access modes.

src/applications/calendar/controller · high confidence

Calendar events now support granular view and edit policies

Calendar events now have configurable view and edit permissions, allowing hosts and invited users to control access. This change introduces specific policy rules for 'Event Host' and 'Event Invitees', enabling fine-grained control over who can view or modify event details. The underlying storage and transaction models have been updated to support these policies, ensuring that only authorized users can interact with the event based on their role (host or invitee).

src/applications/calendar/storage · high confidence

Calendar objects now have dedicated PHID types for global search and handles

Calendar Events, Exports, Imports, and External Invitees are now distinct PHID types (CEVT, CEXP, CIMP, CXNV) with their own handle loading logic. This enables these objects to be resolved via global search using their specific identifiers (e.g., E123 for events) and ensures they appear correctly in feeds and handles with appropriate status indicators (such as closed status for cancelled events or disabled imports/exports).

src/applications/calendar/phid · high confidence

Celerity is introduced as a dedicated application for static resource management

The Celerity subsystem is now a formal application within the platform, providing a structured API for managing static resources (CSS, JS, images). This change introduces a new resource map generator and transformer that handle dependency resolution, minification, and URI translation, while also adding support for CSS variables and high-DPI sprite sheets. For users, this means a more robust and modular foundation for how static assets are bundled, versioned, and served, with improved handling of modern browser requirements like Retina displays.

src/applications/celerity · high confidence

Celerity is registered as a core application with dedicated resource routing

The Celerity module is now a first-class application within the platform, ensuring it cannot be uninstalled and remains hidden from standard application listings. This change introduces specific URL routing rules under the '/res/' prefix, allowing the system to serve compiled and post-processed static resources (such as CSS and JavaScript) through the CelerityPhabricatorResourceController, supporting both platform and resource sites for potential CDN integration.

src/applications/celerity/application · high confidence

Conduit is now a first-class application with dedicated UI and routing

Conduit is now registered as a distinct application within the system, providing a dedicated navigation entry, icon, and help documentation. This change introduces a new user interface for managing Conduit tokens, including creation, editing, and termination, as well as a modern CLI handshake workflow for authentication. The application also exposes specific routes for viewing and exporting method call logs, integrating Conduit operations more deeply into the standard application experience.

src/applications/conduit/application · high confidence

Conduit logs and methods are now searchable via ApplicationSearch

Conduit call logs and API methods are now integrated into the global ApplicationSearch system, allowing users to search and filter logs by caller, method, status, and date range, and to browse methods by stability (stable, unstable, deprecated, frozen) and name. This change introduces dedicated search engines and queries for Conduit logs and methods, enabling saved queries, built-in views (e.g., My Calls, All Call Logs, Modern Methods), and export capabilities for logs, while also adding a search engine extension to support Conduit result interfaces in search.

src/applications/conduit/query · high confidence

Config entries now support edit history and audit trails

Configuration entries can now be tracked via a transaction system, allowing administrators to see who created, edited, or deleted specific settings and view the previous and new values in the change history. This is implemented through new storage classes (PhabricatorConfigEntry, PhabricatorConfigTransaction) that integrate with the application's transaction interface, providing detailed change logs for configuration management.

src/applications/config/storage · high confidence

Configurable project workboard background colors

Users can now customize the background appearance of project workboards. A new configuration class defines a range of solid color options (such as Red, Blue, and Grey) as well as gradient themes (like Ripe Peach and Reef), and allows projects to inherit the parent project's background or use no background at all.

src/applications/project/constants · high confidence

Conpherence application registration and routing

The Conpherence application is now registered as a distinct application within the system, providing the foundational structure for its features. This includes defining the base URI, display name, icon, and a comprehensive set of routes for listing rooms, viewing threads, searching within threads, editing room settings, managing participants, and handling room pictures. The application also registers remarkup rules for thread references and excludes its URIs from the quicksand search index.

src/applications/conpherence/application · high confidence

Conpherence threads are now included in the full-text search index. This change introduces a new engine extension that indexes thread comments, allowing users to search within Conpherence discussions. The indexing process respects transaction cursors to ensure accurate updates when comments are added or modified.

src/applications/conpherence/engineextension · high confidence

Conpherence threads now support email replies

Users can now reply to Conpherence threads via email. The system recognizes addresses matching the 'Z' pattern (e.g., Z123) to identify specific threads, allowing users to send messages that are automatically posted to the corresponding conversation. This change introduces dedicated mail receiver and reply handler classes to process incoming emails, handle attachments, and manage participant additions through the Conpherence application.

src/applications/conpherence/mail · high confidence

Console application and event plugin registration

The Console is now registered as a distinct application within the system, exposing routes for the DarkConsole interface and its data endpoints. Additionally, an event plugin API has been introduced to capture and manage system events, supporting a discard mode to filter out unwanted event data.

src/applications/console/application, src/applications/console/plugin/event · high confidence

Countdown application storage and transaction model introduced

The Countdown application now uses a new storage schema and transaction framework. The \PhabricatorCountdown\ object supports title, description, and epoch (end date) fields, with view and edit policies controlled by the application settings and space membership. Transactions for title, description, and epoch changes are now handled via the Modular Transaction framework, enabling detailed change tracking, mail notifications with specific mailtags, and feed updates. The end date is required, and titles are validated for length. The application also supports subscription, flagging, and destruction via the standard interfaces.

src/applications/countdown/storage · high confidence

DarkConsole gains new debugging panels for errors, events, services, and real-time logs

The DarkConsole debugging interface now includes several new panels to help diagnose application behavior. The Error Log panel displays captured errors and warnings with expandable stack traces. The Events panel lists registered event listeners and logs fired events, including whether they were stopped. The Services panel provides information on external service calls and, when query analysis is enabled via the 'Analyze Query Plans' action, performs EXPLAIN analysis on SELECT queries to highlight performance issues like table scans. A new Realtime panel offers debugging controls for real-time notifications, including Reconnect, Replay, and Repaint actions. Additional panels show Request details (with masked sensitive headers), Startup phase timings, and XHProf profiling data.

src/applications/console/plugin · high confidence

Users can now search for Dashboards, Dashboard Panels, and Portals using the platform's Ferret search engine. This change introduces dedicated search engine classes for each entity type, enabling full-text indexing and relationship-based filtering (such as open vs. closed status) for these previously unindexed dashboard components.

src/applications/dashboard/engine · high confidence

Dashboards can now be assigned custom icons

Users can now select a specific icon to represent their dashboards. This change introduces a new icon set for the dashboard application, providing a variety of options such as Home, Blocks, Project, and Calendar, which allows for better visual identification and organization of different dashboard views.

src/applications/dashboard/icon · high confidence

Define policy codex for imported calendar events

Added a new policy codex class for calendar events that explicitly defines the access rules for imported events. Users can now see specific policy indicators (such as a download icon and 'Uses Import Policy' label) for imported events, and the system enforces that imported events inherit view permissions from their source and cannot be edited by users.

src/applications/calendar/codex · high confidence

Differential email actions are now driven by EditEngine commands

Users can now trigger Differential revision actions (such as accepting, declining, or requesting changes) by sending specific email commands to the system. This change introduces a new command class that maps revision action transactions to email keywords, allowing users to manage code reviews through email interactions rather than only via the web interface.

src/applications/differential/command · high confidence

Differential fields modernized to use the CustomField framework

Core Differential fields (Reviewers, Summary, Test Plan, Repository, JIRA Issues, etc.) are now implemented as CustomField objects, providing a unified configuration, storage, and transaction history for revision metadata. This change introduces new fields for Asana representation, branch details, and required legal signatures, while standardizing how lint/unit results and draft status are displayed and managed.

src/applications/differential/customfield · high confidence

Diffusion Conduit API refactoring and new methods

The Diffusion Conduit API layer has been restructured into dedicated method classes (e.g., DiffusionBlameConduitAPIMethod, DiffusionBranchQueryConduitAPIMethod) and expanded with new capabilities. Users can now use the new 'diffusion.blame' method to get blame information for paths, and 'diffusion.commit.search' for commit queries. The 'diffusion.branchquery' method now supports filtering by branch patterns and the 'contains' constraint. Additionally, 'diffusion.getrecentcommitsbypath' is deprecated in favor of 'diffusion.historyquery', and 'diffusion.querycommits' is marked as frozen.

src/applications/diffusion/conduit · high confidence

Display Harbormaster build status on revisions and commits

Users will now see a build status indicator directly on Differential Revision and Commit views. This new UI element, added via the HarbormasterUIEventListener, queries the associated HarbormasterBuildable and its builds to display the current status icon, name, and color. It also links prominently to the Harbormaster Buildable and includes external build links (such as artifacts) in the build result output, providing immediate visibility into build health without navigating away from the code review or commit page.

src/applications/harbormaster/event · high confidence

Display real-time Aphlict connection status in the UI

Users can now see the current status of the Aphlict notification server connection directly in the interface. A new view component initializes a JavaScript behavior that updates the display based on connection states: it shows a green 'Connected' indicator when the socket is open, a yellow 'Setting Up Client' or 'Connecting...' indicator during setup, and a red 'Disconnected' indicator if the connection closes. If the notification server is not enabled in the environment configuration, a grey 'Notification server not enabled' message is displayed instead.

src/applications/notification/view · high confidence

Display space context on object views

Object views now display the name of the associated Space (separated by a pipe) when the object belongs to a non-default space and the viewer has permission to see spaces. This new context view is hidden for default spaces, when no space is associated with the object, or if the viewer lacks visibility into spaces.

src/applications/spaces/view · high confidence

Display token awards in object property lists and action menus

Users can now see which tokens have been awarded for specific objects via a new 'Tokens' property in the object details view, which lists the token name, icon, and the name of the user who awarded it. Additionally, an 'Award Token' or 'Rescind Token' action is now available in the object's action menu, allowing logged-in users with appropriate permissions to grant or revoke tokens directly from the object view.

src/applications/tokens/event · high confidence

Diviner application registration and configuration

The Diviner application is now registered with the platform, defining its base URI at /diviner/, its name as 'Diviner', and its icon as 'fa-sun-o'. This registration establishes the application's routes for main views, atom lists, and specific book/atom content, assigns it to the 'Utilities' group, and configures its default view and edit policies (admin-only for editing). It also integrates Diviner with global search by registering DivinerAtom and DivinerBook as searchable document types and links to the Diviner User Guide in the help documentation.

src/applications/diviner/application, src/applications/maniphest/application, src/applications/pholio/application · high confidence

Dynamic favicon composition with configurable sources and graceful error handling

The favicon system now dynamically composites icons from customizable sources, allowing administrators to define custom favicon resources via the 'ui.favicons' configuration. The implementation introduces a new PhabricatorFaviconRef class that manages icon dimensions, emblems, and caching, merging built-in default icons (such as 76x76, 120x120, 128x128, 152x128, and emblem variants) with user-defined ones. This change also ensures the system recovers more gracefully when favicon configuration points to corrupt or damaged files, preventing crashes during icon generation.

src/applications/files/favicon · high confidence

Embed dashboard panels in comments

Users can now embed dashboard panels directly within comments and other text fields using Remarkup syntax. This new capability allows for richer context by displaying specific dashboard panel content inline, leveraging the new \PhabricatorDashboardRemarkupRule\ to handle the rendering of these embedded objects securely.

src/applications/dashboard/remarkup · high confidence

Enable Conduit API calls via SSH

Users can now invoke Conduit API methods directly over an SSH connection. A new ConduitSSHWorkflow endpoint accepts a method name and JSON parameters, executes the corresponding API call, and returns the JSON response. This change also ensures that API call logs accurately record the caller's PHID and connection details, and utilizes modernized timing and JSON parsing utilities for the operation.

src/applications/conduit/ssh · high confidence

Enable Git LFS authentication over SSH

Users can now authenticate Git Large File Storage (LFS) operations via SSH, allowing LFS uploads and downloads even when standard HTTP repository access is disabled or unavailable. This change introduces a new \git-lfs-authenticate\ SSH workflow that validates the operation and repository configuration, then generates a temporary, single-use HTTP authorization token valid for 24 hours. This token is returned to the Git client, enabling seamless LFS data transfer over HTTP without requiring the user to have a VCS password or full HTTP repository permissions.

src/applications/diffusion/gitlfs · high confidence

Enable Git, Mercurial, and Subversion repository access over SSH

Users can now interact with Git, Mercurial, and Subversion repositories directly via SSH workflows (e.g., \git clone\, \git push\, \hg serve\, \svnserve -t\) through the Diffusion application. This change introduces dedicated SSH workflow classes for each version control system, handling protocol parsing, authentication, and access control. For clustered repositories, SSH requests are automatically proxied to the appropriate cluster nodes, ensuring that reads and writes are routed correctly while maintaining security via device keys and user permissions.

src/applications/diffusion/ssh · high confidence

Enable audit replies for Diffusion commits

Users can now reply to emails regarding Diffusion commits to trigger audit actions. This change introduces a new mail receiver and reply handler for the Audit application that specifically targets commit objects (identified by the 'COMMIT' prefix). The receiver validates that the email relates to a Diffusion commit and delegates the processing of reply content to a transaction-based handler, allowing users to interact with audit workflows directly via email.

src/applications/audit/mail · high confidence

Enable creating and replying to pastes via email

Users can now create new pastes by sending an email to the system, with the email subject used as the paste title and the body as the content. Additionally, existing pastes can be updated by replying to notification emails, allowing users to modify paste content through email interactions.

src/applications/paste/mail · high confidence

Enable email replies and creation for Ponder questions and answers

Users can now interact with the Ponder application via email. The system introduces new mail receivers that allow users to create new Ponder questions by sending an email to a specific address, as well as reply to existing Ponder questions and answers by replying to notification emails. This functionality is implemented through new \PonderQuestionCreateMailReceiver\, \PonderQuestionMailReceiver\, \PonderAnswerMailReceiver\, and their corresponding reply handlers, which parse email subjects and bodies to generate or update Ponder objects.

src/applications/ponder/mail · high confidence

Enable email replies for Macros

Users can now reply to emails regarding Macros to update them, as the Macro application now includes a dedicated mail receiver and reply handler. This change introduces PhabricatorMacroMailReceiver to process incoming mail for Macro objects (identified by the MCRO prefix) and PhabricatorMacroReplyHandler to manage the transaction logic, allowing users to interact with Macros via email just like other supported applications.

src/applications/macro/mail · high confidence

Enable email replies for Phame posts and blogs

Users can now reply to Phame posts and blogs via email. This change introduces new mail receiver and reply handler classes for both PhamePost and PhameBlog, allowing incoming emails to be processed as interactions with these specific Phame objects.

src/applications/phame/mail · high confidence

Enable email replies for shortened URLs

Users can now reply to emails related to shortened URLs (Phurl) to trigger actions. This change introduces the mail receiver and reply handler classes that parse incoming emails, identify the associated URL object by its ID, and route the reply to the appropriate transaction handler, allowing for interactive management of shortened URLs via email.

src/applications/phurl/mail · high confidence

Enable email replies to calendar events

Users can now reply to calendar event transaction emails, which will automatically update the corresponding event. This change introduces a new mail receiver and reply handler for the Calendar application, allowing email interactions to be processed and reflected in the calendar system.

src/applications/calendar/mail · high confidence

Enable email replies to update Countdowns

Users can now send emails to update Countdowns. This change introduces a new mail receiver and reply handler for the Countdown application, allowing users to interact with Countdowns via email by replying to notifications. The system recognizes email subjects containing a Countdown ID (pattern C followed by digits) and processes the email content as a reply to the corresponding Countdown object.

src/applications/countdown/mail · high confidence

Enable email-based interaction with Slowvote polls

Users can now interact with Slowvote polls via email. The system introduces a mail receiver that parses incoming messages containing poll IDs (formatted as 'V' followed by a number) and a reply handler to process those responses, allowing users to cast votes or react to polls without logging into the web interface.

src/applications/slowvote/mail · high confidence

Enable embedding slowvote polls in remarkup text

Users can now embed slowvote polls directly into remarkup content (such as task descriptions or comments) using the 'V' prefix. This change introduces the SlowvoteRemarkupRule, which handles the parsing and rendering of these embedded polls by loading poll data via PhabricatorSlowvoteQuery and displaying it through the SlowvoteEmbedView.

src/applications/slowvote/remarkup · high confidence

Enable file creation and management via email replies

The Files application now supports interacting with files through email. Users can create new files by sending emails with attachments to the designated mail receiver, receiving a confirmation with links to the uploaded files. Additionally, existing files can be managed by replying to email notifications associated with them, leveraging the new FileReplyHandler for transaction-based interactions.

src/applications/files/mail · high confidence

Enable full-text search for Phame blogs and posts

Users can now search the content of Phame blogs and posts using the system's full-text search engine. This change introduces dedicated search engine classes for both PhameBlog and PhamePost, indexing blog names and descriptions as well as post titles and bodies, and associating them with their respective authors and archival status.

src/applications/phame/search · high confidence

A new PonderRemarkupRule has been added to allow Ponder questions to be rendered as links within Remarkup text. The rule identifies question objects by the 'Q' prefix and loads them using a viewer context to ensure proper access control.

src/applications/ponder/remarkup · high confidence

Enhanced Diffusion search, navigation, and hovercard capabilities

This change introduces several new engine extensions for the Diffusion application to improve search and user interface interactions. Search results for repositories now include metrics such as commit counts and the most recent commit, and can also return associated repository URIs. A new attachment allows search queries to retrieve auditor information for commits. The global search experience is improved with new quick-search datasources for repositories and symbols, as well as 'jump nav' shortcuts (e.g., 'r' for repositories, 'a' for audits, 's' for symbols) that direct users to relevant Diffusion pages. Additionally, commit hovercards have been modernized to display richer details, including the full commit message, author, committer, repository, and audit status. Finally, links to Diffusion files in remarks are now rendered with special formatting to provide better context.

src/applications/diffusion/engineextension · high confidence

Expanded Harbormaster Conduit API with search, edit, and control methods

The Harbormaster Conduit API now exposes a comprehensive set of methods for managing and querying build infrastructure. Users can search for builds, build plans, build targets, build steps, buildables, and artifacts using dedicated search endpoints (e.g., \harbormaster.build.search\, \harbormaster.buildplan.search\). The API also introduces edit capabilities for builds, build plans, build steps, and buildables, allowing users to create or modify these entities. Additionally, a new \harbormaster.createartifact\ method enables the attachment of artifacts to build targets, and \harbormaster.sendmessage\ allows for sending control commands (pause, restart, abort, resume) to builds and buildables, as well as reporting lint and unit results. The legacy \harbormaster.querybuilds\ method is now deprecated in favor of the new search API.

src/applications/harbormaster/conduit · high confidence

Expose modern search and edit endpoints for Almanac resources

The Almanac application now exposes a comprehensive set of modern Conduit API methods for managing infrastructure resources. Users can now search and edit bindings, devices, interfaces, namespaces, networks, and services via dedicated endpoints (e.g., \almanac.binding.search\, \almanac.device.edit\). This provides a consistent, programmatic way to query and modify Almanac entities, replacing or supplementing older API patterns with standard search and edit engine implementations.

src/applications/almanac/conduit · high confidence

Flags application now supports search, filtering, and grouping

Users can now search for flags using the standard Phabricator search interface, with the ability to filter results by object type (e.g., tasks, revisions) and flag color. The search view also allows grouping flags by color for easier visual management. Additionally, flag list items are now disabled if the underlying object they reference is closed, preventing interaction with resolved items.

src/applications/flag/query · high confidence

Harbormaster application registration and routing configuration

The Harbormaster application is now fully registered within the Phabricator application framework, exposing its core build and CI capabilities to users. This change defines the application's identity (name, icon, group) and establishes the complete URL routing structure for managing build plans, steps, and builds, including actions like pausing, resuming, restarting, and aborting. It also enables access to build logs (view, render, download), lint and unit messages, and integrates webhooks for CircleCI and Buildkite, while setting default administrative policies for creating plans and editing build configurations.

src/applications/differential/application, src/applications/harbormaster/application · high confidence

Harbormaster build steps can now wait for external messages

Build plans can now configure individual build steps to pause indefinitely after completion, waiting for an external system to report results via the \harbormaster.sendmessage\ API. This is implemented through new custom field classes (\HarbormasterBuildStepCustomField\ and \HarbormasterBuildStepCoreCustomField\) that expose a 'When Complete' setting, allowing users to choose between continuing the build normally or waiting for a message. This enables integration with external workflows where build progress depends on outside actions.

src/applications/harbormaster/customfield · high confidence

Herald PHID type registrations for rules, transcripts, and webhooks

The Herald application now registers PHID type classes for its core objects, enabling consistent object handling and URI generation. Specifically, HeraldRulePHIDType (monogram HRUL) allows rules to be referenced by monogram and displays disabled rules with a closed status. HeraldTranscriptPHIDType (HLXS) provides handles for transcripts. HeraldWebhookPHIDType (HWBH) and HeraldWebhookRequestPHIDType (HWBR) register webhook entities, allowing them to be handled and linked via their respective URIs and names.

src/applications/herald/phid · high confidence

Herald actions are modularized and new actions added

Herald actions are now modular, with a new abstract base class (HeraldAction) and action groups (e.g., Utility, Notify, Prevent) that organize available actions. This change introduces new actions: Call webhooks (queues webhooks for adapters that support them), Add comment (adds a Remarkup comment to objects that support transactions), and Do nothing (a no-op action). Existing actions are also modularized, and the UI now hides actions that the current adapter cannot fire.

src/applications/herald/action · high confidence

Herald application registration and webhook support

The Herald application is now registered with the platform, providing the base URI, icon, and navigation structure for creating notification rules. This change introduces dedicated routes and controllers for managing webhooks (list, view, edit, test, and key management), effectively adding webhook configuration capabilities to the Herald interface. It also defines specific policy capabilities for managing global rules and creating webhooks, restricting these actions to administrators by default.

src/applications/herald/application · high confidence

Herald integration for Phame blogs and posts

Users can now create Herald rules that react to the creation or update of Phame blogs and Phame posts. Two new adapters, HeraldPhameBlogAdapter and HeraldPhamePostAdapter, have been added to the Herald system, enabling global and personal rule types for these specific Phame content objects.

src/applications/phame/herald · high confidence

Herald rules can now trigger Harbormaster build plans

Users can now configure Herald rules to automatically queue Harbormaster build plans when specific conditions are met. This change introduces a new 'Run build plans' action within Herald, allowing administrators to select build plans as targets. When a rule triggers, it creates build requests linked to the rule's PHID as the initiator, and the UI will display which Herald rules are responsible for triggering builds on Harbormaster build plans.

src/applications/harbormaster/herald · high confidence

Herald rules can now trigger actions on outbound email

Users can now create Herald rules that react to the preparation of outbound mail. This change introduces a new 'Outbound Mail' adapter and associated fields (such as Subject and Receiving email addresses) to evaluate mail content. It also adds new actions allowing rules to send emails to specific recipients, force emails to the rule author, route messages as notifications, or require that mail be transmitted over secure channels (must encrypt).

src/applications/metamta/herald · high confidence

Herald rules can now trigger on other Herald rules

The Herald system now supports rules that react to the creation or update of other Herald rules. This is enabled by the new HeraldRuleAdapter, which allows users to configure global or personal rules that execute when a Herald rule itself is modified, facilitating automation around rule management and auditing.

src/applications/herald/adapter · high confidence

Herald rules for commits now support pre-commit content hooks and granular author/committer context

Users can now create Herald rules that trigger on pre-commit content (pushes) rather than only after commits are discovered. This change introduces new fields for pre-commit hooks, including 'Author', 'Committer', 'Raw Author', 'Raw Committer', 'Pusher', 'Pusher is committer', 'Branches', 'Affected files', 'Diff content', and 'Is merge commit'. It also adds context-aware fields for both commits and pre-commit hooks, such as 'Author's packages', 'Author's projects', 'Committer's packages', and 'Committer's projects', allowing rules to react to the specific identities and ownership contexts of the people involved in a push.

src/applications/diffusion/herald · high confidence

Image macros now support associated audio and modular transaction history

The Macro application now allows image macros to have an associated audio file and define an audio behavior (none, play once, or loop), with the author and audio file stored directly on the macro object. Additionally, image macros now use a modular transaction system, enabling a full history of changes and comments to be tracked for each macro.

src/applications/macro/storage · high confidence

Initial Files application definition and routing

The Files application is now defined with its base URI, name, and icon, and registers specific remarkup rules for embedding files and images. The application exposes a comprehensive set of routes for file operations, including viewing, listing, uploading, editing, deleting, and managing transforms, as well as new UI components for attaching files via a curtain interface and detaching them. It also supports email integration for uploading files via attachments and includes a data download route that supports instance identifiers and one-time tokens for secure access.

src/applications/files/application · high confidence

Initial Legalpad storage schema and data models

Introduces the core database schema and storage classes for the Legalpad application, enabling the creation, versioning, and signing of legal documents. This includes the LegalpadDocument model with configurable view/edit policies and signature requirements (individual, corporation, or none), the LegalpadDocumentBody model for storing versioned document text with Remarkup support, and the LegalpadDocumentSignature model for tracking verified/unverified signatures and exemptions. The change also adds the LegalpadTransaction and LegalpadTransactionComment classes to support modular transaction history and line-specific commenting on documents.

src/applications/legalpad/storage · high confidence

Initial Phortune query infrastructure for accounts, carts, and subscriptions

This change introduces the foundational query classes for the Phortune payment application, enabling users to retrieve and filter data for accounts, carts, merchants, charges, payment methods, products, purchases, and subscriptions. It adds specific query engines for searching orders (carts), charges, merchants, and subscriptions, allowing users to view order history, unpaid invoices, charge lists, and subscription details within their account or merchant contexts.

src/applications/phortune/query · high confidence

Initial Ponder storage schema and transaction model

This change introduces the foundational storage layer for the Ponder Q&A application. It defines the database schemas for PonderQuestion and PonderAnswer, including fields for content, status, voting, and mail keys, along with unique constraints to ensure one answer per user per question. It also implements the modular transaction system for both questions and answers, enabling detailed change tracking, email notifications via specific mail tags, and integration with Phabricator's policy, subscription, and markup systems.

src/applications/ponder/storage · high confidence

Initial database schema and migration infrastructure

This change introduces the foundational database schema for the platform, creating core tables for Projects, Differential (code reviews), Maniphest (task tracking), Herald (automation rules), and Repository management. It also establishes the SQL patching system (resources/sql/patches) used to manage schema evolution, including initial migrations for OAuth integration, worker task queues, and user preferences.

resources/sql/patches · high confidence

Initial database schema and storage layer for the Badges application

This change introduces the core storage classes for the new Badges feature, defining the database schema for badges and their awards. It adds PhabricatorBadgesBadge to store badge metadata (name, icon, quality, status) and enables searching by badge name via n-grams. It also adds PhabricatorBadgesAward to track which users have received which badges, replacing the previous edge-based model with a dedicated table. The entry includes the base DAO, transaction types for badge modifications (details, awards, revocations), and the necessary schema specifications to create the required database tables.

src/applications/badges/storage · high confidence

Initial implementation of Phortune payment controller and landing page

This change introduces the foundational controller layer for the new Phortune payment application. The PhortuneController base class provides helper methods to load and filter payment providers for merchants, distinguishing between those that can create payment methods and those supporting one-time payments. The PhortuneLandingController handles the initial user entry point by redirecting users with a single account to their profile, or to the account selection page if multiple accounts exist.

src/applications/phortune/controller · high confidence

Initial implementation of the Legalpad application module

This change introduces the core application definition for Legalpad, enabling the system to recognize and route requests to the new 'Agreements and Signatures' utility. It registers the base URI '/legalpad/', defines the application name and icon, and maps specific URL patterns to controllers for listing, editing, viewing, and verifying legal documents and signatures. Additionally, it configures the application's capabilities, including default view and edit policies tied to document templates, and exposes mail command objects for interacting with Legalpad documents via email.

src/applications/legalpad/application · high confidence

Initial implementation of the OAuth 2.0 server core

This change introduces the foundational classes for the OAuth 2.0 server functionality within Phabricator. It adds \PhabricatorOAuthServer\ to handle the core logic for authorizing clients, generating authorization codes and access tokens, and validating redirects. It also includes \PhabricatorOAuthResponse\ to manage HTTP responses (including error handling and JSON encoding) and \PhabricatorOAuthServerScope\ to define and filter OAuth scopes. This establishes the backend infrastructure for OAuth 2.0 integration.

src/applications/oauthserver · high confidence

Initial payment provider implementations for Stripe, PayPal, and testing

Phortune now includes concrete payment provider implementations for Stripe, PayPal, and a test mode. Merchants can configure Stripe to accept credit and debit cards by providing API keys, and can configure PayPal to accept payments via PayPal accounts by providing API credentials and selecting a test or live mode. A test provider is also available to simulate payments without real money, allowing users to add a virtual payment method for development and testing purposes.

src/applications/phortune/provider · high confidence

Initial scaffolding for the Fund application

This change introduces the foundational structure for the new Fund application, including policy capabilities for creating initiatives and viewing default content, as well as a remarkup rule to link Fund initiatives in text. Users will now have the underlying permission framework and text-linking support necessary for future Fund-related features.

src/applications/fund/capability, src/applications/fund/remarkup · high confidence

Initial storage layer for Dashboards, Panels, and Portals

This change introduces the core data models for the new Dashboard application, adding storage classes for Dashboards, Dashboard Panels, and Portals. Dashboards now support configurable layouts, icons, and archive statuses, while Panels are typed and capable of holding custom properties. Portals provide a container for grouping dashboards and other resources. All entities implement transaction, policy, destructibility, and fulltext/Ferret search interfaces, establishing the foundation for creating, editing, and searching these resources.

src/applications/dashboard/storage · high confidence

Initial storage layer for Passphrase credential management

This change introduces the foundational database schema and data access objects for the new Passphrase application, enabling users to store and manage various types of credentials (such as tokens, SSH keys, and secrets). The diff adds the core \PassphraseCredential\ and \PassphraseSecret\ classes, defining the necessary columns for credential types, access policies, and secret data storage. It also includes the transaction model for tracking changes to credentials and the schema specification for database migrations, establishing the backend infrastructure required for the feature.

src/applications/passphrase/storage · high confidence

Initial storage schema for the Multimeter performance sampling application

This change introduces the foundational database storage layer for the new Multimeter application, which is designed to sample and record performance data such as web request times and subprocess execution. The diff adds the core Data Access Object (DAO) classes, including \MultimeterEvent\ to store specific metrics like static resources, request times, and execution times, along with dimension classes (\MultimeterContext\, \MultimeterHost\, \MultimeterLabel\, \MultimeterViewer\, \MultimeterDimension\) to categorize these events. This provides the persistent backend structure required for the application to ingest and query performance samples.

src/applications/multimeter/storage · high confidence

Initial storage structure for Phrequent time tracking

This change introduces the foundational storage classes for the Phrequent application, enabling users to track and account for time spent on objects. It adds PhrequentUserTime to record individual time events with start/end dates and notes, PhrequentDAO as the base data access object, and PhrequentTimeBlock/PhrequentTimeSlices to calculate total duration by merging time ranges and handling complex scenarios like preemption stacks and ongoing events.

src/applications/phrequent/storage · high confidence

Initial support for Dashboard Portals with status and name management

This change introduces the foundational backend components for a new 'Portals' feature within the Dashboard application. It adds a status constant class defining 'active' and 'archived' states for portals, and implements the transaction logic required to rename a portal, including validation to ensure a title is provided and respects length limits. These files establish the data structure and change-tracking mechanism for portal entities.

src/applications/dashboard/constants, src/applications/dashboard/xaction/portal · high confidence

Introduce APC-backed graph cache for repository path history

Added PhabricatorRepositoryGraphCache to efficiently determine the most recent commit that modified a specific path by caching repository graph data in APC. This replaces slow, per-request VCS log operations (e.g., \git log -n1 \<commit\> -- \<path\>\) with fast in-memory graph walks, significantly improving performance for repository rendering and Diffusion queries like \diffusion.lastmodifiedquery\.

src/applications/repository/graphcache · high confidence

Introduce Almanac storage models for devices, services, interfaces, and bindings

This change adds the core data storage layer for the Almanac application, introducing new database-backed models for devices, services, interfaces, and bindings. Users can now manage infrastructure components through these new entities, with devices supporting status tracking and SSH keys, services organized by type and network, and bindings linking services to interfaces. The storage layer enforces unique constraints on names, supports hierarchical namespace management, and enables property-based configuration for all entities.

src/applications/almanac/storage · high confidence

Introduce Almanac utility classes for address handling, device identity, and name validation

This change adds three new utility classes to the Almanac application to support its core data models and configuration. AlmanacAddress provides a structured representation for network addresses including network PHID, address string, and port, with methods for serialization and hashing. AlmanacKeys introduces logic to retrieve the local host's device ID from a configuration file and query the corresponding device record, as well as a method to determine the SSH username for cluster operations. AlmanacNames enforces strict validation rules for service, device, property, network, and namespace names, ensuring they are between 3 and 100 characters, contain only lowercase alphanumeric characters, hyphens, and periods, and follow specific formatting constraints (e.g., no digit-only segments, no consecutive hyphens or periods).

src/applications/almanac/util · high confidence

Introduce Aphlict real-time notification server and modular connection/rate limiting

This change adds the Aphlict notification server, a new Node.js-based WebSocket server that replaces the previous broadcast mechanism with targeted message transmission to support real-time notifications. It includes a PHP management wrapper (\aphlict\_launcher.php\) and supports clustering, SSL configuration (including certificate chains), and configurable logging. Additionally, the system introduces a modular rate-limiting framework (\PhabricatorClientLimit\ and its subclasses) to enforce separate limits for concurrent connections and request rates, utilizing APC/APCu for state tracking, and improves handling of \X-Forwarded-For\ headers to correctly identify client IPs behind load balancers.

support · high confidence

Introduce AphrontController and AphrontRequest as core request handling components

This change introduces the foundational \AphrontController\ and \AphrontRequest\ classes in the \src/aphront\ directory, establishing the new request lifecycle and routing architecture. \AphrontController\ provides a standardized interface for handling requests, including delegation support, application context management, and resource initialization, while \AphrontRequest\ centralizes access to HTTP data, URI parsing, cookie management, and cluster request handling. These components replace previous ad-hoc request processing logic, enabling more modular and secure handling of user interactions, including support for high-security modes and improved proxy header forwarding.

src/aphront · high confidence

Introduce Application Emails and centralized mail status tracking

This change introduces a new Application Email system, allowing administrators to configure dedicated email addresses for specific applications (such as Maniphest) via the new \PhabricatorMetaMTAApplicationEmail\ storage class and editor. It also centralizes mail delivery and processing outcomes by introducing dedicated status constant classes (\PhabricatorMailOutboundStatus\ for send states like Queued/Sent/Fail, and \MetaMTAReceivedMailStatus\ for inbound processing results like Duplicate/Unknown Sender) and a \PhabricatorMailRoutingRule\ class to manage how incoming mail is routed as either notifications or standard mail.

src/applications/metamta/storage · high confidence

Introduce Application Search controllers for unified query management

This change adds a suite of new controllers in the search application to power the redesigned Application Search interface. The new \PhabricatorApplicationSearchController\ serves as the central delegating controller for search results, exports, and customization, while dedicated controllers handle specific workflows: \PhabricatorSearchEditController\ and \PhabricatorSearchDeleteController\ allow users to create, edit, and delete saved queries (including disabling built-in ones); \PhabricatorSearchDefaultController\ lets users set a default query for an application; \PhabricatorSearchOrderController\ supports reordering queries via drag-and-drop; and \PhabricatorSearchRelationshipController\ manages object relationships. Additionally, \PhabricatorSearchHandleController\ and \PhabricatorSearchHovercardController\ provide developer tools and context-aware hovercards, and \PhabricatorSearchRelationshipSourceController\ powers the relationship source UI. These controllers replace the previous ad-hoc search handling with a modular, unified system for managing named and saved queries across applications.

src/applications/search/controller · high confidence

Introduce ApplicationSearch engine and ProfileMenu infrastructure

This change introduces the core ApplicationSearch engine (PhabricatorApplicationSearchEngine) which provides a unified framework for building, saving, and executing search queries across applications, supporting features like named queries, result ordering, and context-specific rendering. It also adds the ProfileMenu engine and related view classes (PhabricatorProfileMenuEngine, PhabricatorProfileMenuItemView) to replace the previous ProfilePanel system, enabling structured, configurable navigation menus for user profiles and dashboards. Additionally, a new Datasource engine (PhabricatorDatasourceEngine) and Ngram search engine (PhabricatorSearchNgramEngine) are added to support quick-search typeahead functionality and text tokenization, while a new Conduit API method base class (PhabricatorSearchEngineAPIMethod) standardizes search endpoints for the API.

src/applications/search/engine · high confidence

Introduce ApplicationTransaction timeline views and diff rendering

This change adds new view classes for the transactions application to improve how users interact with object history and comments. PhabricatorApplicationTransactionView now groups related transactions and hides older activity by default, showing only content since the user's last interaction to reduce noise in long threads. PhabricatorApplicationTransactionDetailView renders text and JSON changes as tabbed 'Old', 'New', and 'Diff' views, allowing users to easily compare previous and current values. PhabricatorApplicationTransactionCommentView supports versioned drafts, MFA warnings, and edit engine locks, ensuring comments are saved safely and interactions are restricted when objects are locked.

src/applications/transactions/view · high confidence

Introduce Auth Messages management UI for customizing onboarding and welcome flows

Administrators can now view, view details for, and edit authentication messages (such as those used in onboarding or welcome flows) through a new set of controllers. The list page displays all available message types, distinguishing between those using default text and those that have been customized. The view page provides detailed descriptions, previews of the current message text, and shows the default message content for reference. The edit page allows administrators to customize the message content for specific types, with the system automatically creating a new record upon first customization if one does not already exist.

src/applications/auth/controller/message · high confidence

Introduce Badges application for gamified achievements

A new 'Badges' application has been added to the Utilities group, enabling users to manage achievements and notoriety. This change registers the application with the base URI '/badges/' and defines routes for listing, viewing, creating, editing, archiving, and commenting on badges, as well as managing recipients. It also establishes default administrative policies for creating and editing badges.

src/applications/badges/application · high confidence

Introduce Calendar application with event management and import/export capabilities

This change registers the new Calendar application, defining its core identity, base URI (/calendar/), and icon. It establishes the routing infrastructure for viewing, editing, and managing calendar events, including specific endpoints for joining, declining, or canceling events, as well as dragging to reschedule. The application also introduces comprehensive support for importing events via .ics files (including drag-and-drop and bulk deletion) and exporting events to .ics format, alongside configuration for default view and edit policies for new events.

src/applications/calendar/application · high confidence

Introduce Celerity resource abstraction layer

This change introduces a new class hierarchy for managing static assets in Celerity, starting with the base \CelerityResources\ abstract class and its \CelerityPhysicalResources\ and \CelerityResourcesOnDisk\ implementations. The \CelerityResourcesOnDisk\ class specifically expands supported file types to include \.ico\ and \.woff2\ resources alongside existing formats like \.png\, \.js\, and \.css\. A concrete \CelerityPhabricatorResources\ class is added to define the location and mapping for Phabricator's static resources, and tests are included to verify the resource discovery mechanism.

src/applications/celerity/resources · high confidence

Introduce Conduit API Token storage and cluster token automation

This change adds the database schema and storage classes for Conduit API tokens, enabling a more robust authentication mechanism. It introduces three token types—Standard, Command Line, and Cluster—with specific expiration policies (Command Line tokens expire after 1 hour, Cluster tokens after 30 minutes). A key behavioral addition is the automatic generation and caching of Cluster API tokens for logged-in users via \PhabricatorConduitToken::loadClusterTokenForUser\, which ensures a valid token is available for clustered operations by creating new ones if existing ones are missing or expiring within five minutes. The storage layer also includes schema definitions for token metadata and method call logs.

src/applications/conduit/storage · high confidence

Introduce Conduit API exception hierarchy

Adds a new set of exception classes for the Conduit API protocol, establishing a base \ConduitException\ class that supports detailed error descriptions via \setErrorDescription\ and \getErrorDescription\. It also introduces \ConduitMethodNotFoundException\ as an abstract base for method-not-found errors, with concrete implementations \ConduitMethodDoesNotExistException\ (for non-existent methods) and \ConduitApplicationNotInstalledException\ (for methods belonging to uninstalled applications).

src/applications/conduit/protocol/exception · high confidence

Introduce Conduit API tokens and modernize the Conduit console interface

The Conduit application now supports authentication via API tokens, replacing the previous certificate-based workflow. A new token management system includes controllers for generating, viewing, and terminating standard and cluster tokens, as well as a handshake flow for command-line clients. The Conduit API console has been redesigned with a new side navigation, updated documentation views, and example code generation for arc, cURL, and PHP. Additionally, the console is now accessible to logged-out users for browsing method documentation, and the API controller handles both human-readable and JSON output formats with proper capability headers.

src/applications/conduit/controller · high confidence

Introduce Conpherence Durable Column and redesigned layout views

Conpherence now features a persistent 'Durable Column' sidebar that remains visible across page requests, allowing users to switch between chat threads without reloading the main content area. This change introduces new view classes (ConpherenceDurableColumnView, ConpherenceLayoutView) that restructure the application into a multi-pane interface with a dedicated thread list, message pane, and participant sidebar. The update also modernizes the UI by replacing legacy rendering methods with PHUI components, adding support for draft messages, and implementing a new 'NUX' (New User Experience) state for users with no existing rooms.

src/applications/conpherence/view · high confidence

Introduce Conpherence constants for room settings and update actions

This change adds new constant definitions for the Conpherence application, establishing the foundational configuration for user-facing features. It defines available sound options (such as 'tap', 'alert', 'bing') and their default mappings for receive and mention notifications, as well as a set of room theme colors (Light, Blue, Indigo, Peach, Green, Pink) with corresponding CSS class generators. Additionally, it enumerates specific real-time update actions (message, draft, join\_room, add\_person, remove\_person, add\_status, load) that drive the application's live interaction model.

src/applications/conpherence/constants · high confidence

Introduce Conpherence fulltext search and new query classes

Users can now search Conpherence threads by content using a new fulltext search capability. This change adds several new query classes in the Conpherence application, including ConpherenceFulltextQuery for searching message corpus, ConpherenceParticipantCountQuery and ConpherenceParticipantQuery for managing participant data, ConpherenceThreadQuery for thread listing with policy-aware filtering and transaction loading, ConpherenceThreadSearchEngine for integrating with the application search interface, and ConpherenceTransactionQuery for transaction retrieval. The fulltext search uses a ConpherenceIndex table and supports boolean mode matching, allowing users to find threads based on message content.

src/applications/conpherence/query · high confidence

Introduce Conpherence storage schema and data access layer

This change establishes the foundational storage layer for the Conpherence application by adding new database schema definitions and Data Access Objects (DAOs). It introduces the ConpherenceThread, ConpherenceParticipant, ConpherenceTransaction, and ConpherenceIndex classes, defining the column schemas, unique keys, and full-text search capabilities required to persist chat threads, participant states, and message history. Additionally, it implements the ConpherenceDAO base class and schema specification to integrate these new tables into the application's database infrastructure.

src/applications/conpherence/storage · high confidence

Introduce Contact Number management for SMS authentication

This change adds a new 'Contact Numbers' settings panel that allows users to manage phone numbers used for SMS-based authentication. Users can now add, edit, and view contact numbers, designate one as their primary number, and enable or disable specific numbers. A new 'Send Test Message' action is also available, allowing users to verify that a contact number is working by sending a test SMS. The controllers ensure that users can access these settings during account setup and enforce appropriate permissions for editing and status changes.

src/applications/auth/controller/contact · high confidence

Introduce Countdown view component

Added the PhabricatorCountdownView class, which renders the countdown timer interface. This view displays the countdown's monogram and title in a header, shows a table with placeholders for days, hours, minutes, and seconds, and includes a footer with the launch date. It also supports displaying a remarkup description and initializes the client-side JavaScript behavior to update the timer dynamically.

src/applications/countdown/view · high confidence

Introduce Daemons application entry point

A new PhabricatorDaemonsApplication class has been added to define the 'Daemons' application within the admin group. This change registers the application's metadata, including its name, short description, and base URI (/daemon/), and establishes the routing structure for daemon management, task details, log viewing, and bulk job operations.

src/applications/daemon/application · high confidence

Introduce Dashboard Panel Types

This change introduces the foundational panel type system for Dashboards, allowing users to add and configure specific content widgets. The initial set of panel types includes Query (to display search results), Chart (to visualize data), Text (to display static or Remarkup content), and Tabs (to group other panels into a tabbed interface). Each panel type defines its own configuration fields, rendering logic, and header actions, establishing the extensible framework for future dashboard customizations.

src/applications/dashboard/paneltype · high confidence

Introduce Dashboard application controllers

This change adds the initial controller skeleton for the new Dashboard application, including the main console view, a dashboard listing page, profile view logic, and a specific controller to handle adding query panels to dashboards. These controllers establish the basic routing and request handling structure for the feature.

src/applications/dashboard/controller · high confidence

Introduce Dashboards application with portal support and install flow

The new PhabricatorDashboardApplication registers the 'Dashboards' feature as a default-pinned application, exposing routes for creating custom pages, managing portals (collections of dashboards), and handling panel installations. This includes controllers for listing, viewing, editing, and archiving both dashboards and their constituent panels, as well as a dedicated install workflow and console integration, effectively replacing the previous ad-hoc dashboard handling with a structured application entry point.

src/applications/dashboard/application · high confidence

Introduce Diffusion application registration and URI routing

The Diffusion application is now registered as a first-class application with its own entry point, icon, and help documentation. This change establishes the new URI structure for browsing repositories, viewing commits, and managing repository settings, while also exposing mail receivers for commit interactions and defining default policy capabilities for viewing, editing, and pushing to repositories.

src/applications/diffusion/application · high confidence

Introduce DiffusionBuildableEngine to manage buildable status transactions

A new DiffusionBuildableEngine class has been added to handle the publication of buildable status changes. This engine prevents the publication of manual buildables and suppresses updates if the status has not changed or if a build is currently in progress. When valid, it creates and applies a DiffusionCommitBuildableTransaction to record the new buildable status, and provides a method to retrieve the author identity for the associated object.

src/applications/diffusion/harbormaster · high confidence

Introduce DiffusionDocumentRenderingEngine for file browsing

A new DiffusionDocumentRenderingEngine class has been added to handle the rendering of document views within Diffusion. This engine manages the generation of URIs for file references and symbol metadata, integrates coverage data into the rendered references, and sets up blame URIs for file lines. It serves as the underlying mechanism for displaying file contents and associated metadata in the Diffusion browse UI.

src/applications/diffusion/document · high confidence

Introduce DiffusionPathChangeQuery for efficient path change retrieval

A new DiffusionPathChangeQuery class has been added to handle queries for file path changes within a repository commit. This component allows users to retrieve a limited set of direct path changes (additions, modifications, moves) for a specific commit, sorting them by path name. It also deduces 'away paths' (where a file was moved from) when the full result set is loaded, providing context for file moves without requiring separate lookups.

src/applications/diffusion/query/pathchange · high confidence

Introduce Diviner Atom and Atom Ref classes for documentation indexing

This change adds the core data structures for the Diviner documentation system: DivinerAtom and DivinerAtomRef. DivinerAtom represents a specific documentation entity (such as a class, method, or article) and handles parsing docblocks, managing links, and providing stable sorting keys. DivinerAtomRef serves as a lightweight reference to these atoms, featuring robust string normalization to handle special characters in names and contexts, and supports serialization via dictionaries and hashes. These classes form the foundation for linking and organizing documentation content.

src/applications/diviner/atom · high confidence

Introduce Diviner Atomizers for PHP and Article Documentation

This change introduces the Diviner Atomizer subsystem, adding new classes (DivinerAtomizer, DivinerPHPAtomizer, DivinerArticleAtomizer, DivinerFileAtomizer) that parse source files into structured documentation atoms. For PHP files, it now extracts function signatures, class/interface declarations (including abstract/final modifiers and inheritance), method details (access modifiers, parameters, return types), and docblock metadata, while explicitly excluding closures. It also supports generating documentation for article files by parsing their docblocks for titles and names. This enables Diviner to provide richer, structured documentation for PHP codebases and internal articles.

src/applications/diviner/atomizer · high confidence

Introduce Diviner documentation generation workflows

Adds new command-line workflows for the Diviner documentation system: \DivinerGenerateWorkflow\ to build documentation books (supporting cache management, repository identifiers, and configurable publishers like the new live publisher) and \DivinerAtomizeWorkflow\ to parse source files into documentation atoms. These changes enable users to generate and manage documentation via \bin/diviner generate\ and \bin/diviner atomize\, including support for \.book\ configuration files, group-based file organization, and fault-tolerant generation.

src/applications/diviner/workflow · high confidence

Introduce Diviner documentation generator script

Adds a new \diviner.php\ entry point for the Diviner documentation generator. The script initializes the environment, sets up argument parsing with a user-facing tagline and synopsis, and dynamically discovers available workflows by querying the class map for classes extending \DivinerWorkflow\, ensuring the tool remains extensible without hardcoding specific command implementations.

scripts/diviner · high confidence

Introduce Diviner renderer architecture with default implementation

Adds the core rendering infrastructure for the Diviner documentation application, establishing an abstract \DivinerRenderer\ base class and a concrete \DivinerDefaultRenderer\. This change enables the system to render code documentation atoms (such as classes, methods, and properties) into HTML, including support for atom titles, types, properties, and descriptions. The default renderer specifically handles the formatting of atom summaries and indexes, grouping references by type, and processes docblock text using a configured markup engine to support remarkup syntax in documentation descriptions.

src/applications/diviner/renderer · high confidence

Introduce Document Rendering Engine for file views

File viewing now uses a new Document Rendering Engine architecture, allowing users to switch between different rendering views (such as blame, syntax highlighting, and encoding options) directly within the file viewer interface. This change centralizes rendering logic, enabling features like view switching, blame toggling, and async rendering for files.

src/applications/files/document/render · high confidence

Introduce DocumentEngine for rich file rendering and diffs

The Files application now uses a new DocumentEngine architecture to render file contents directly in the browser instead of offering only raw text or download links. This adds native support for viewing audio and video files with embedded players, images with rich diff comparisons, JSON with syntax highlighting, Jupyter notebooks with cell-level diffs, PDFs, and hex dumps. The system also supports text encoding detection, syntax highlighting for source code, and blame annotations, while enforcing file size limits to prevent performance issues with large documents.

src/applications/files/document · high confidence

Introduce Doorkeeper bridge framework with initial Asana, GitHub, and JIRA integrations

This change introduces the core Doorkeeper bridge infrastructure, including the abstract DoorkeeperBridge base class and specific implementations for Asana tasks, GitHub issues and users, and JIRA issues. These new components enable the system to pull and synchronize external object references from these services, handling authentication via linked accounts, managing API timeouts, and resolving race conditions during import. Users will now see external objects from Asana, GitHub, and JIRA properly bridged into Phabricator with their metadata and links populated.

src/applications/doorkeeper/bridge · high confidence

Introduce Drydock application registration and routing

The Drydock application is now registered in the system, providing the base URI '/drydock/' and defining the navigation structure for its core entities: blueprints, resources, leases, authorizations, and repository operations. This registration establishes the entry points for users to view and manage software resource allocations, including specific routes for disabling/enabling blueprints, viewing recent active resources and leases, and managing authorization requests.

src/applications/drydock/application · high confidence

Introduce Drydock authorization and blueprint search capabilities

Drydock blueprints can now be searched by name, and a new authorization model allows administrators to control which objects are permitted to use specific blueprints. This is implemented via the new DrydockAuthorization storage class, which tracks requested, authorized, and declined states for blueprint access, and the DrydockBlueprintNameNgrams class, which enables efficient name-based searching of blueprints.

src/applications/drydock/storage · high confidence

Introduce Drydock blueprint implementations for Almanac hosts and working copies

This change adds the concrete implementation classes for Drydock blueprints, specifically \DrydockAlmanacServiceHostBlueprintImplementation\ and \DrydockWorkingCopyBlueprintImplementation\, extending the new abstract \DrydockBlueprintImplementation\ base. For users, this enables Drydock to lease existing hosts defined in an Almanac service pool and to manage repository working copies with proper lease acquisition, resource allocation, and interface configuration (such as SSH access). The implementations handle the lifecycle of these resources, including binding validation, slot locking for concurrency control, and the separation of allocation and activation steps.

src/applications/drydock/blueprint · high confidence

Introduce Drydock repository automation operations

This change adds the foundational classes for Drydock repository automation, including the abstract base class DrydockRepositoryOperationType and two concrete operation types: DrydockLandRepositoryOperation and DrydockTestRepositoryOperation. The 'Land Revision' operation automates the process of committing and pushing a Differential Revision to a target branch, handling authorship metadata and displaying status updates for waiting, working, and done states. The 'Test Configuration' operation allows administrators to verify that Drydock can successfully interact with a repository by running a status check (git/hg/svn) to ensure the automation setup is correct.

src/applications/drydock/operation · high confidence

Introduce EditEngine and Transactional Editors for Phame Blogs and Posts

This change replaces the previous creation and editing mechanisms in the Phame application with a new EditEngine-based architecture. For Phame Blogs, the new PhameBlogEditEngine provides a unified form for creating and editing blogs, supporting fields for name, subtitle, description, full domain URI, parent site details, and status (including archiving). For Phame Posts, the PhamePostEditEngine allows creation and editing of posts with fields for title, subtitle, visibility, and body content, including a remarkup preview panel. Both components are backed by new transactional editors (PhameBlogEditor and PhamePostEditor) that handle policy enforcement, mail notifications (with specific logic to include post body only on initial creation or visibility changes), feed stories, Herald rule application, and subscriber management. A new lock mechanism (PhamePostEditEngineLock) prevents editing of posts where comments are disabled.

src/applications/phame/editor · high confidence

Introduce EditEngine and transaction editors for Fund initiatives and backers

Users can now create and edit Fund initiatives through a structured form that requires a name and a selected merchant account (from Phortune) to receive payments, along with optional description and risks fields. This change also adds the underlying transaction editors for initiatives and backers, enabling activity tracking, email notifications, and feed updates when initiatives are created, backed, or modified.

src/applications/fund/editor · high confidence

Introduce EditEngine as a unified, configurable framework for object creation and editing

This change introduces the EditEngine architecture, replacing hard-coded, ad-hoc edit forms with a unified, configurable system for creating and modifying objects. The new framework allows applications to define and customize edit forms, supporting features like field locking, subtype-based behavior, and MFA requirements. It provides a standardized API for both web and Conduit interactions, enabling consistent editing experiences across the platform and allowing administrators to configure global defaults and form behaviors.

src/applications/transactions/editengine · high confidence

Introduce EditEngine field and action types for comment actions

This change adds a new set of EditEngine components in the \src/applications/transactions/editfield\ and \src/applications/transactions/commentaction\ directories to support structured comment actions. It introduces an abstract \PhabricatorEditEngineCommentAction\ base class and specific action types for checkboxes, columns, points, selects, static text, and tokenizers, along with corresponding edit field classes (e.g., \PhabricatorCheckboxesEditField\, \PhabricatorSelectEditField\, \PhabricatorTokenizerEditField\) that wire these actions to the UI. This enables applications to define and render complex, grouped, and conflict-aware actions (like 'Accept' or 'Reject') within the EditEngine framework rather than using hard-coded ad-hoc definitions.

src/applications/transactions/editfield · high confidence

Introduce EditEngine-based editors for Diffusion commits, repositories, and URIs

This change adds new EditEngine implementations for Diffusion objects, providing a unified, modern interface for managing repositories, commits, and repository URIs. The DiffusionRepositoryEditEngine handles repository creation and editing, including allocating new repositories to random cluster services when in cluster mode. The DiffusionCommitEditEngine allows users to edit commit details, specifically enabling the addition and removal of auditors and the selection of commit actions via a stacked comment interface. The DiffusionURIEditEngine and DiffusionURIEditor provide a new way to create and edit repository URIs, supporting various VCS types (Git, Mercurial, Subversion) and handling credential management securely by clearing credentials when protocol or domain changes occur. These editors replace older, ad-hoc editing mechanisms with a consistent, transaction-based approach.

src/applications/diffusion/editor · high confidence

Introduce EditEngine-based forms and explicit member management for Phortune accounts and merchants

Phortune accounts and merchants now use the EditEngine framework for creation and editing, providing structured forms for account name, billing details, and merchant contact information. This change introduces explicit member management, allowing users to add or remove account and merchant managers via edge transactions, with validation that prevents self-removal. Additionally, new edge types define the relationships between accounts, merchants, and their members, and dedicated editors handle transaction validation and email notifications for these entities.

src/applications/phortune/editor · high confidence

Introduce Elasticsearch and Ferret fulltext search engines

Users can now utilize two new fulltext search backends: an Elasticsearch engine (configured via the 'elasticsearch' identifier) and a Ferret engine (configured via the 'mysql' identifier). The Elasticsearch implementation provides advanced query parsing, relevance-based sorting, and support for auxiliary constraints like author, project, and status filters. The Ferret engine enables global fulltext queries across multiple object types, returning combined results sorted by overall relevance. This change establishes the underlying infrastructure for these search capabilities within the fulltext storage layer.

src/applications/search/fulltextstorage · high confidence

Introduce Fact Daemon for background data aggregation

Added PhabricatorFactDaemon, a new background service that iterates through installed applications to collect and store factual data points. The daemon processes objects using registered fact engines, manages processing cursors to track progress, and batches updates to the database, including support for hibernation to optimize resource usage when idle.

src/applications/fact/daemon · high confidence

Introduce Facts application for data analysis

A new 'Facts' application has been added to the Utilities group, providing a dedicated interface to chart and analyze data. This change introduces the application entry point with base URI /fact/ and registers routes for a home view, interactive charts (supporting dynamic drawing and resizing), and a specific page to examine the facts generated by individual objects.

src/applications/fact/application · high confidence

Introduce Favorites application entry point

The system now includes a dedicated Favorites application module, exposing the '/favorites/' base URI and registering the 'PhabricatorFavoritesMenuItemController' to handle menu item routes. This establishes the foundational application structure for the Favorites feature, although the application is currently marked as non-launchable from the main navigation.

src/applications/favorites/application, src/applications/xhprof/application · high confidence

Introduce Favorites engine for customizable profile menu items

The Favorites application now includes a dedicated engine (PhabricatorFavoritesProfileMenuEngine) that allows the profile menu to be customized. This engine automatically populates the menu with 'Quick Create' items derived from all registered edit engines, sorted by their defined order, and appends a divider followed by a link to manage favorites. This change shifts the profile menu behavior to support dynamic, configurable content rather than static defaults.

src/applications/favorites/engine · high confidence

Introduce Favorites menu item controller

Added a new controller (PhabricatorFavoritesMenuItemController) that handles requests for the Favorites menu item. It retrieves the installed PhabricatorFavoritesApplication and uses PhabricatorFavoritesProfileMenuEngine to build the response for the viewer's profile menu.

src/applications/favorites/controller · high confidence

Introduce Ferret fulltext search engine

Adds a new fulltext search engine implementation called Ferret, which uses basic MySQL primitives to index and search content. This engine provides a structured schema for documents, fields, and ngrams, and includes logic for tokenization, stemming, and relevance sorting. It allows applications to implement the FerretInterface to integrate this new search capability, supporting features like ngram extraction and common term removal to improve search performance and accuracy.

src/applications/search/ferret · high confidence

Introduce Ferret-based fulltext search for Maniphest tasks

This change adds a new search engine implementation for Maniphest tasks, replacing the previous indexing approach with a Ferret-based fulltext engine. The new \ManiphestTaskFulltextEngine\ handles document construction by indexing task titles, descriptions, and relationships (author, owner, open/closed status), while \ManiphestTaskFerretEngine\ wires this into the application's search infrastructure. Users will benefit from improved fulltext search capabilities for tasks, leveraging the new Ferret engine's primitives.

src/applications/maniphest/search · high confidence

Introduce Flags application configuration

The system now includes a dedicated application class for the Flags feature, defining its name as 'Flags', short description as 'Personal Bookmarks', base URI as '/flag/', and icon as 'fa-flag'. This registration establishes the application's identity, routing structure (including list, view, edit, and delete endpoints), and event listeners within the application registry.

src/applications/flag/application · high confidence

Introduce Fund application for backing initiatives

The Fund application is now available, allowing users to back initiatives. This change introduces the core application class, defines the '/fund/' base URI, and registers routes for listing, creating, editing, closing, and backing initiatives, as well as viewing backers. The application is marked as a prototype and includes remarkup rules and search document types for initiatives.

src/applications/fund/application · high confidence

Introduce Fund application for backing initiatives

The Fund application is now available, allowing users to create, view, and back funding initiatives. This change introduces a new controller layer (src/applications/fund/controller) that provides endpoints for listing initiatives, viewing individual initiative details with transaction timelines, editing initiatives, closing or reopening them, and managing the backing process. Users can now contribute funds to open initiatives via a payment flow integrated with Phortune, and view a list of backers for each initiative.

src/applications/fund/controller · high confidence

Introduce Fund initiative and backer data models

This change adds the core storage layer for the Fund application, introducing \FundInitiative\ and \FundBacker\ data objects. \FundInitiative\ defines the structure for crowdfunding projects, including fields for name, description, risks, status, and total funding amount, along with policy controls for viewing and editing. \FundBacker\ tracks individual contributions, linking backers to initiatives and recording the contribution amount and status. The entry also includes the base \FundDAO\ class, transaction wrappers for handling changes to initiatives and backers, and the schema specification required to create the necessary database tables.

src/applications/fund/storage · high confidence

Introduce GitHub event parsing and URI generation

Added NuanceGitHubRawEvent to parse raw GitHub event payloads, distinguishing between issue and pull request events, extracting repository names, issue/PR numbers, and comments, and generating appropriate GitHub URIs with anchors for linking to specific events.

src/applications/nuance/github · high confidence

Introduce Guides application for short tutorials

Users can now access a new 'Guides' application under Utilities, featuring short tutorials organized into modules. The application provides a dedicated navigation sidebar to browse enabled modules and renders module content using a CMS-style view layout.

src/applications/guides/application, src/applications/guides/controller · high confidence

Introduce Harbormaster Autoplan configuration for Arcanist

Users can now configure Harbormaster to automatically plan builds using Arcanist tools. This change introduces a new \HarbormasterBuildAutoplan\ base class and a specific \HarbormasterBuildArcanistAutoplan\ implementation that registers the 'arcanist' plan key with the display name 'arc lint + arc unit'. The system uses \PhutilClassMapQuery\ to dynamically discover available autoplans, allowing Harbormaster to automatically detect and utilize this Arcanist-based build configuration.

src/applications/harbormaster/autoplan · high confidence

Introduce Harbormaster artifact types for files, URIs, and Drydock leases

This change adds a new artifact abstraction layer to Harbormaster, introducing specific artifact types that allow build results to reference external resources. Users can now create artifacts for files (HarbormasterFileArtifact), URIs (HarbormasterURIArtifact), and Drydock leases including working copies and hosts (HarbormasterWorkingCopyArtifact, HarbormasterHostArtifact). The URI artifact specifically supports external links with a 'noreferrer' rel attribute and validates protocols against configuration, while the Drydock lease artifacts enable builds to interact with leased resources, ensuring proper cleanup via release commands.

src/applications/harbormaster/artifact · high confidence

Introduce Harbormaster build execution workers

Added new worker classes to handle the execution and management of Harbormaster builds. HarbormasterBuildWorker initiates or continues builds and updates buildables. HarbormasterTargetWorker executes individual build targets, managing their status transitions (e.g., from pending to building, handling yields, failures, or aborts) and ensuring build steps can run in parallel. HarbormasterLogWorker finalizes build logs by processing byte offsets, compressing logs, and uploading them as files. HarbormasterWorker serves as the abstract base class for these workers, ensuring they run with omnipotent user privileges.

src/applications/harbormaster/worker · high confidence

Introduce Harbormaster build storage schema

This change adds the core data models for the Harbormaster build system, including entities for builds, build targets, build logs (with chunked storage and compression), build artifacts, and structured lint and unit test messages. These classes define the database schema, serialization, and policy interfaces required to persist and query build execution data, laying the foundation for build tracking, logging, and result reporting.

src/applications/harbormaster/storage/build · high confidence

Introduce Harbormaster buildable interfaces for CI integrations

Harbormaster now defines specific interfaces to support external CI systems, allowing buildable objects to expose integration-specific data. The new HarbormasterCircleCIBuildableInterface enables CircleCI integration by providing methods to retrieve the GitHub repository URI and build identifiers, while HarbormasterBuildkiteBuildableInterface supports Buildkite by exposing branch and commit information. These interfaces are part of the broader HarbormasterBuildableInterface contract, which also standardizes how build variables and display PHIDs are accessed for human-readable context in the UI.

src/applications/harbormaster/interface · high confidence

Introduce Harbormaster storage schema and data models

This change establishes the foundational database schema and data access objects for the Harbormaster continuous integration application. It adds core storage classes including HarbormasterBuildable for tracking build targets and their statuses, HarbormasterBuildMessage for handling asynchronous messages from external systems, and HarbormasterBuildTransaction for managing build state changes. The update also includes the base HarbormasterDAO class, schema specifications for database table generation, and utility classes like HarbormasterString for efficient string indexing, enabling the application to persist and query build-related data.

src/applications/harbormaster/storage · high confidence

Introduce Harbormaster webhook integrations for Buildkite and CircleCI

Harbormaster now supports external CI integrations via new webhook controllers for Buildkite and CircleCI. These controllers listen for build completion events from the respective services, validate the incoming requests using configured tokens, and automatically update the status of the corresponding Harbormaster build targets by sending pass or fail messages through the Conduit API.

src/applications/harbormaster/controller · high confidence

Introduce Help application with dedicated documentation routes

The Help application is now a distinct module that registers itself in the main menu and provides specific routes for keyboard shortcuts and application documentation. Users can now access help documentation for specific applications via the /help/documentation/{application}/ path, and keyboard shortcut information is available at /help/keyboardshortcut/. The application is marked as unlisted and cannot be uninstalled, ensuring it remains a core part of the interface.

src/applications/help/application · high confidence

Introduce HeraldRuleTypeConfig for rule type definitions

A new HeraldRuleTypeConfig class has been added to centralize the definition of Herald rule types (Global, Object, Personal) and provide a mapping to their user-facing labels. This config class serves as the source of truth for available rule scopes within the Herald application.

src/applications/herald/config · high confidence

Introduce JX.Quicksand for client-side navigation

Adds the JX.Quicksand library to enable client-side navigation, allowing the application to capture link clicks and browser history events to load content via AJAX without full page reloads. This preserves persistent UI elements during navigation, though it requires the application to handle the resulting asynchronous content updates.

webroot/rsrc/externals/javelin · high confidence

Introduce Legalpad document creation and editing workflow

Users can now create and edit Legalpad documents through a dedicated interface. The new \LegalpadDocumentEditEngine\ provides a form for entering a document title, preamble, and body text, along with optional signature configuration (specifying who should sign and whether signing is required for login). The \LegalpadDocumentEditor\ handles the persistence of these changes, automatically versioning documents upon modification, tracking contributors, and sending email notifications to the creator and editor with a link to the document details.

src/applications/legalpad/editor · high confidence

Introduce Meme Macro Engine

Adds the PhabricatorMemeEngine class, enabling users to generate meme images by overlaying custom text on template images via the {meme ...} macro. The engine handles caching of transformed assets, supports both ImageMagick and GD backends for image processing, and ensures that templates without text are returned unmodified to save processing resources.

src/applications/macro/engine · high confidence

Introduce Multimeter application skeleton

Adds the application registration for the new 'Multimeter' performance sampling tool, making it accessible under the /multimeter/ base URI. The application is registered as a prototype within the Developer group, uses a motorcycle icon, and links to the Multimeter User Guide for documentation.

src/applications/multimeter/application · high confidence

Introduce Multimeter performance sampling application

Adds the Multimeter application, a new performance sampling tool that allows users to browse and group event samples by dimensions such as type, request, viewer, context, host, and label. The controller logic implements a query interface that aggregates sample data over the last 24 hours, calculating average and total resource costs, and supports filtering by these dimensions with specific privacy masking for non-admin users viewing event viewer data.

src/applications/multimeter/controller · high confidence

Introduce Multimeter performance sampling control layer

Added the MultimeterControl class, which serves as the central coordinator for the new Multimeter performance sampling application. This component manages the sampling lifecycle by handling sample rates, pausing/resuming data collection, and creating event records. It also handles the persistence of these events to the database, ensuring that writes are guarded against read-only states and that context data (such as the requesting viewer and environment) is correctly associated with each sampled event.

src/applications/multimeter/data · high confidence

Introduce Nuance application for high-volume task queues

A new 'Nuance' application is added to the platform, providing a web UI for managing high-volume task queues. This change introduces the application entry point, defines its base URI at /nuance/, and registers controllers for listing, viewing, editing, and performing actions on Nuance items, sources, and queues. It also establishes default policy capabilities for viewing and editing sources, marking the application as a prototype.

src/applications/nuance/application · high confidence

Introduce Nuance command execution framework and trash action

This change adds the core infrastructure for executing commands on Nuance items, including the abstract \NuanceCommandImplementation\ base class which handles transaction queuing and item editing, and the \NuanceItemCommandSpec\ for defining command metadata. It also introduces the \NuanceTrashCommand\, which allows users to immediately close form items by moving them to the trash, leveraging the new immediate application capability.

src/applications/nuance/command · high confidence

Introduce Nuance item update worker with command execution and locking

Added NuanceWorker and NuanceItemUpdateWorker classes to handle background processing of Nuance items. The update worker loads items, updates them via their implementation, routes items to default queues if they are in the routing status, and executes pending commands. Command execution is protected by global locks to prevent race conditions, ensuring commands are executed exactly once and status transitions (issued -\> executing -\> done/failed) are handled correctly.

src/applications/nuance/worker · high confidence

Introduce OAuth Server application with client management and disabled state support

The OAuth Server is now available as a distinct application, providing routes for client listing, authentication, token issuance, and client editing. Users can now manage OAuth clients, including the ability to disable them rather than destroying them, and view client secrets through a dedicated controller. The application is marked as a prototype and is grouped under administration, with specific capabilities for creating clients restricted to admins.

src/applications/oauthserver/application · high confidence

Introduce PHID type classes for Harbormaster entities

This change adds PHID type classes for Harbormaster entities, including Build, Build Plan, Build Step, Build Target, Buildable, Build Log, and Build Artifact. These classes provide the necessary infrastructure for handling PHIDs (Phabricator IDs) for these entities, enabling better integration with Phabricator's object system. Users will benefit from improved object handling and referencing within the Harbormaster application.

src/applications/harbormaster/phid · high confidence

Introduce PHID type for MetaMTA Mail objects

Added PhabricatorMetaMTAMailPHIDType to enable unique PHID identification for MetaMTA Mail objects. This allows mail items to be referenced, queried, and displayed with handles (e.g., 'Mail 123') within the Phabricator ecosystem, integrating them into the object graph alongside other entities.

src/applications/metamta/phid · high confidence

Introduce PHID type for Passphrase Credentials

A new PHID type, PassphraseCredentialPHIDType, has been added to support Passphrase Credential objects. This enables credentials to be handled as first-class objects within the system, allowing them to be queried, loaded by name (e.g., K123), and displayed with specific handles and URIs in the UI.

src/applications/passphrase/phid · high confidence

Introduce PHID type handlers for Drydock entities

This change adds PHID type handler classes for Drydock entities (authorizations, blueprints, leases, repository operations, and resources), enabling these objects to be properly identified, queried, and displayed with handles in the system.

src/applications/drydock/phid · high confidence

Introduce PHID types for Fund initiatives and backers

Added PHID type handlers for Fund initiatives (FITV) and backers (FBAK), enabling the system to resolve, display, and query these new entities via their unique identifiers. This allows users to reference and interact with Fund initiatives and backers in global search and other handle-based contexts.

src/applications/fund/phid · high confidence

Introduce PHID types for new authentication entities

This change adds PHID type definitions for several new authentication-related objects, including Auth Factors, MFA Providers, Auth Challenges, Contact Numbers, Auth Invites, Auth Messages, Auth Passwords, Public SSH Keys, and Sessions. These types enable the system to uniquely identify and manage these entities, supporting features like SMS-based MFA, configurable MFA providers, and enhanced session management.

src/applications/auth/phid · high confidence

Introduce PHID types for project columns, triggers, and projects

This change adds the PHID type definitions for Project Columns, Project Triggers, and Projects themselves within the project application. Users will now see proper handles, icons, and URIs for these entities in comments and notifications: project columns display with a 'fa-columns' icon and link to their workboard view, triggers appear with an 'fa-exclamation-triangle' icon, and projects resolve via their slug (e.g., \#slug) or PHID if no slug exists, including support for case-insensitive slug matching in markup.

src/applications/project/phid · high confidence

Introduce PHID types for repository entities

This change adds PHID type definitions for core repository objects, including Commits (CMIT), Identities (RIDT), Refs (RREF), and various events like Pull, Push, and Sync. This enables these entities to be uniquely identified and referenced across the platform. Specifically, commit handles now display rewritten commit information when available, and repository handles are marked as closed when the repository is inactive.

src/applications/repository/phid · high confidence

Introduce PHPAST application with dedicated navigation and routing

A new PHPAST application has been added to the platform, providing a visual PHP parser interface. This change registers the application under the Developer group with the display name 'PHPAST' and assigns it the 'fa-ambulance' icon. It establishes the base URI at '/xhpast/' and configures specific routes for running parsers, viewing framesets, inputs, trees, and streams, making the PHPAST functionality accessible through the main application navigation.

src/applications/phpast/application · high confidence

Introduce Packages application for publishing software

A new 'Packages' application has been added to the Utilities group, enabling users to publish and manage software applications and extensions. This change introduces the core application structure, including default capabilities for creating publishers and managing packages (with admin-only creation and restricted default edit/view policies), and registers the necessary routes for listing, viewing, and editing publishers, packages, and their versions.

src/applications/packages/application · high confidence

Introduce Passphrase credential management with locking and Conduit access controls

This change introduces the core controller and transaction logic for the Passphrase application, enabling users to create, edit, and manage credentials (such as SSH keys and tokens). A key behavioral addition is the ability to permanently lock credentials, which hides the secret and revokes programmatic access via the Conduit API. The system also tracks when a secret is viewed and allows administrators to explicitly permit or deny Conduit access for specific credentials, ensuring that sensitive data is only exposed to authorized programmatic consumers.

src/applications/passphrase/controller · high confidence

Introduce Passphrase key classes for credential management

New classes (PassphraseAbstractKey, PassphrasePasswordKey, PassphraseSSHKey) are added to the passphrase/keys directory to provide a structured way to load and validate credentials. PassphrasePasswordKey exposes password secrets, while PassphraseSSHKey handles SSH private keys, including writing them to temporary files when necessary and ensuring they are cleaned up. This change enables applications to securely retrieve and use credentials stored in the Passphrase system.

src/applications/passphrase/keys · high confidence

Introduce Paste Embed View with configurable line count and syntax highlighting

A new PasteEmbedView class has been added to render paste content as an embeddable widget. This view allows users to configure the number of visible lines (defaulting to 24) and apply specific syntax highlighting ranges. The embedded code block automatically disables the 'highlight on click' interaction and includes a header linking to the full paste detail page.

src/applications/paste/view · high confidence

Introduce Paste application storage layer with transactional editing and policy controls

This change adds the core storage infrastructure for the new Paste application, including the PhabricatorPaste entity, its DAO, and schema specifications. It enables users to create, edit, and archive pastes with configurable view and edit policies, while supporting features like language selection, file attachments, and subscription notifications. The implementation includes a transactional system for tracking changes (title, content, language) and sending relevant email notifications, as well as integration with Spaces, projects, and search capabilities.

src/applications/paste/storage · high confidence

Introduce People application with user management and profile capabilities

The People application is now available, providing core infrastructure for user accounts and profiles. Administrators can manage user lifecycles, including creating, inviting, approving, disabling, empowering, deleting, and renaming users, with specific capabilities (PeopleCreateUsersCapability, PeopleDisableUsersCapability) defaulting to admin-only access. User profiles now support viewing activity logs, badges, tasks, commits, revisions, and editing profile pictures, all accessible via dedicated routes under /people/ and /p/\<username\>/.

src/applications/people/application · high confidence

Introduce Phabricator-specific guidance engine and context classes

This change adds a new set of classes to the \guides\ and \people\ applications to support a Phabricator-specific guidance system. It introduces \PhabricatorGuidanceContext\ as the base context, \PhabricatorGuidanceEngine\ to orchestrate guidance generation via extensions, \PhabricatorGuidanceEngineExtension\ as the abstract base for guidance providers, and \PhabricatorGuidanceMessage\ to represent individual guidance items with severity and priority. Additionally, \PhabricatorPeopleCreateGuidanceContext\ is added to provide a specific context for people creation guidance. These classes form the backend infrastructure for displaying contextual guidance messages within the Phabricator interface.

src/applications/guides/guidance, src/applications/people/guidance · high confidence

Introduce PhabricatorApplicationTransactionFeedStory for feed rendering

Added a new \PhabricatorApplicationTransactionFeedStory\ class to handle the rendering and logic for transaction-based feed stories. This component determines visibility in both the main feed and notifications by checking individual transaction hide flags, retrieves primary object and transaction details for display, and manages the rendering of titles, bodies, and author information using application icons and user images.

src/applications/transactions/feed · high confidence

Introduce PhabricatorFeedStory for unified event rendering

The new PhabricatorFeedStory class centralizes the loading, policy enforcement, and rendering of feed events. It allows a single event (such as a comment) to be represented consistently across different channels like the main feed, notifications, and realtime alerts. The implementation handles loading associated objects and handles, enforces object policies to ensure users only see visible content, and processes Remarkup markup for display.

src/applications/feed/story · high confidence

Introduce PhabricatorFeedStoryNotification storage class

Added a new storage class, PhabricatorFeedStoryNotification, to handle notification records for feed stories. This class defines the database schema for tracking user-specific story notifications, including fields for chronological ordering and view status, and provides a method to mark notifications as viewed while clearing the associated user notification count cache.

src/applications/notification/storage · high confidence

Introduce PhabricatorHomeApplication for Home page configuration

The Home page is now backed by a dedicated \PhabricatorHomeApplication\ class, which defines its base URI as \/home/\, sets the display name to 'Home' with the short description 'Command Center', and assigns the 'fa-home' icon. This class also configures the routing to direct requests to \PhabricatorHomeMenuItemController\ and marks the application as non-launchable with a specific application order.

src/applications/home/application · high confidence

Introduce PhabricatorPHID class for generating system-level PHIDs

Added the PhabricatorPHID class to provide a dedicated mechanism for generating PHIDs for the Phabricator system itself. This new class includes a generateNewPHID method that creates unique identifiers with a 20-character random suffix for standard types and a 15-character suffix for subtypes, ensuring distinct naming conventions for system objects.

src/applications/phid/storage · high confidence

Introduce PhabricatorPolicyQuery for centralized policy loading

A new PhabricatorPolicyQuery class has been added to centralize the loading and resolution of policy objects. This query supports both global policies (Public, All Users, Administrators, No One) and object-specific policies, handling the distinction between rule-based policies and handle-based policies. It provides static methods to load policies for a given object and render their descriptions with capability links, streamlining how policy information is retrieved and presented to users.

src/applications/policy/query · high confidence

Introduce Phame application registration with blog and post routing

This change registers the Phame application within the system, defining its base URI (/phame/), icon, and description as 'Internal and External Blogs'. It establishes the core routing structure for managing blogs and posts, including controllers for listing, editing, viewing, publishing, unpublishing, moving, and archiving both blogs and individual posts. The application also supports live blog URLs, custom profile and header images for blogs, and integrates with the remarkup system for post content. Additionally, it sets default creation policies for blogs and adds a quicksand URI blacklist for live blog paths.

src/applications/phame/application · high confidence

Introduce Phame blog and post query engines with search and policy support

This change adds the core query and search infrastructure for the Phame blogging application, enabling users to browse, search, and filter blogs and posts. It introduces PhameBlogQuery and PhamePostQuery classes that enforce policy controls (e.g., visibility, access rights) and support filtering by status (active/archived for blogs; published/draft/archived for posts), domain, and publication date. The new PhameBlogSearchEngine and PhamePostSearchEngine integrate these queries into the global application search, allowing users to find blogs and posts via the main search interface with filters for status and visibility. Additionally, transaction queries (PhameBlogTransactionQuery, PhamePostTransactionQuery) are added to support viewing change history for blogs and posts.

src/applications/phame/query · high confidence

Introduce Phame blog architecture with homepage, live views, and URI canonicalization

The Phame application now supports a structured blog system. A new PhameHomeController provides a landing page that displays recent published posts from active blogs, lists available blogs, and shows draft posts for logged-in users. The PhameLiveController handles public-facing blog and post views, introducing logic to canonicalize URIs by redirecting to the correct slug and blog ID when mismatches are detected, ensuring consistent URLs. It also distinguishes between internal and external (custom domain) views, adjusting breadcrumbs and visibility rules accordingly (e.g., only showing published posts on external domains).

src/applications/phame/controller · high confidence

Introduce Phame storage layer for blogs and posts

This change adds the core storage classes for the Phame blogging application, including PhameBlog and PhamePost entities, their associated transaction objects, and the database schema specification. Users can now have blogs with configurable domains, policies, and images, and posts with visibility controls, modular transactions, and full-text search support.

src/applications/phame/storage · high confidence

Introduce Phlux Variable Editor for managing variables

A new PhluxVariableEditor class has been added to handle editing operations for Phlux Variables. This editor supports transactions for editing variable keys and values, as well as viewing and editing policies, enabling users to modify these specific attributes through the application's transaction system.

src/applications/phlux/editor · high confidence

Introduce Phlux application as a key/value configuration store

A new application named 'Phlux' has been added to the system, providing a key/value configuration store accessible at the /phlux/ base URI. This utility is categorized under the Utilities group and is marked as a prototype, indicating it is in an early stage of development. The application includes routes for listing, viewing, and editing configuration keys, and utilizes a copy icon for its interface representation.

src/applications/phlux/application · high confidence

Introduce Phlux application for managing variables

Adds the Phlux application controllers (PhluxController, PhluxEditController, PhluxListController, PhluxViewController) which provide a new UI for creating, editing, listing, and viewing variables. Users can now manage variable keys (validated as lowercase alphanumeric with dots and hyphens) and JSON values, with policy controls for viewing and editing, and a transaction timeline for history.

src/applications/phlux/controller · high confidence

Introduce Phlux application query classes

Added new query classes for the Phlux application, including PhluxTransactionQuery and PhluxVariableQuery. These classes enable retrieving Phlux transactions and variables with support for filtering by IDs, keys, and PHIDs, as well as cursor-based pagination and ordering.

src/applications/phlux/query · high confidence

Introduce Phlux application storage layer

Adds the initial database storage infrastructure for the new Phlux application, including the PhluxDAO base class, PhluxVariable entity with JSON-serialized value support and unique key constraints, PhluxTransaction for tracking variable creation and updates, and PhluxSchemaSpec for edge table definitions.

src/applications/phlux/storage · high confidence

Introduce Pholio application for image mockups

Adds the Pholio application, enabling users to create and manage image mockups (PholioMock) and associated images (PholioImage). This includes storage classes for mockups with open/closed statuses, image history tracking via replacement chains, and modular transaction support for tracking changes to names, descriptions, and image replacements. The feature also supports inline comments on images, subscription notifications, and policy-based access control for viewing and editing mockups.

src/applications/pholio/storage · high confidence

Introduce Pholio mock management controllers

Adds the core controller layer for the new Pholio image mock application. This includes PholioController as the base, along with specific handlers for listing mocks (PholioMockListController), viewing mock details with image grids and timelines (PholioMockViewController), editing mock properties and images (PholioMockEditController), managing mock status via archive/close actions (PholioMockArchiveController), handling mock-level comments (PholioMockCommentController), and supporting inline image comments (PholioInlineController, PholioInlineListController) and image uploads (PholioImageUploadController).

src/applications/pholio/controller · high confidence

Introduce Phortune application for accounts and billing

Adds the Phortune application, a new module for managing accounts and billing. It registers a suite of controllers and routes covering payment methods, carts, orders, charges, subscriptions, and merchant management, along with an external portal for viewing orders and invoices. The application is marked as a prototype and includes specific capabilities for merchant accounts to receive payments.

src/applications/phortune/application · high confidence

Introduce Phortune storage layer for purchasing entities and transactions

This change establishes the core data model for the Phortune payment application by adding storage classes for accounts, merchants, carts, charges, payment methods, products, purchases, and subscriptions. It enables users to manage purchasing entities with member and merchant relationships, track the full lifecycle of orders through cart statuses (Building, Ready, Purchasing, Charged, Hold, Review, Purchased), and handle financial transactions including charges, refunds, and recurring billing triggers.

src/applications/phortune/storage · high confidence

Introduce PhortuneCurrency type for USD monetary values

This change introduces a new PhortuneCurrency type to handle monetary values within the Phortune application. The type enforces storage of amounts in integer cents to avoid floating-point precision issues, supports only USD, and provides methods for parsing user input, formatting for display (e.g., "$10.00 USD"), and performing arithmetic operations like addition and subtraction. A corresponding serializer is also added to handle persistence of these currency objects in the database.

src/applications/phortune/currency · high confidence

Introduce Phrequent application registration

The Phrequent application is now registered in the system, providing the core metadata required for it to appear in the application navigation and be accessible via the '/phrequent/' base URI. This includes its display name ('Phrequent'), short description ('Track Time Spent'), icon ('fa-clock-o'), and routing definitions for list and track controllers. The application is marked as a prototype and grouped under Utilities.

(repo-wide) · high confidence

Introduce Phrequent time tracking with start/stop dialogs

This change adds the core controller logic for the Phrequent time-tracking feature. The new PhrequentTrackController provides user-facing dialogs to start and stop tracking time on specific objects, including validation to prevent future timestamps and ensuring stop times occur after start times. It also allows users to add notes when stopping a timer and displays the current start time during the stop action. The PhrequentListController delegates to the standard application search infrastructure, while the base PhrequentController sets up the side navigation menu.

src/applications/phrequent/controller · high confidence

Introduce Phurl URL Shortener Application

Adds the Phurl application, a new URL shortener utility. This change registers the application with the base URI '/phurl/', defines routing for short URLs (via '/U' and '/u' paths) and list/edit views, and integrates remarkup rules to allow linking to short URLs in text. It also configures custom capabilities for creating new short URLs and sets up specific routes for status, favicon, and robots.txt handling on short sites.

src/applications/phurl/application · high confidence

Introduce Phurl URL management and viewing controllers

This change adds the core controller layer for the Phurl application, enabling users to view, edit, and list shortened URLs. The new controllers handle public redirections for short links, display detailed URL information with validity warnings, provide a 'Visit URL' action in the header, and integrate the EditEngine for managing URL properties and comments.

src/applications/phurl/controller · high confidence

Introduce Phurl URL storage and transaction schema

This change adds the foundational storage layer for the Phurl application, introducing the PhabricatorPhurlURL data object and its associated schema. Users can now have URLs tracked with specific names, aliases, and descriptions, all of which are managed through a modular transaction system that records history and sends notifications for changes.

src/applications/phurl/storage · high confidence

Introduce Portal management controllers

Added controller classes for the new Portals feature, enabling users to list, view, and edit portals. The list controller exposes a public view of all portals and includes a navigation crumb to the edit interface, while the view controller retrieves specific portal details and renders their profile menus and transaction timelines. The edit controller delegates to an engine to handle portal modification, and the base controller establishes the standard 'Portals' navigation breadcrumb.

src/applications/dashboard/controller/portal · high confidence

Introduce SSH-based VCS access and device authentication

Adds new scripts in scripts/ssh to enable version control operations (Git, Mercurial, Subversion) over SSH. ssh-auth.php generates authorized keys for sshd, supporting both user keys and trusted Almanac device keys for cluster-to-cluster communication. ssh-connect.php acts as a wrapper for VCS clients to handle SSH options and port parsing. ssh-exec.php executes authenticated SSH commands, logging activity and enforcing security policies such as forbidding disabled devices.

scripts/ssh · high confidence

Introduce Slowvote application with poll management capabilities

This change adds the PhabricatorSlowvoteApplication class, registering the 'Slowvote' application under the Utilities group. It defines the base URI as '/vote/', sets the application icon to 'fa-bar-chart', and provides a short description 'Conduct Polls'. The application exposes routes for listing, creating, editing, voting on, commenting on, and closing polls, handled by dedicated controllers. It also configures a custom capability for setting the default view policy for new polls, allowing users to specify a template for visibility settings.

src/applications/slowvote/application · high confidence

Introduce Slowvote query and search infrastructure

This change adds the core query and search engine classes for the Slowvote application, enabling users to browse, filter, and search for polls. The new PhabricatorSlowvoteQuery class allows filtering polls by ID, PHID, author, status, and viewer vote status, while also loading associated options and choices. The PhabricatorSlowvoteSearchEngine provides a user-facing search interface with built-in queries for 'Open Polls', 'All Polls', 'Authored', and 'Voted In', along with custom search fields for authors, vote status, and poll status. A transaction query class is also added to support loading poll-related transactions.

src/applications/slowvote/query · high confidence

Introduce Space namespace PHID type

Added PhabricatorSpacesNamespacePHIDType to define the 'Space' object type (TYPECONST 'SPCE') within the Spaces application. This enables the system to resolve Space PHIDs, load their handles (including monogram, name, and URI), and support named object lookups via the 'S' prefix pattern. It also integrates Space archival status into handle display and links the type to the PhabricatorSpacesApplication.

src/applications/spaces/phid · high confidence

Introduce Spaces application for managing policy namespaces

Adds a new Spaces application that allows administrators to create and manage policy namespaces (Spaces). Users with the 'Can Create Spaces' capability can define new spaces with a name, description, and default view/edit policies. The application provides controllers for listing spaces, editing their properties, and viewing details. It also introduces the ability to archive and activate spaces; archiving hides existing objects from query results by default, while activating restores them. Access is controlled via capabilities, and users without access to any space see a tailored 'No Access' message depending on whether they are logged in.

src/applications/spaces/controller, src/applications/spaces/storage · high confidence

Introduce Spaces application with policy templates and archival support

The Spaces application is now available, providing a new area at /spaces/ for managing policy namespaces. This update introduces a dedicated remarkup rule for Spaces, allows spaces to be archived via new routes, and configures default view and edit policies using specific namespace templates for newly created spaces.

src/applications/spaces/application · high confidence

Introduce Subscriptions Editor for managing user subscriptions

A new PhabricatorSubscriptionsEditor class has been added to handle subscription state changes for subscribable objects. This editor allows users to explicitly subscribe, implicitly subscribe (with suppression if previously unsubscribed), or unsubscribe specific users (identified by PHIDs) from an object. The save operation resolves conflicts where a user is both subscribed and unsubscribed by prioritizing unsubscription, and updates the underlying edge storage to reflect the final subscription state.

src/applications/subscriptions/editor · high confidence

Introduce Subscriptions application with edit, list, mute, and transaction history controllers

This change adds the core backend controllers for the new Subscriptions application, enabling users to manage their notification preferences for subscribable objects. The PhabricatorSubscriptionsEditController handles adding or removing subscriptions via AJAX, supporting both legacy objects and those implementing the ApplicationTransactionInterface. The PhabricatorSubscriptionsListController provides a public-facing dialog to view the list of subscribers for an object. The PhabricatorSubscriptionsMuteController allows users to mute or unmute notifications for specific objects, while the PhabricatorSubscriptionsTransactionController displays a dialog showing subscribers added or removed by a specific transaction. These controllers collectively provide the foundation for subscribing, unsubscribing, muting, and viewing subscription history for objects within the system.

src/applications/subscriptions/controller · high confidence

Introduce Subscriptions application with mute/unmute capability

A new Subscriptions application has been added, providing the core infrastructure for managing user subscriptions. This includes the ability to mute and unmute subscribable objects via a dedicated mute controller and route, alongside standard add/delete and list operations. The application registers its own event listeners and routes to support these subscription management features.

src/applications/subscriptions/application · high confidence

Introduce System application with dedicated routes for status, debugging, and favicon handling

A new PhabricatorSystemApplication class has been added to centralize system-level functionality. This change registers specific routes for system status (/status/), debugging (/debug/), favicon serving (/favicon.ico), robots.txt (/robots.txt), and object redirection (/object/...). It also introduces controllers for selecting text encoding, syntax highlighting, and viewing diffs as different document types (/services/), as well as a controller for handling read-only mode reasons (/readonly/). This consolidates these system-wide behaviors into a single application module.

src/applications/system/application · high confidence

Introduce Tokens application for awarding trinkets

A new 'Tokens' application has been added to the platform, providing functionality to award and acquire trinkets. This feature introduces a dedicated section accessible at /token/, including controllers for viewing given tokens, giving tokens to other users, and viewing token leaders. The application is categorized under Utilities and uses a thumbs-up icon for its interface.

src/applications/tokens/application · high confidence

Introduce Tokens application storage schema

Adds the foundational storage layer for the new Tokens application, including the \PhabricatorTokenDAO\ base class and specific entity classes (\PhabricatorTokensToken\, \PhabricatorTokenGiven\, \PhabricatorTokenCount\, \PhabricatorToken\). This introduces the \token\_token\ database table to manage token definitions (with active/archived status and image support) and tracks which objects have been awarded tokens, enforcing policy inheritance where viewed tokens reflect the object's policies while edit rights are restricted to the granting user.

src/applications/fact/storage, src/applications/tokens/storage · high confidence

Introduce Transactions application with dedicated routing and configuration endpoints

A new PhabricatorTransactionsApplication class has been added to define the Transactions application, registering its name and configuring it as non-launchable and non-uninstallable. The application exposes a comprehensive set of routes for managing transaction comments, including actions to edit, remove, view history, quote, view raw data, and see details for specific transaction PHIDs. It also provides pagination support via 'show older' and value controllers, inline remarkup preview capabilities, and a full suite of EditEngine configuration endpoints that allow administrators to manage form configurations, including sorting, reordering, setting defaults, locking, hiding, disabling, and configuring subtypes for edit and create forms.

src/applications/transactions/application · high confidence

Introduce \`bin/files\` script for managing file storage

A new \bin/files\ command-line script has been added to allow users to manage Phabricator file storage. This script dynamically loads and exposes workflows that extend \PhabricatorFilesManagementWorkflow\, providing a centralized entry point for file management tasks.

scripts/files · high confidence

Introduce abstract application configuration panel base class

Added PhabricatorApplicationConfigurationPanel, an abstract base class that defines the interface for application configuration panels. This class provides methods to set and retrieve the viewer and application context, generate panel URIs, and load all registered panel implementations using PhutilClassMapQuery. Subclasses must implement getPanelKey, shouldShowForApplication, buildConfigurationPagePanel, and handlePanelRequest to define specific panel behavior. A corresponding test case verifies the panel loading mechanism.

src/applications/meta/panel · high confidence

Introduce abstract base class for Lipsum generators

Added PhabricatorTestDataGenerator, an abstract base class that extends Phobject to provide shared utilities for Lipsum data generation. This class centralizes common functionality such as loading random PHIDs and users, rolling dice for random values, and constructing transactions, allowing specific generator implementations to inherit these helpers and focus on their unique object creation logic.

src/applications/lipsum/generator · high confidence

Introduce availability status indicators in typeahead tokens

The typeahead component now displays user availability status (such as 'away' or 'busy') via colored dots within tokenizer tokens and autocomplete results. This change adds a new \PhabricatorTypeaheadTokenView\ class that processes availability data from object handles, mapping partial availability to orange and no availability to red, and renders these indicators alongside the user icon and name for better context during selection.

src/applications/typeahead/view · high confidence

Introduce badge search and query capabilities

Users can now search for badges by name, filter by quality and status, and sort results by rarity (quality) in the application search engine. This change adds the underlying query classes (PhabricatorBadgesQuery, PhabricatorBadgesAwardQuery, etc.) that power these search and listing features, including support for cursor-based pagination and policy-aware access control.

src/applications/badges/query · high confidence

Introduce bin/cache command for managing caches

A new \bin/cache\ script has been added to allow users to manage Phabricator caches. This command automatically discovers and registers workflows that extend \PhabricatorCacheManagementWorkflow\, providing a centralized interface for cache operations.

scripts/cache · high confidence

Introduce block-based diff rendering for structured documents

The diff view now supports rendering changes in structured documents (such as Jupyter notebooks) as a series of blocks rather than raw line-by-line text. This change introduces new internal classes (PhabricatorDocumentEngineBlock, PhabricatorDocumentEngineBlockDiff, PhabricatorDocumentEngineBlocks) to manage block-level differences, allowing the system to group content into logical units, compute hashes for efficient comparison, and display changes in a two-up or one-up layout. Users will see diffs that respect the structure of the document, with unchanged context potentially folded and added/removed blocks clearly distinguished.

src/applications/files/diff · high confidence

Introduce built-in avatar and icon image generation

The system now supports generating default profile images and project icons on the fly. For user avatars, a new generator creates deterministic images based on the user's username, selecting from various icon packs, colors, and borders; it gracefully falls back to a static default image if the PHP GD extension is not installed. For projects, a new composer allows selecting from a set of built-in icons (such as Android, Apple, Bug, etc.) and colors to generate a 200px project icon. These changes provide a more personalized and visually consistent experience for user profiles and project representations without requiring manual image uploads.

src/applications/files/builtin · high confidence

Introduce centralized Drydock control script with dynamic workflow loading

A new \scripts/drydock/drydock\_control.php\ entry point has been added to manage Drydock software resources. This script initializes the environment with signal handling and dynamically discovers and registers management workflows by querying for classes extending \DrydockManagementWorkflow\ via \PhutilClassMapQuery\, rather than hardcoding them. This change establishes the CLI interface for the Drydock subsystem, allowing users to interact with resource management features through a unified command structure.

scripts/drydock · high confidence

Introduce centralized Files configuration options

Adds a new configuration class for the Files application, exposing settings to manage MIME type handling for viewable, image, audio, and video content, as well as file icon mappings and storage engine paths (local disk and S3). Most MIME type options are locked by default to prevent security issues like SSRF, while users can now configure the maximum file size for MySQL storage and specify local or S3 storage paths.

src/applications/files/config · high confidence

Introduce chatlog storage schema for channels and events

The chatlog application now persists data using new database tables for channels and events. Users can now have chat logs associated with specific channels, where each event records the author, type, and message content. Access to these logs is governed by channel-level view and edit policies, ensuring that permissions are inherited from the channel configuration.

src/applications/chatlog/storage · high confidence

Introduce command-line tool to revoke specific authentication credentials

Administrators can now use the \bin/auth revoke\ command to selectively invalidate specific types of authentication credentials, including SSH keys, Conduit API tokens, temporary tokens (such as password reset links), and active login sessions. This new revoker framework allows for targeted credential management without affecting unrelated authentication methods, providing granular control over user access and security posture.

src/applications/auth/revoker · high confidence

Introduce configurable build plan behaviors

Harbormaster build plans now support configurable behaviors that control how builds interact with code review and landing workflows. Users can configure options for holding drafts (preventing review until build completion), affecting buildables, warning on landing (alerting when changes land during ongoing or failed builds), and controlling restartability (allowing builds to be restarted always, if failed, or never). These behaviors provide finer control over the build lifecycle and integration with Phabricator's review and land processes.

src/applications/harbormaster/plan · high confidence

Introduce configurable project icon sets

Users can now customize the icons used to represent different project types (such as Project, Tag, Policy, Group, etc.) via a new configuration system. The diff introduces \PhabricatorProjectIconSet\ to manage these icon definitions and \PhabricatorProjectDropEffect\ to handle visual feedback during drag-and-drop operations, allowing the system to display specific icons, colors, and content previews based on the configured icon set.

src/applications/project/icon · high confidence

Introduce configurable workboard column triggers for tasks

Users can now define automated actions that execute when tasks are dragged onto or moved within workboard columns. This change adds a new trigger rule system (PhabricatorProjectTriggerRule) with several built-in capabilities: automatically adding or removing project tags, reassigning task ownership, changing task priority or status, and playing a notification sound. An editor UI allows users to configure these rules, and the system provides live previews of the effects during drag-and-drop operations. It also includes robust validation to distinguish between invalid rule formats and invalid values, ensuring that misconfigured triggers are clearly identified.

src/applications/project/trigger · high confidence

Introduce custom policy storage and management

Users can now define and persist custom policies beyond the standard global, user, project, and admin scopes. This change adds the \PhabricatorPolicy\ and \PhabricatorPolicyDAO\ classes to the storage layer, enabling the system to store policy rules as JSON, assign specific types (including a new custom type), and manage policy metadata like names, icons, and links. This provides the foundation for granular, object-specific permission rules that are saved to the database rather than being ephemeral or hardcoded.

src/applications/policy/storage · high confidence

Introduce customizable auth message types

This change adds a new extensible system for customizing instructional text and email body content across key authentication flows. Administrators can now tailor messages for specific scenarios, including the login screen, email login links, password setup, welcome emails, account linking prompts, username change requests, and wait-for-approval screens. This allows installations to provide context-specific guidance to users during onboarding and account recovery processes.

src/applications/auth/message · high confidence

Introduce daemon storage schema and lock logging

This change adds the database schema definitions for the daemon application, including tables to track daemon logs (with status, PID, and user context), daemon log events, and a new lock log to help debug where locks are being held. It also establishes the base DAO class for the daemon application.

src/applications/daemon/storage · high confidence

Introduce data models for Conduit API documentation and constant descriptions

Added two new data classes, ConduitAPIDocumentationPage and ConduitConstantDescription, to support the Conduit API method console. ConduitAPIDocumentationPage provides a structure for storing API documentation content, anchors, and icons, while ConduitConstantDescription models constant values with support for deprecation flags, enabling self-documenting checkbox constraints in the API interface.

src/applications/conduit/data · high confidence

Introduce database-backed markup cache with schema and DAO

Users now have a new persistent storage layer for markup caching. This change adds a dedicated database table schema (PhabricatorCacheSchemaSpec) to store cache entries with keys, data, and expiration times, along with the corresponding Data Access Object (PhabricatorCacheDAO) and a specific implementation for markup data (PhabricatorMarkupCache). This enables caching of rendered markup content in the database rather than relying solely on memory or other storage backends.

src/applications/cache/storage · high confidence

Introduce dedicated Aphlict notification client and server reference classes

This change adds PhabricatorNotificationClient and PhabricatorNotificationServerRef to src/applications/notification/client, establishing the client-side infrastructure for real-time notifications via Aphlict. The new client handles posting messages to configured notification servers with unique IDs and fallback logic, while the server reference class manages server configuration (host, port, protocol, path) and URI construction for both HTTP and WebSocket connections, including support for clustering via instance parameters.

src/applications/notification/client · high confidence

Introduce dedicated Badges application controllers

This change adds a new set of controllers for the Badges application, including PhabricatorBadgesViewController, PhabricatorBadgesEditController, PhabricatorBadgesRecipientsController, PhabricatorBadgesAwardController, PhabricatorBadgesArchiveController, and PhabricatorBadgesCommentController. These controllers handle the core user interactions for viewing, editing, awarding, archiving, and commenting on badges, as well as managing badge recipients. The implementation establishes the backend routing and logic for these badge-specific features.

src/applications/badges/controller, src/applications/home/controller · high confidence

Introduce dedicated Mail application with inbound webhook support

A new 'Mail' application has been added to the system, providing a dedicated interface for sending and receiving email. This change registers the application under the Admin group with the base URI '/mail/' and includes specific route definitions for handling inbound mail via webhooks from SendGrid, Mailgun, and Postmark. Users can now access mail lists and view individual mail details through the new controllers associated with this application.

src/applications/metamta/application · high confidence

Introduce dedicated Notifications application class

A new PhabricatorNotificationsApplication class has been added to define the Notifications application, specifying its name, base URI (/notification/), description, icon, and routing configuration for list, panel, individual, clear, and test controllers.

src/applications/notification/application · high confidence

Introduce dedicated PHID type handler for Maniphest tasks

Added a new \ManiphestTaskPHIDType\ class to manage how Maniphest tasks are identified, queried, and displayed within the PHID system. This change enables the application to correctly resolve task handles (e.g., T123), load task objects by their short names, and determine their closed status, ensuring that task references in the UI and API behave consistently with other PHID-managed objects.

src/applications/maniphest/phid · high confidence

Introduce dedicated Search application module

Adds a new PhabricatorSearchApplication class that registers the Search feature as a distinct application within the platform. This change defines the core search interface at /search/, including routes for full-text search queries, hovercards, handle details, and the management (edit, delete, order) of saved queries. It also establishes the foundation for relationship-based search operations via dedicated controllers, effectively separating search functionality into its own modular application scope.

src/applications/search/application · high confidence

Introduce dedicated Settings application with wrench icon and modular routing

Users now access user preferences through a new, dedicated 'Settings' application located at /settings/, replacing the previous scattered panel-based structure. This application is visually represented by a wrench icon and groups utilities under a single entry point. The new routing structure supports a main settings list, user-specific settings pages, global administrator settings, and specific controllers for timezone adjustments and account issues, laying the groundwork for a more modular settings experience.

src/applications/settings/application · high confidence

Introduce dedicated content source classes for Herald, Email, and Phortune

This change adds specific content source implementations for Herald, Email, and Phortune, each extending the base PhabricatorContentSource class. Users will now see distinct, labeled content sources for changes triggered by Herald rules, content sent via email, and updates from Phortune subscriptions and payment processors, improving clarity in how different types of content origins are identified and described within the system.

src/applications/herald/contentsource, src/applications/metamta/contentsource, src/applications/phortune/contentsource · high confidence

Introduce dedicated controllers for Phame blog management and visibility

The Phame application now uses a set of specialized controllers to handle blog lifecycle and presentation. A new PhameBlog404Controller provides explicit 404 handling for live blog views, while PhameBlogArchiveController allows users to archive and reactivate blogs via a confirmation dialog. Blog management is centralized in PhameBlogManageController, which displays blog details, status, and actions, and links to new controllers for editing the blog header (PhameBlogHeaderPictureController) and profile picture (PhameBlogProfilePictureController). Public-facing blog listing and viewing are handled by PhameBlogListController and PhameBlogViewController respectively, with the latter supporting a modernized header and post list. Additionally, PhameBlogFeedController generates Atom feeds for blogs, and PhameBlogEditController delegates editing to an EditEngine.

src/applications/phame/controller/blog · high confidence

Introduce dedicated fatal setup error response class

A new PhabricatorConfigResponse class has been added to handle fatal configuration errors during setup. This response class returns a 500 HTTP status code and renders a specific error page with dedicated CSS styles. It distinguishes between an 'in-flight' setup check and a final fatal error, rendering the appropriate view content for each state, while also providing a plain-text fallback message for non-HTML contexts.

src/applications/config/response · high confidence

Introduce dedicated repository management scripts for hooks, linting, and administration

This change adds three new CLI scripts to the repository management area: \commit\_hook.php\ handles incoming commit hooks for Git, Mercurial, and Subversion repositories (including support for SVN revision properties and observed repositories), \save\_lint.php\ discovers and saves lint errors to the database with options for blame assignment and severity filtering, and \manage\_repositories.php\ serves as a dispatcher for repository management workflows. These scripts replace ad-hoc hook handling and provide a structured way to manage repository operations, linting, and administrative tasks via the command line.

scripts/repository · high confidence

Introduce dedicated validation error object for transaction errors

A new \PhabricatorApplicationTransactionValidationError\ class has been added to encapsulate validation errors for application transactions. This object stores the error type, transaction details, and both short and full error messages, while also supporting a flag to identify missing field errors. This change provides a structured way to handle and display validation feedback to users when transaction inputs are invalid.

src/applications/transactions/error · high confidence

Introduce disk-backed caching for Diviner atom and publish data

Diviner now persists its internal state to disk using a new cache layer, which should improve performance for large repositories by avoiding full recomputation on every run. This change adds three new classes in src/applications/diviner/cache: DivinerDiskCache provides the base infrastructure using PhutilDirectoryKeyValueCache with profiled access and optimized hash-key directory structures; DivinerAtomCache manages the persistence of file hashes, atom data, symbols, and dependency edges; and DivinerPublishCache handles the mapping of atom hashes to file paths and maintains the publication index.

src/applications/diviner/cache · high confidence

Introduce draft persistence engine and interface

This change introduces the core infrastructure for saving and restoring user drafts. It adds the \PhabricatorDraftInterface\ which objects must implement to support drafts, and the \PhabricatorDraftEngine\ abstract class which handles the logic for loading, synchronizing, and attaching draft status to objects. A concrete \PhabricatorBuiltinDraftEngine\ is also added to provide default behavior. This enables applications to persist partial user input across sessions.

src/applications/transactions/draft · high confidence

Introduce extended policy interfaces for complex object dependencies

The policy system now supports complex, cross-object policy checks through two new interfaces: PhabricatorPolicyInterface and PhabricatorExtendedPolicyInterface. PhabricatorPolicyInterface defines the standard capability and policy methods for objects, while PhabricatorExtendedPolicyInterface allows objects to specify additional policy requirements based on other objects (e.g., requiring visibility of a parent repository to view a revision). This enables more granular and efficient policy enforcement across related objects without repeated reloading.

src/applications/policy/interface · high confidence

Introduce extensible Nuance source definitions with GitHub and Web Form support

Users can now configure Nuance to ingest data from new sources via a modular definition system. This change adds a base NuanceSourceDefinition class and two concrete implementations: a GitHub Repository source that imports issues and pull requests using separate cursors for repository and issues events, and a Web Form source that allows users to submit complaints directly into a Nuance queue. The system supports custom view actions and property rendering for these sources.

src/applications/nuance/source · high confidence

Introduce extensible chart and fact engine infrastructure

This change adds the core engine classes for the new Facts application, enabling users to view tracked metrics through charts and tables. It introduces PhabricatorFactEngine as the base for generating facts (such as task counts and points) from transaction history, and PhabricatorChartEngine to render these facts into visual charts or tabular data. The implementation includes a demo chart engine for testing, a rendering engine that stores chart data and generates the necessary JavaScript for display, and specific fact engines for Maniphest tasks that track creation, assignment, and status changes over time.

src/applications/fact/engine · high confidence

Introduce extensible file storage format system with AES-256 encryption support

Files now support pluggable storage formats, allowing data to be stored in raw, encoded, or encrypted states. The system introduces an abstract base class for storage formats and includes three implementations: a raw format for unmodified data, a ROT13 format for testing and development, and an AES-256-CBC format for production-grade at-rest encryption. The AES-256 implementation automatically generates and manages unique keys and initialization vectors for each file block, encrypts the file data, and computes an HMAC-SHA256 integrity hash to detect tampering. Users can now store files with strong encryption at rest, with the system handling key generation, encryption, decryption, and integrity verification transparently.

src/applications/files/format · high confidence

Introduce extensible product implementation architecture for Phortune

The Phortune product purchasing flow now uses a modular implementation pattern, introducing the abstract \PhortuneProductImplementation\ base class to define how different product types are handled. This change adds specific implementations for 'Ad-Hoc Products' (allowing flexible, reference-based purchases) and 'Subscription Products' (linking purchases to existing subscription objects and delegating lifecycle hooks like purchase and refund events). This structure enables the system to support diverse product types beyond simple fixed-price items, laying the groundwork for more complex purchasing behaviors.

src/applications/phortune/cart, src/applications/phortune/product · high confidence

Introduce external MIME mail parser library

Added the php-mime-mail-parser library (MimeMailParser.class.php, attachment.class.php) to the externals directory to handle email parsing. The implementation includes a workaround for a mailparse extension bug where messages lacking a terminal newline are truncated, and modifies the parser to skip 'inline' text attachments, ensuring only actual file attachments are processed.

externals/mimemailparser · high confidence

Introduce external object storage for Doorkeeper

The Doorkeeper application now includes a new storage layer to track and manage external objects. This change adds the \DoorkeeperExternalObject\ data model, which stores references to objects from other systems (identified by application type, domain, type, and ID) along with associated properties and policies. A corresponding DAO (\DoorkeeperDAO\) and schema specification (\DoorkeeperSchemaSpec\) are also introduced to support database persistence and schema generation for this new entity.

src/applications/doorkeeper/storage · high confidence

Introduce feed story publishing with notification integration

The feed application now includes a new \PhabricatorFeedStoryPublisher\ class that handles the creation and persistence of feed stories. This publisher manages story metadata, links related objects, and integrates with the notification system by inserting notifications for subscribed users and scheduling a background worker task to handle further processing. It also supports marking notifications as read for users who receive email alerts for the same event.

src/applications/feed · high confidence

Introduce feed story storage schema and DAOs

Added new database storage classes for feed stories, including PhabricatorFeedDAO, PhabricatorFeedStoryData, and PhabricatorFeedStoryReference. These classes define the schema for storing feed story data, including chronological keys, story types, and references to objects. The implementation supports unique constraints on PHIDs and chronological keys, and handles destruction of related notifications and references when a story is deleted.

src/applications/feed/storage · high confidence

Introduce feed.query Conduit API method

Users can now query feed stories via the new 'feed.query' Conduit API endpoint. This method supports filtering by specific PHIDs, pagination using 'before' and 'after' cursors, and returning results in multiple formats including full HTML, HTML summaries, plain text, or structured data dictionaries.

src/applications/feed/conduit · high confidence

Introduce formal Conduit parameter type system

This change adds a new, structured type system for Conduit API parameters located in src/applications/conduit/parametertype. It introduces a base ConduitParameterType class and a suite of specific types (including bool, int, string, list, phid, epoch, points, and user/project lists) that enforce validation, handle type coercion (such as accepting string representations of booleans or integers), and provide standardized format descriptions and examples for API consumers.

src/applications/conduit/parametertype · high confidence

Introduce function-driven logical project queries in typeahead

The project typeahead now supports a new function-driven query syntax that allows users to construct complex logical constraints directly in the search box. This includes the \any()\ and \not()\ functions for OR/NOT logic (e.g., \any(ios), any(android)\ or \not(vanilla)\), the \only()\ function to match results with exactly specified tags, and the \null()\ function to find items not tagged with any projects. Additionally, new functions like \viewerprojects()\ and \projects(\<user\>)\ allow filtering by the current user's projects or a specific user's projects, while \members(\<project\>)\ filters by project members. The typeahead also now supports logical ancestor queries, where searching for a parent project automatically includes its subprojects.

src/applications/project/typeahead · high confidence

Introduce in-process Conduit method execution

Applications can now call Conduit API methods directly in-process via the new ConduitCall class, eliminating the need for HTTP requests for internal communication. This change allows applications to invoke methods with strict parameter validation, automatic authentication checks, and capability-based access control, while also recording these calls in the service profiler for performance monitoring.

src/applications/conduit/call · high confidence

Introduce live documentation publisher for Diviner

Diviner now supports a 'live' publishing mode alongside the existing static file generation. This change adds a new \DivinerLivePublisher\ class that stores documentation symbols and atoms directly in the application's database (using \DivinerLiveBook\ and \DivinerLiveSymbol\) rather than writing static HTML files. It integrates with the global search index by queuing documents for indexing via \PhabricatorSearchWorker\, allowing users to view and search documentation dynamically within the application interface.

src/applications/diviner/publisher · high confidence

Introduce live storage layer for Diviner books and symbols

This change adds a new persistent storage backend for Diviner, introducing \DivinerLiveBook\ and \DivinerLiveSymbol\ entities to replace or supplement previous in-memory or file-based approaches. \DivinerLiveBook\ now supports full CRUD operations, policy-based access control (view/edit), permanent destruction (which cascades to its atoms), and full-text search integration. \DivinerLiveSymbol\ stores detailed metadata for documentation atoms (titles, slugs, hashes, types) and enables efficient querying and linking within books. A new \DivinerLiveAtom\ entity tracks live atom data, and \DivinerLiveBookTransaction\ provides transactional history for book changes. This foundation enables features like live documentation views, better searchability, and persistent book configuration.

src/applications/diviner/storage · high confidence

Introduce low-level Diffusion query classes for VCS operations

This change introduces a new set of low-level query classes in \src/applications/diffusion/query/lowlevel\ to handle direct interactions with Git, Mercurial, and Subversion repositories. The new classes include \DiffusionLowLevelCommitQuery\ for fetching commit metadata (author, message, hashes) with improved Git version compatibility, \DiffusionLowLevelCommitFieldsQuery\ for parsing commit messages and matching them to Differential revisions, \DiffusionLowLevelGitRefQuery\ for resolving Git branches and tags using \git for-each-ref\, \DiffusionLowLevelMercurialBranchesQuery\ for tracking Mercurial branch states including closed branches, \DiffusionLowLevelMercurialPathsQuery\ for listing files using \hg locate\ or \hg files\, \DiffusionLowLevelParentsQuery\ for retrieving parent commit hashes, \DiffusionLowLevelFilesizeQuery\ for calculating file sizes in Git commits, and \DiffusionLowLevelResolveRefsQuery\ for resolving various reference types to commit identifiers. These classes provide a more robust and performant foundation for Diffusion's repository data ingestion and display.

src/applications/diffusion/query/lowlevel · high confidence

Introduce mail reply handlers and recipient summary stamps

This change introduces the core reply handler infrastructure (PhabricatorMailReplyHandler) and mail target logic (PhabricatorMailTarget) for the MetaMTA application. For users, this enables the system to process incoming email replies to Phabricator objects and enhances outgoing notification emails by appending a 'STAMPS' section to the body. In HTML emails, these stamps are rendered with smaller, lighter text, and a recipient summary (To/Cc lines) is added to both plain text and HTML bodies to clarify who received the message.

src/applications/metamta/replyhandler · high confidence

Introduce mail stamp system for client routing

Added a new mail stamp framework in src/applications/metamta/stamp to improve client mail routing. This includes a base PhabricatorMailStamp class and concrete implementations for boolean, PHID, and string values, enabling structured metadata tagging on emails.

src/applications/metamta/stamp · high confidence

Introduce modern PHUI view classes and refactor form/dialog rendering

This change introduces a suite of new PHUI (Phabricator User Interface) view classes, including AphrontDialogView, AphrontFormView, AphrontTagView, and various form controls, to modernize the application's UI rendering. These new components replace older, less flexible view implementations, providing a more consistent and maintainable structure for dialogs, forms, and tag-based layouts. The update also includes new test cases for AphrontView, local time formatting, and byte formatting to ensure the reliability of these core UI components.

src/view · high confidence

Introduce modular ApplicationTransaction editors and configuration forms

This change introduces a new, modular transaction editing infrastructure for Phabricator applications. It adds the core \PhabricatorApplicationTransactionEditor\ class, which handles the application of transactions, mail publishing, and feed updates, along with a specialized \PhabricatorApplicationTransactionCommentEditor\ for managing comment edits with MFA checks and policy validation. Additionally, it provides \PhabricatorEditEngineConfigurationEditEngine\ and its associated editor, allowing administrators to configure and customize the edit forms for other applications. These components replace older, monolithic editing patterns with a more flexible, reusable system for handling object edits and comments across the platform.

src/applications/transactions/editor · high confidence

Introduce modular file storage engine architecture with chunked upload support

The file storage system has been refactored into a pluggable engine architecture, introducing a new abstract base class (PhabricatorFileStorageEngine) and concrete implementations for local disk, MySQL blobs, and Amazon S3. This change enables chunked file storage via a new PhabricatorChunkedFileStorageEngine, which splits large files into manageable pieces to support resumable JavaScript uploads and bypasses traditional filesize limits. Users benefit from improved scalability, the ability to store large files reliably across distributed backends, and enhanced integrity verification through chunked hashing.

src/applications/files/engine · high confidence

Introduce modular item types for Nuance with GitHub event support

Nuance now uses a modular item type system, allowing different content sources to define their own item behaviors and views. This change introduces a base NuanceItemType class and specific implementations, including a new GitHub Event item type that bridges GitHub issues and users via Doorkeeper to attribute actions correctly. Additionally, a Form item type is added to handle complaint-style content, providing a basic view and a 'Throw In Trash' work command.

src/applications/nuance/item · high confidence

Introduce modular transaction infrastructure for Harbormaster Build Plans and Steps

Harbormaster Build Plans and Build Steps now use a modular transaction system to manage changes, enabling a detailed, auditable history of edits (such as creating steps, changing names, or modifying dependencies) in the UI timeline. This change also establishes the underlying data model for Build Plans, including support for autoplans, plan status (active/disabled), and specific policy capabilities for viewing and editing.

src/applications/harbormaster/storage/configuration · high confidence

Introduce modular transaction storage for Nuance items, queues, and sources

The Nuance application now uses a modular transaction system for its core storage objects. This change adds database schema definitions and transaction types for NuanceItem, NuanceQueue, and NuanceSource, enabling users to track and audit changes to item status, ownership, queue routing, source names, and default queues. It also introduces NuanceItemCommand to record and execute commands against items, and NuanceImportCursorData to track import progress for sources.

src/applications/nuance/storage · high confidence

Introduce modular transaction storage infrastructure

This change adds the core storage classes for the new modular transaction system, including PhabricatorApplicationTransaction, PhabricatorModularTransaction, and PhabricatorModularTransactionType. These classes provide the database schema and base logic for storing transaction records, managing transaction types via a modular implementation pattern, and handling comments and configuration. This forms the foundation for the broader refactor of how object changes are tracked and rendered across the platform.

src/applications/transactions/storage · high confidence

Introduce modular typeahead datasource controllers with browse paging and function help

This change introduces a new controller hierarchy for typeahead datasources, starting with a base \PhabricatorTypeaheadDatasourceController\ and specific implementations like \PhabricatorTypeaheadModularDatasourceController\ and \PhabricatorTypeaheadFunctionHelpController\. The modular controller enables a new browse view for typeahead results, supporting offset-based paging with a hard limit of 1,000 results to prevent performance issues, and allows users to select tokens from a paginated list. Additionally, a new help page is added that documents available typeahead functions for each datasource, improving discoverability for advanced search features.

src/applications/typeahead/controller · high confidence

Introduce modular user cache for preferences, badges, and counts

A new modular user cache system has been added to the People application, introducing a base \PhabricatorUserCacheType\ and specific implementations for user preferences, profile images, notification counts, message counts, and badges. This change centralizes how these user-specific data points are stored and retrieved, validating preferences against defined settings and optimizing profile image generation by caching URI and version data. Users will benefit from more consistent and performant access to their profile images, notification/message counts, and badge information, with preferences now validated before caching to ensure data integrity.

src/applications/people/cache · high confidence

Introduce modular user preferences storage with transaction support

The settings application now includes a new storage layer for user preferences, represented by the \PhabricatorUserPreferences\ class and its associated transaction type. This change enables preferences to be stored as JSON-serialized data in the database and supports modification via application transactions, laying the groundwork for a more modular and editable settings system.

src/applications/settings/storage · high confidence

Introduce multi-factor authentication (MFA) with TOTP, SMS, and Duo support

Users can now secure their accounts with multi-factor authentication. The system adds support for three factor types: Time-based One-Time Password (TOTP) via mobile authenticator apps like Google Authenticator or Authy, verification codes sent via SMS to a user's primary contact number, and push notifications via Duo Security. This change introduces the underlying MFA framework, including challenge tracking, temporary sync tokens for enrollment, and UI components for entering and validating codes.

src/applications/auth/factor · high confidence

Introduce new Flag application controllers

The Flag application now includes dedicated controllers to manage user interactions: PhabricatorFlagListController handles listing flags via ApplicationSearch, PhabricatorFlagEditController provides a dialog for creating or editing flag colors and notes, PhabricatorFlagDeleteController allows owners to remove their flags, and PhabricatorFlagController serves as the base class providing side navigation. This structure replaces the previous monolithic or legacy controller setup with a modular approach for flag management.

src/applications/flag/controller · high confidence

Introduce new modular authentication controllers for login, registration, and session management

The authentication system has been refactored into a new set of dedicated controllers to support a modernized login and registration flow. This change introduces \PhabricatorAuthLoginController\ to handle external provider logins and account linking, \PhabricatorAuthRegisterController\ to manage new user registration and first-time setup, and \PhabricatorAuthConfirmLinkController\ to allow users to explicitly confirm linking external accounts. Session handling is now split into \PhabricatorAuthFinishController\ for upgrading partial sessions and enforcing multi-factor authentication, and \PhabricatorAuthDowngradeSessionController\ for exiting high-security modes. Additional controllers include \PhabricatorAuthInviteController\ for processing invite codes, \PhabricatorAuthNeedsApprovalController\ for pending account approvals, \PhabricatorAuthNeedsMultiFactorController\ for MFA enrollment, \PhabricatorAuthOneTimeLoginController\ for secure email-based login links, and \PhabricatorAuthRevokeTokenController\ for managing temporary tokens. Legacy OAuth redirect compatibility is maintained via \PhabricatorAuthOldOAuthRedirectController\, while SSH key management is abstracted into \PhabricatorAuthSSHKeyController\ and \PhabricatorAuthSSHKeyEditController\. These controllers collectively replace the previous monolithic authentication logic with a more granular, secure, and extensible architecture.

src/applications/auth/controller · high confidence

Introduce new search query and result infrastructure

This change adds the core query classes and data structures that power the new search system, including PhabricatorFulltextResultSet and PhabricatorFulltextToken to handle search results and token metadata (such as short words, stop words, and operators like exact match or substring), along with query loaders for named queries, saved queries, and profile menu item configurations. It also introduces PhabricatorSearchApplicationSearchEngine to manage the search form and saved query conversion, and PhabricatorSearchDocumentQuery to execute fulltext searches and load document handles with policy filtering.

src/applications/search/query · high confidence

Introduce new view components for the Guides application

Added PhabricatorGuideItemView and PhabricatorGuideListView to render guide items using the PHUIObjectItemListView component. The list view now displays guide entries with icons, titles, descriptions, and optional 'Skip' buttons, leveraging the PHUI framework for consistent styling.

src/applications/guides/view · high confidence

Introduce ngram-based search indexing for Phabricator objects

A new abstract base class \PhabricatorSearchNgrams\ has been added to support ngram-based search capabilities. This class manages the storage and retrieval of ngrams for search objects, utilizing a dedicated database table schema with columns for object ID and ngram values. It integrates with a \PhabricatorSearchNgramEngine\ to split text into ngrams and handles the persistence of these tokens, enabling more flexible and fuzzy search functionality for Phabricator entities.

src/applications/search/ngrams · high confidence

Introduce notification builder with aggregation and desktop notification support

Added PhabricatorNotificationBuilder to centralize notification processing, introducing support for aggregating multiple stories into single notifications (e.g., combining updates to the same task) and enabling desktop notifications for application transaction stories. The builder allows toggling timestamp display in popup bubbles and respects user-specific notification settings to determine whether web or desktop notifications are shown.

src/applications/notification/builder · high confidence

Introduce one-up diff view and refactor renderer architecture

Differential now supports a 'one-up' diff view alongside the existing two-up layout, allowing users to see changes in a single-column format for both the web UI and email notifications. This change introduces a new renderer hierarchy (DifferentialChangesetHTMLRenderer, DifferentialChangesetOneUpRenderer, and DifferentialChangesetOneUpMailRenderer) to manage these distinct layouts, while also adding a new DifferentialRawDiffRenderer to handle patch generation with configurable byte limits and format options (unified or git).

src/applications/differential/render · high confidence

Introduce policy editing and explanation controllers

Adds PhabricatorPolicyEditController and PhabricatorPolicyExplainController to the policy application. The edit controller allows users to create and save custom policy rules for objects, including validation to reject meaningless rules and support for different rule types. The explain controller provides a dialog that details policy settings, including space-level restrictions, extended policies, and exceptions, helping users understand why they have or don't have access to specific objects.

src/applications/policy/controller · high confidence

Introduce policy editing fields via EditEngine extension

Adds a new EditEngine extension that automatically provides View, Edit, Join, and Interact policy fields for objects implementing PhabricatorPolicyInterface. This allows users to modify access controls directly through the standard edit workflow, with specific handling for Space objects to link space membership to view policies.

src/applications/policy/editor · high confidence

Introduce policy-aware query classes for Pholio images, mocks, and transactions

This change adds new query classes (PholioImageQuery, PholioMockQuery, PholioTransactionQuery) and a search engine (PholioMockSearchEngine) to the Pholio application. These classes enable users to retrieve Pholio images and mocks with proper policy enforcement, including support for filtering by author, status, and inline comments. The search engine provides a user-friendly interface for browsing and filtering Pholio mocks, with built-in queries for open, all, and authored mocks.

src/applications/pholio/query · high confidence

Introduce project workboard trigger management UI

Users can now create, edit, and view project workboard triggers through a new interface. The list controller provides a searchable index of all triggers, while the view controller displays trigger details including associated rules and a list of workboard columns that use the trigger (distinguishing between active and restricted columns). The edit controller allows users to configure trigger names, edit policies, and rule sets, and supports attaching or detaching triggers from specific workboard columns during the editing process.

src/applications/project/controller/trigger · high confidence

This change adds three new PHP interfaces to the project application: PhabricatorProjectInterface, PhabricatorWorkboardInterface, and PhabricatorColumnProxyInterface. These interfaces serve as contracts for objects that can be tagged with projects, represent workboards, and provide column names for workboard displays, respectively. This lays the groundwork for implementing milestone columns on workboards and marking objects as project-taggable.

src/applications/project/interface · high confidence

Introduce query for aggregating notification and message counts

A new AphlictDropdownDataQuery class has been added to centralize the retrieval of unread notification and Conpherence message counts for the current viewer. This query checks whether the respective applications are installed, fetches the raw counts, formats numbers greater than 999 as infinity, and returns a structured array containing the installation status, count type, formatted count, and raw count for both notifications and messages.

src/applications/aphlict/query · high confidence

Introduce repository-based symbol generation and import scripts

Added new CLI scripts in the symbols directory to generate and import code symbols for repositories. The system now supports generating symbols via Exuberant Ctags (for general languages) and XHPAST (for PHP), with the PHP generator specifically skipping anonymous functions and normalizing language identifiers (e.g., c\# to cs). The import script allows users to upload these symbols to the repository database, supporting incremental updates via a no-purge flag and ignoring parse errors to improve robustness during bulk imports.

scripts/symbols · high confidence

Introduce search result bucket infrastructure

Added the \PhabricatorSearchResultBucket\ and \PhabricatorSearchResultBucketGroup\ classes to support grouping search results into named buckets. The bucket base class provides a framework for defining result groups with configurable page sizes and viewer context, while the group class stores the bucket's name, key, display string for empty states, and the associated objects.

src/applications/search/buckets · high confidence

Introduce stable iteration for fact extraction updates

A new PhabricatorFactUpdateIterator class has been added to handle the stable iteration of objects during fact extraction. This iterator processes objects based on their update time (dateModified) and ID, ensuring a consistent order even as new data is inserted. It includes logic to ignore very recent updates (within the last 15 seconds) to prevent race conditions where an object might be updated multiple times within the same second, which could otherwise lead to skipped updates or inconsistent state. This mechanism supports the new fact application by providing a reliable way to traverse and process object changes.

src/applications/fact/extract · high confidence

Introduce structured Almanac service types for clusters and Drydock

Almanac now uses explicit service type classes (e.g., Cluster Database, Cluster Repository, Custom, Drydock Pool) instead of generic service classes. This adds structured metadata and field specifications for cluster services, including a boolean to control whether new repositories can be created and a binding-level toggle to allow or prevent writes. Users benefit from clearer service categorization and more granular control over repository access and write permissions within clusters.

src/applications/almanac/servicetype · high confidence

Introduce structured Drydock logging with multiple log types

Drydock now supports structured logging for lease and resource operations, providing specific log types for events such as lease acquisition, activation, failure, reclamation, and authorization checks. This change introduces a new \DrydockLogType\ base class and a suite of concrete log types (e.g., \DrydockLeaseAcquiredLogType\, \DrydockResourceReclaimLogType\) that allow logs to be formally typed, filtered, and rendered in both text and HTML formats. A convenience \DrydockTextLogType\ is also added for arbitrary text logging, enabling better visibility into Drydock's internal state changes for users.

src/applications/drydock/logtype · high confidence

Introduce structured Profile Menu Items for Applications, Dashboards, and Conpherence

This change adds a new, extensible system for configuring profile sidebar menus, replacing the previous ad-hoc approach with specific menu item types. Users can now add structured items for Applications, Conpherence rooms, Dashboards, Projects, Forms, and external Links, each with dedicated validation and display logic. Dashboard items can now render their content directly on the page rather than just linking to it, and Conpherence items display unread message counts. The system also includes utility items like Dividers, Labels, and a Motivator panel, along with a dedicated icon set for menu items.

src/applications/search/menuitem · high confidence

Introduce structured credential types for Passphrase

The Passphrase application now supports distinct credential types—Password, Token, Note, and SSH Private Key (with subtypes for text, file, and generated keys)—allowing users to store and manage secrets with appropriate UI controls and metadata. This change replaces the previous generic storage model with a typed system that enables features like password stripping for SSH keys, public key extraction, and key generation, while maintaining backward compatibility for existing SSH key-file credentials.

src/applications/passphrase/credentialtype · high confidence

Introduce structured file upload source abstraction

The file upload system now uses a new \PhabricatorFileUploadSource\ base class with concrete implementations for iterator-based and exec-future-based data streams. This change introduces a structured way to handle file uploads, including support for byte limits (throwing \PhabricatorFileUploadSourceByteLimitException\ when exceeded), configurable TTL, view policies, and MIME types. It also enables chunked file uploads for large files by delegating to storage engines, and allows uploading files larger than 8MB by streaming data rather than loading it entirely into memory.

src/applications/files/uploadsource · high confidence

Introduce structured message types and phone number handling for MetaMTA

The MetaMTA messaging system now uses distinct message classes to handle different communication channels, introducing PhabricatorMailEmailMessage for emails and PhabricatorMailSMSMessage for SMS, both extending a new PhabricatorMailExternalMessage base that supports a message type identifier. This change adds support for sending SMS messages by introducing a PhabricatorPhoneNumber class that normalizes and validates phone numbers into E.164 format, and a PhabricatorMailAttachment class to manage email attachments with file upload integration. These components provide the foundational data structures required for the MetaMTA application to route and format messages for both email and SMS delivery.

src/applications/metamta/message · high confidence

Introduce structured policy capability classes for view, edit, join, and interact permissions

This change introduces a new set of policy capability classes (PhabricatorPolicyCanViewCapability, PhabricatorPolicyCanEditCapability, PhabricatorPolicyCanJoinCapability, and PhabricatorPolicyCanInteractCapability) that extend the abstract PhabricatorPolicyCapability base class. These classes define specific permission types (view, edit, join, interact) with human-readable names and rejection messages. Notably, the 'Can View' and 'Can Interact' capabilities now support public policy settings via the shouldAllowPublicPolicySetting() method, allowing applications to configure these permissions as publicly accessible. The base class provides a mechanism for registering and retrieving capabilities by key using PhutilClassMapQuery, enabling applications to define and manage their own policy capabilities in a standardized way.

src/applications/policy/capability · high confidence

Introduce structured typeahead result model

Added PhabricatorTypeaheadResult, a new storage class that standardizes how typeahead data is represented. This model supports rich metadata including icons, display names, PHIDs, priority levels, and availability status, enabling more consistent and visually informative search suggestions across the application.

src/applications/typeahead/storage · high confidence

Introduce subscription implementation base class

Added the abstract \PhortuneSubscriptionImplementation\ class, which serves as the base for defining how specific subscription types behave within the Phortune application. This class establishes the interface for loading implementations, retrieving subscription names and costs, and handling post-purchase logic, enabling the system to support flexible subscription models beyond a single fixed price.

src/applications/phortune/subscription · high confidence

Introduce synthetic data generation script

A new \manage\_lipsum.php\ script has been added to the \scripts/lipsum\ directory to generate synthetic test data, improving development convenience. The script utilizes \PhutilClassMapQuery\ to dynamically locate and register management workflows that extend \PhabricatorLipsumManagementWorkflow\, allowing users to run commands like \bin/lipsum\ to create test data.

scripts/lipsum · high confidence

Introduce system action rate limiting infrastructure

A new abstract base class, PhabricatorSystemAction, has been added to provide a standardized framework for managing action rates. This class introduces methods to determine score thresholds, check if an actor should be blocked based on their current activity level, and generate user-friendly explanations for rate limits (e.g., actions per second, minute, or hour). This infrastructure allows system actions to implement consistent rate-limiting behavior and clear feedback for users who exceed allowed thresholds.

src/applications/system/action · high confidence

Introduce token assignment editor with user notifications

Added PhabricatorTokenGivenEditor to handle the logic for awarding and revoking tokens on objects. This change enables the system to assign a token to an object, replacing any existing token, and automatically notifies users associated with the object via a feed story when a token is awarded.

src/applications/tokens/editor · high confidence

Introduce token management and leaderboard views

The Tokens application now provides dedicated controller pages for managing and viewing tokens. Users can navigate to a 'Tokens Given' list to see which tokens they have awarded to other objects, and to a 'Leader Board' to view a ranked list of objects that have received the most tokens. Additionally, a new interface allows users to give or rescind tokens directly from an object's page via a dialog.

src/applications/tokens/controller · high confidence

Introduce token query classes for the Tokens application

Added four new query classes in the Tokens application to support token-related data retrieval: PhabricatorTokenQuery for loading built-in tokens, PhabricatorTokenGivenQuery for tracking token usage with policy awareness, PhabricatorTokenCountQuery for retrieving token counts by object, and PhabricatorTokenReceiverQuery for listing objects ranked by token counts.

src/applications/tokens/query · high confidence

Introduce transaction types for project trigger configuration

This change adds the underlying transaction infrastructure for managing project workboard triggers, allowing users to modify trigger properties via the standard Phabricator transaction system. It introduces an abstract base class for trigger transactions and implements specific transaction types for updating the trigger's name and its associated ruleset. Users can now rename triggers, validate that names do not exceed the configured maximum length, and update trigger rulesets with validation that distinguishes between invalid record formats and invalid record values, with changes to the ruleset displayed as a JSON diff in the change history.

src/applications/project/xaction/trigger · high confidence

Introduce transaction-based editing for Pholio Mocks

Pholio Mocks now use a modular transaction editor (PholioMockEditor) to manage changes, enabling structured history tracking, email notifications, feed integration, and Herald rule activation. This change supports specific transaction types including inline comments, edge relationships, and policy edits, and ensures inline comments are grouped and rendered correctly in email notifications.

src/applications/pholio/editor · high confidence

Introduce unified 'bin/repository' CLI for repository management

Consolidates repository administration into a new 'bin/repository' command-line interface, replacing scattered scripts with a structured set of subcommands. This includes 'repository list' and 'list-paths' for inventory, 'repository pull' (with an --ignore-locality flag) and 'mirror' for data synchronization, 'repository discover' (with --repair) and 'parents' for commit graph maintenance, and 'rebuild-identities' for author/committer resolution. It also adds operational controls such as 'clusterize' for moving repositories into Almanac cluster services, 'lock' and 'maintenance' for read-only modes during upkeep, and 'mark-reachable' and 'hint' for correcting commit status and metadata.

src/applications/repository/management · high confidence

Introduce versioned draft storage for comment forms

Users can now have their comment drafts saved and restored automatically, even when editing the same object multiple times. This change adds new storage classes (PhabricatorDraft and PhabricatorVersionedDraft) that support versioning, ensuring that drafts are correctly associated with specific objects and authors, and that empty drafts are not persisted. It also includes logic to purge drafts after a transaction edit and handle race conditions during preview requests, improving the reliability of the draft experience in EditEngine comment forms.

src/applications/draft · high confidence

Introduce web-based management for Drydock blueprints, resources, leases, and operations

This change adds a comprehensive set of web controllers for the Drydock application, enabling users to manage Drydock blueprints, resources, leases, and repository operations directly through the browser. The new controllers provide list views, detail views, and specific action pages for key workflows: users can now create, edit, and disable blueprints; view and release resources; manage lease lifecycles (including explicit release and viewing acquisition/activation epochs); and monitor repository operations with the ability to dismiss them. A new Drydock Console serves as a central hub to navigate these sections. Additionally, a new authorization system allows specific objects to request and be granted permission to lease resources from blueprints, with dedicated views to approve or decline these requests.

src/applications/drydock/controller · high confidence

Introduce webhook delivery worker with silent-mode and locking support

Adds a new HeraldWebhookWorker that processes queued webhook requests by fetching the associated object and transactions, signing the payload with HMAC-SHA256, and posting it to the configured URI. The worker respects the global 'phabricator.silent' configuration by permanently failing requests when silent mode is enabled, and implements per-webhook global locking to prevent thundering herd issues during high-volume delivery.

src/applications/herald/worker · high confidence

Introduces a new, centralized caching infrastructure with specialized backends

This change replaces the previous caching mechanisms with a new, centralized \PhabricatorCaches\ system that provides distinct cache stacks for different use cases: a request-scoped cache (destroyed per request with garbage collection), an immutable stack (APC + database for permanent data), a runtime stack (APC-only for fast, restart-scoped data), and a mutable structure stack. It introduces a new database-backed key-value cache (\PhabricatorKeyValueDatabaseCache\) that supports deflated storage for modern hunks and uses a dedicated \cache\_general\ table. Additionally, it adds a \PhabricatorKeyValueSerializingCacheProxy\ to allow complex data structures to be stored in string-only caches, and a \PhabricatorCachedClassMapQuery\ to optimize class lookups by caching individual class mappings rather than loading the entire map.

src/applications/cache · high confidence

Introduces dedicated query and search engines for Herald rules, transcripts, and webhooks

This change adds new query classes (HeraldRuleQuery, HeraldTranscriptQuery, HeraldWebhookQuery, etc.) and corresponding search engines (HeraldRuleSearchEngine, HeraldTranscriptSearchEngine, HeraldWebhookSearchEngine) to the Herald application. For users, this means Herald rules can now be searched and filtered by author, rule type, content type, and active/disabled status directly through the application search interface. Transcripts are now queryable by object monograms or IDs, and webhooks can be searched by status (active/archived). These components provide the backend infrastructure for listing, filtering, and displaying these entities in the UI, replacing or supplementing previous ad-hoc loading mechanisms.

src/applications/herald/query · high confidence

Introduces modern query and search infrastructure for Differential objects

This change adds a suite of new query and search engine classes for Differential objects, including \DifferentialChangesetQuery\, \DifferentialDiffQuery\, \DifferentialHunkQuery\, and \DifferentialRevisionQuery\, along with their corresponding search engines. These new components replace legacy query mechanisms, enabling cursor-based paging, policy-aware access control, and standardized search fields (such as filtering by responsible users, authors, reviewers, repositories, and status). The update also introduces result bucketing logic (e.g., 'Must Review', 'Ready to Land') for the Differential dashboard and adds a repository lookup utility to infer the source repository for a diff.

src/applications/differential/query · high confidence

Introduces modular authentication engines for CSRF, passwords, sessions, and invites

The authentication engine is restructured into dedicated, modular components: PhabricatorAuthCSRFEngine handles CSRF token generation and validation with BREACH mitigation; PhabricatorAuthPasswordEngine centralizes password validation, blocklisting, and hashing upgrades; PhabricatorAuthSessionEngine manages session lifecycles, including anonymous sessions, high-security modes, and partial sessions; PhabricatorAuthInviteEngine processes email-based account invitations; and PhabricatorAuthSessionEngineExtension provides hooks for session lifecycle events. This refactoring separates concerns, improves testability, and lays the groundwork for more flexible authentication workflows.

src/applications/auth/engine · high confidence

Introduces modular infrastructure for key-value caching and database clustering

This change adds foundational infrastructure components to the platform. It introduces a unified key-value cache interface (\PhutilKeyValueCache\) with multiple implementations (APC, Memcache, in-memory, and on-disk) and composable wrappers (stacking, namespacing, and profiling) to support flexible caching strategies. Additionally, it adds configuration validation types for database clustering (\cluster.databases\) and mailer clustering (\cluster.mailers\), enabling administrators to define and manage multiple database hosts and mail adapters with specific roles and priorities.

src/infrastructure · high confidence

Introduction of DarkConsole error logging API

A new API class, DarkConsoleErrorLogPluginAPI, has been added to the console error log plugin. This class provides a centralized mechanism for registering an error handler that captures exceptions, standard errors, and Phlog messages into a static error list. It supports a discard mode to suppress error collection and exposes the collected errors for consumption by the DarkConsole interface, enabling better visibility into console execution issues.

src/applications/console/plugin/errorlog · high confidence

Introduction of PhabricatorFlaggableInterface

A new interface, PhabricatorFlaggableInterface, has been added to the codebase. It extends PhabricatorPHIDInterface and currently contains no additional methods, serving as a marker interface to identify objects that can be flagged within the system.

src/applications/flag/interface · high confidence

Introduction of Policy application entry point

A new PhabricatorPolicyApplication class has been added to define the Policy application's metadata and routing. This includes setting the application name to 'Policy', marking it as non-launchable and non-uninstallable, and registering routes for policy explanation and editing functionality.

src/applications/policy/application · high confidence

Introduction of the Auth application with comprehensive authentication and identity management routes

The new PhabricatorAuthApplication defines the core authentication entry point at /auth/ and registers a wide range of controllers to handle login, registration, password management, and external account linking. It introduces dedicated routes for managing SSH public keys, configuring multi-factor authentication (MFA) providers, sending SMS messages via contact numbers, and customizing onboarding messages. The application also exposes administrative capabilities for managing auth providers and includes specific endpoints for session termination, token revocation, and email verification, effectively centralizing user identity and access control logic.

src/applications/auth/application · high confidence

Introduction of the Config application with hierarchical admin layout

The Config application is now a distinct, pinned admin module accessible at /config/, featuring a full-width hierarchical layout. It consolidates various configuration tasks into specific sections: a main console, database cluster status and schema review, repository server administration, search cluster support, module/extension management, cache status and purging, and a comprehensive settings history view. The application is restricted to administrators by default and utilizes a sparkle emoji icon to denote its administrative nature.

src/applications/config/application · high confidence

Legalpad controller layer introduces signature management and public access

The Legalpad application controller layer is established with a new base controller and specific handlers for document listing, editing, management, and signing. This change introduces a complete signature workflow, allowing users to sign documents individually or as corporate representatives, with support for signature exemptions and email-based verification. The controllers enforce public access on key pages (signing, verification, done) to accommodate unauthenticated users, while managing navigation via a side-nav that includes a dedicated 'Find Signatures' search filter. Document management is handled through a dedicated controller that displays document properties, transaction timelines, and action curtains for viewing, editing, and signing.

src/applications/legalpad/controller · high confidence

Legalpad document and signature search capabilities

This change introduces new query and search engine classes for the Legalpad application, enabling users to filter and find documents and signatures with greater precision. Users can now search for Legalpad documents by specific criteria including creators, contributors, signers, and creation date ranges. Additionally, a dedicated search engine for signatures allows users to find signatures by signer, document, name, or email substring, and view signature status (such as verified, corporate, or unverified) directly in search results.

src/applications/legalpad/query · high confidence

Legalpad mail integration

Users can now interact with Legalpad documents via email. The new LegalpadMailReceiver and LegalpadReplyHandler classes enable the system to parse incoming emails addressed to Legalpad documents (identified by the 'L' prefix) and process replies through the standard transaction reply handler mechanism.

src/applications/legalpad/mail · high confidence

Macros can now have associated audio files and playback behaviors

Users can now attach audio files to image macros and configure how that audio plays. A new Audio controller allows administrators to upload an audio file and select a playback behavior: Do Not Play, Play Once (when the macro is viewed), or Play Continuously (treating the macro as an ambient audio source). The macro view page now displays the configured audio behavior and provides a link to edit the audio settings for those with management capabilities.

src/applications/macro/controller · high confidence

Make Maniphest task statuses and priorities user-configurable

Task statuses and priorities are no longer hardcoded; they are now driven by environment configuration (maniphest.statuses and maniphest.priorities). This allows administrators to customize status names, colors, icons, and keywords, as well as define custom priorities with associated labels and colors. The system now supports locking specific statuses to prevent comments or edits, disabling statuses or priorities entirely, and requiring Multi-Factor Authentication (MFA) for interactions with certain statuses. Additionally, a configurable points field can be enabled for tasks.

src/applications/maniphest/constants · high confidence

Manage OAuth client authorizations in Settings

Users can now review and revoke their OAuth client authorizations directly from the Settings panel. A new 'OAuth Authorizations' section displays a table of authorized applications, including the application name, scope, creation date, and last modification date, along with a 'Revoke' button to remove access for each client.

src/applications/oauthserver/panel · high confidence

Modernized People application with granular user management and profile capabilities

The People application has been completely rewritten to provide a more structured and secure user management experience. Administrators can now create standard, bot, and mailing-list user accounts through a dedicated workflow that enforces high-security sessions. User lifecycle actions—such as approving, disabling, empowering (promoting to admin), and renaming users—are now handled via explicit controllers and modular transactions, replacing older, less secure flows. The user profile view has been redesigned to display status tags (e.g., Administrator, Bot, Disabled), support profile pictures, and integrate with other applications like Badges and Diffusion (commits). Additionally, a new approval queue allows administrators to review and approve pending user accounts, and activity logs are now accessible for auditing user actions.

src/applications/people/controller · high confidence

Modular transaction types for Fund initiatives and backers

The Fund application now uses a modular transaction system for tracking changes to initiatives and backers. New transaction classes handle specific actions such as updating the initiative name, description, risks, status, and merchant, as well as managing backer status and refunds. This allows for more granular tracking and clearer change history for users editing or interacting with Fund initiatives.

src/applications/fund/xaction · high confidence

Modularize Celerity postprocessors and add new display modes

The Celerity postprocessor system has been refactored into a modular architecture, allowing users to select different visual themes via new postprocessors. This change introduces support for Dark Mode (Experimental), High Contrast colors, larger font sizes, and a Red/Green colorblind accessibility mode, in addition to the standard color scheme. Users can now customize their interface appearance and readability through these distinct display profiles.

src/applications/celerity/postprocessor · high confidence

Modularize configuration options into dedicated PHP classes

Configuration options are now organized into dedicated PHP classes (e.g., PhabricatorAWSConfigOptions, PhabricatorAccessLogConfigOptions, PhabricatorAuthenticationConfigOptions) that extend PhabricatorApplicationConfigOptions. This change introduces a new modular structure for managing settings, including support for custom UI types, validation, and contextual help. Specific options such as AWS integration keys, access log formats, and authentication provider configurations are now defined within these classes, allowing for better organization and maintainability of the configuration system.

src/applications/config/option · high confidence

Modularize temporary token types with a configuration panel

The authentication system now supports a modular architecture for temporary tokens, introducing a new 'Temporary Token Types' configuration panel in the application settings. This change adds specific implementations for 'One-Time Login' and 'Password Reset' tokens, both of which are revocable, and provides a base class to manage token type registration and display. Users can now view the registered temporary token types and their properties through the new module interface.

src/applications/auth/tokentype · high confidence

New 'bin search' CLI for managing search indexes

A new command-line interface is available for managing search infrastructure, providing commands to initialize or repair search services (\bin search init\), build or rebuild indexes with options to filter by object type, version, or date range and to run in the background (\bin search index\), recompute common ngrams with configurable thresholds (\bin search ngrams\), and execute raw search queries for debugging (\bin search query\). These workflows validate the \cluster.search\ configuration before execution to ensure consistency.

src/applications/search/management · high confidence

New 'conduit call' management command with local execution and user impersonation

A new 'bin/conduit call' command has been added to allow administrators to invoke Conduit methods directly from the command line. This tool supports reading parameters from a file or stdin, and includes a '--local' flag to force execution within the current process rather than proxying to another cluster host. It also features an '--as' flag to execute calls on behalf of a specific user, which is useful for profiling and testing user-specific behavior.

src/applications/conduit/management · high confidence

New CLI commands for approving, enabling, and empowering user accounts

The people management CLI now includes three new commands to manage user account states: \approve\ to approve pending accounts, \enable\ to re-enable disabled accounts, and \empower\ to grant administrator privileges. These commands provide a direct way for administrators to modify user status via the command line, replacing the previous \bin/people profileimage\ workflow for these specific administrative actions.

src/applications/people/management · high confidence

New CLI commands for audit management and synchronization

Administrators can now use the command line to manage audit data. The new 'bin/audit delete' command allows bulk removal of audit requests based on filters like user, repository, commit, date range, or status, with a dry-run mode for safety. The 'bin/audit synchronize' command updates commit audit statuses to reflect the current state of audit requests, fixing potential database inconsistencies. Additionally, 'bin/audit update-owners' refreshes package ownership relationships for commits based on affected paths.

src/applications/audit/management · high confidence

New CLI commands for managing Herald rules, testing rules, and calling webhooks

This change introduces several new command-line workflows in the Herald management application. Administrators can now use \bin/herald rule\ to enable or disable specific Herald rules by ID or monogram, bypassing standard policies. A new \bin/herald test\ command allows users to perform dry runs of content rules against specific objects to verify expected behavior, similar to the web UI test console. Additionally, \bin/webhook call\ enables manual triggering of webhooks with options to run in the background via the daemon queue, specify a count of calls, and set silent or secure flags.

src/applications/herald/management · high confidence

New CLI commands for managing inbound and outbound mail

Administrators now have a set of new \bin/mail\ subcommands to manage and diagnose mail traffic directly from the command line. You can list recent inbound and outbound messages (\list-inbound\, \list-outbound\), view detailed diagnostic information including headers and delivery reasons (\show-inbound\, \show-outbound\), and resend failed messages (\resend\). The suite also includes tools for testing mail configuration (\send-test\, \receive-test\), monitoring mail volume over a configurable time period (\volume\), and managing email verification status (\unverify\).

src/applications/metamta/management · high confidence

New CLI commands for managing the Aphlict notification server

Administrators now have a set of command-line workflows to control the Aphlict notification service. You can start, stop, restart, and check the status of the server, as well as run it in debug mode for diagnostics. Additionally, a new 'notify' command allows you to manually send test notifications to specific users to verify delivery. These commands rely on a new JSON configuration format that supports defining client and admin server ports, SSL settings (including chain files), and clustering options.

src/applications/aphlict/management · high confidence

New CLI commands to view and unlock object policies

Administrators can now use the command line to inspect and modify object access controls. The new 'bin/policy show' command displays the current view, edit, and owner policies for a specified object, including any special codex rules. Additionally, 'bin/policy unlock' allows administrators to grant specific users view, edit, or ownership permissions on an object by identifying it via its name (e.g., T123) or PHID, using flags like --view, --edit, or --owner to target the specific capability to change.

src/applications/policy/management · high confidence

New CLI management scripts for system administration

Added a suite of new command-line scripts in scripts/setup/ (including manage\_audit, manage\_auth, manage\_bulk, manage\_calendar, manage\_celerity, manage\_conduit, manage\_config, manage\_differential, manage\_feed, manage\_garbage, manage\_harbormaster, manage\_herald, manage\_i18n, manage\_lock, manage\_nuance, manage\_phortune, manage\_policy, manage\_remove, manage\_trigger, manage\_user, manage\_webhook, and manage\_worker) that provide administrative interfaces for managing various Phabricator subsystems such as audits, authentication, bulk jobs, calendar, static resources, API, configuration, code reviews, feeds, garbage collection, builds, automation rules, internationalization, locks, search, billing, policies, object removal, event triggers, user accounts, webhooks, and the task queue.

scripts/setup · high confidence

New CLI tools for silent bulk jobs and data export

Added new command-line workflows for bulk management: the \make-silent\ command allows administrators to configure specific bulk jobs to run without sending mail or publishing notifications, provided the job is in the confirm status; the \export\ command enables exporting transaction data to flat files (JSON, CSV, Excel, etc.) using specified search queries and formats, supporting multiple queries via union logic, explicit output paths, and an overwrite flag for existing files.

src/applications/transactions/bulk/management · high confidence

New CLI workflows to register hosts and manage SSH key trust in Almanac

Administrators can now use the \bin/almanac\ command-line interface to register a host as an Almanac device and manage the trust status of its SSH keys. The new \register\ workflow allows a host to associate itself with an existing Almanac device by providing a private key, storing the resulting public and private keys with correct permissions, and writing a device ID. The \trust-key\ and \untrust-key\ workflows allow administrators to explicitly mark or revoke trust for a public key associated with an Almanac device, which is required for the key to be used in device registration. These changes introduce a base \AlmanacManagementWorkflow\ class and support the secure, automated association of hosts with Almanac devices for cluster authorization.

src/applications/almanac/management · high confidence

New Celerity asset generation and merge scripts

Added three new scripts to the Celerity toolset: \generate\_emoji.php\ rebuilds emoji data sheets from \emoji\_strategy.json\, \generate\_sprites.php\ regenerates CSS sprite sheets (tokens, login) with optional \optipng\ optimization, and \install\_merge.sh\ configures Git to use the Celerity map merger for resolving conflicts in \map.php\.

scripts/celerity · high confidence

New Celerity management workflows for resource maps and syntax CSS

Added new command-line management workflows for the Celerity application, allowing administrators to rebuild static resource maps and regenerate syntax highlighting CSS files. The \CelerityManagementMapWorkflow\ iterates through all physical resources to regenerate their maps, while the \CelerityManagementSyntaxWorkflow\ generates and writes CSS files for all configured syntax styles to the webroot. These tools provide a dedicated interface for maintaining Celerity's static asset outputs.

src/applications/celerity/management · high confidence

New Conduit API Tokens settings panel

Administrators and users can now manage Conduit API tokens directly from the settings interface. A new 'Conduit API Tokens' panel has been added, allowing users to view active tokens, generate new ones, and terminate existing ones. The panel displays token names, types, creation dates, and expiration status, with specific access controls ensuring that mailing list users cannot access this management view.

src/applications/conduit/settings · high confidence

New Conduit API endpoints for Owners packages

This change introduces two new Conduit API methods for the Owners application: \owners.search\ allows users to read information about Owners packages, and \owners.edit\ enables creating or modifying Owners packages via the EditEngine. These additions provide programmatic access to search and manage owner package data.

src/applications/owners/conduit · high confidence

New Conduit API endpoints for managing and querying image macros

This change introduces a new set of Conduit API methods for the Macro application, enabling programmatic interaction with image macros. Users can now query macro details using \macro.query\ (filtering by author, PHID, ID, or name), create new memes via \macro.creatememe\ (specifying a template and text overlays), and edit or create macros using the standard \macro.edit\ endpoint. These additions provide a structured API for integrating macro generation and management into external tools and workflows.

src/applications/macro/conduit · high confidence

This change introduces a new Conduit API method, 'remarkup.process', which allows external clients to process text through various Remarkup engines (such as Differential, Maniphest, or Diffusion) by specifying a context. It also adds a new 'RemarkupValue' class to handle corpus and metadata for remarkup results. Additionally, a new 'PhabricatorRemarkupHyperlinkEngineExtension' is added to handle self-URI links, ensuring that links to Diffusion files and other internal resources are recognized and rendered with special behavior, while filtering for allowed protocols (http/https).

src/applications/remarkup · high confidence

New Conduit API for querying passphrase credentials

A new \passphrase.query\ Conduit method has been added, allowing users to retrieve details about stored credentials (such as SSH keys, passwords, and tokens) via the API. The method supports filtering by credential IDs or PHIDs and includes options to request secret material (\needSecrets\) and public keys (\needPublicKeys\). Access to sensitive material is strictly controlled: secrets are only returned if the credential is not locked and has API access enabled (\allowConduit\), ensuring that locked or restricted credentials remain inaccessible through this endpoint.

src/applications/passphrase/conduit · high confidence

New Conduit API method for searching transactions and comments

A new 'transaction.search' Conduit API method has been added, allowing users to retrieve transaction records and associated comments for a specific object (via PHID or identifier) or for all objects of a particular type. The method supports filtering by specific transaction PHIDs or author PHIDs, and returns enriched data including inline comments and structured information for modular transactions, facilitating use cases such as webhook implementations.

src/applications/transactions/conduit · high confidence

New Conduit API methods for Drydock resources

This change exposes several Drydock entities through the Conduit API, allowing external tools and scripts to interact with the system programmatically. New methods include \drydock.authorization.search\ to retrieve authorization information, \drydock.blueprint.search\ for listing blueprints, \drydock.blueprint.edit\ to create or modify blueprints, \drydock.lease.search\ to query lease details, and \drydock.resource.search\ to find available resources. These additions enable automation of Drydock resource management and authorization checks.

src/applications/drydock/conduit · high confidence

New Conduit API methods for SSH key management and session termination

This change introduces three new Conduit API methods to the authentication application: \auth.querypublickeys\ allows users to retrieve a list of their active SSH public keys with filtering options (by ID, PHID, object PHID, or key string); \auth.logout\ enables users to terminate all active web login sessions and, if applicable, revoke the current OAuth token; and a base abstract class \PhabricatorAuthConduitAPIMethod\ is added to standardize application context and status for these new methods. These additions provide programmatic control over SSH key visibility and session security via the API.

src/applications/auth/conduit · high confidence

New Conduit API methods for flags and PHID lookups

This change introduces new Conduit API endpoints for managing flags and resolving PHIDs. In the flag application, users can now query, create, edit, and delete flags via the \flag.query\, \flag.edit\, and \flag.delete\ methods, which support filtering by owner, type, and object PHID, as well as setting custom colors and notes. In the PHID application, the \phid.query\ method allows retrieving information for a list of PHIDs, and \phid.lookup\ enables resolving objects by name; the older \phid.info\ method is marked as deprecated in favor of \phid.query\. These methods return structured dictionaries containing handle information such as URIs, names, and status.

src/applications/flag/conduit, src/applications/phid/conduit · high confidence

New Conduit API methods for managing tokens

This change introduces three new Conduit API endpoints for the Tokens application: \token.query\ allows users to list available tokens, \token.given\ enables querying which objects have been granted specific tokens, and \token.give\ allows granting or revoking token access for objects. These methods are implemented as new Conduit API classes that extend a shared base class, providing a structured way to interact with the token system via the API.

src/applications/tokens/conduit · high confidence

New Conduit API methods for querying and recording chat logs

This change introduces two new Conduit API endpoints for the ChatLog application: \chatlog.query\ and \chatlog.record\. The \chatlog.query\ method allows users to retrieve chat log entries, supporting optional filtering by channel IDs and a configurable limit (defaulting to 100). The \chatlog.record\ method enables users to submit new chat log entries in bulk, automatically creating the necessary channel records if they do not already exist. Both methods are marked as unstable.

src/applications/chatlog/conduit · high confidence

New Configuration Console with Library Version Tracking

The Config application now includes a new console interface that provides a central hub for managing settings, reviewing setup issues, viewing service statuses, and checking installed extensions. A key addition is the 'Version Information' section, which displays the current version, commit hash, date, and branchpoint for core libraries like Phabricator and Arcanist, helping administrators verify their deployment state.

src/applications/config/controller · high confidence

New Differential management CLI commands for commits, hunks, and changesets

The Differential management area now exposes several new CLI workflows to give administrators more control over revision data. You can now extract diffs from commits (\extract\), explicitly attach commits to revisions (\attach-commit\), and rebuild changesets for a specific revision (\rebuild-changesets\). Additionally, a new \migrate-hunk\ command allows you to move hunk data between storage engines (text vs. file) or automatically optimize storage formats, supporting both single-hunk and bulk migrations with dry-run capabilities.

src/applications/differential/management · high confidence

New Differential search attachments, hovercard extension, and mail stamps

This change introduces four new engine extensions for the Differential application. Users can now retrieve local commit information for diffs via the new 'Diff Commits' search attachment, and search for revisions by reviewer using the 'Differential Reviewers' search attachment. Hovercards for Differential revisions now display the author, a list of reviewers, and a truncated summary. Additionally, email notifications for revisions now include stamps for the author, reviewers (including blocking and resigned statuses), the revision repository, and the modern revision status.

src/applications/differential/engineextension · high confidence

New Differential typeahead tokens for blocking reviewers, exact users, and revision status

The Differential typeahead now supports several new query tokens. You can add blocking reviewers using the \blocking(user)\ function, which marks a reviewer as required to approve changes. The \exact(user)\ token allows you to filter results to only those associated with a specific user, excluding their projects or packages. Additionally, you can find revisions with no reviewers using \none()\, and filter by open or closed status using \open()\ and \closed()\ functions. The 'Responsible Users' token has also been modernized to include these new capabilities.

src/applications/differential/typeahead · high confidence

New Diffusion configuration options for SSH, Git LFS, and audit behavior

This change introduces a new configuration file for Diffusion that exposes several new settings to users. Administrators can now configure SSH connection details, including a custom SSH host, port, and username, which are locked to prevent runtime modification. Git Large File Storage (LFS) support is now explicitly configurable via a boolean option. Additionally, the system allows users to control whether commit authors can accept their own audits via the 'audit.can-author-close-audit' setting, and provides controls for attaching or inlining patches in Diffusion email notifications. The configuration also includes options for linking external bug trackers and managing custom repository fields.

src/applications/diffusion/config · high confidence

New Diffusion engine classes for commit drafts, hooks, and timeline

Added three new engine classes in the Diffusion application: DiffusionCommitDraftEngine, which checks for publishable inline comments on commits; DiffusionCommitHookEngine, which manages pre-commit hook execution including rejection of dangerous changes, oversized files, and enormous changes, as well as Herald rule application; and DiffusionCommitTimelineEngine, which generates audit transaction views for commit timelines.

src/applications/diffusion/engine · high confidence

New Diffusion query classes for commit resolution, auditing, and repository metadata

This change introduces a suite of new query classes in the Diffusion application to improve commit handling, auditing workflows, and repository metadata management. DiffusionCachedResolveRefsQuery provides a fast, database-backed method for resolving Git, Mercurial, and Subversion references (commits, branches, tags) without contacting the VCS service. DiffusionCommitQuery is expanded with new capabilities including ancestry filtering (ancestorsOf), epoch range filtering, and identity loading, while DiffusionCommitHintQuery handles commit hints like rewrites. Auditing is enhanced with DiffusionCommitRequiredActionResultBucket, which groups commits by action status (Needs Attention, Needs Verification, Ready to Audit, etc.), and DiffusionDiffInlineCommentQuery allows querying inline comments by commit. Additional new classes include DiffusionCommitRevisionQuery for linking commits to revisions, DiffusionLintCountQuery for counting lint issues by path, DiffusionPullLogSearchEngine for searching pull logs, DiffusionRepositoryIdentitySearchEngine for managing commit identities, DiffusionResolveUserQuery for mapping author/committer names to users, and DiffusionRenameHistoryQuery for tracking file renames across commits.

src/applications/diffusion/query · high confidence

New Diffusion views for branches, tags, logs, and repository browsing

This change introduces a suite of new PHP view classes for the Diffusion application, providing dedicated UI components for browsing repository branches (DiffusionBranchListView), tags (DiffusionTagListView), and commit graphs (DiffusionCommitGraphView). It also adds views for displaying pull logs (DiffusionPullLogListView), push logs (DiffusionPushLogListView), and intracluster sync logs (DiffusionSyncLogListView), along with supporting views for repository clone URIs (DiffusionCloneURIView), README files (DiffusionReadmeView), pattern search results (DiffusionPatternSearchView), and empty browse results (DiffusionEmptyResultView). These components collectively modernize the Diffusion interface by unifying history and branch displays, exposing detailed push/pull/sync metadata, and improving the rendering of repository metadata and search results.

src/applications/diffusion/view · high confidence

New DiffusionPathIDQuery class for repository path resolution

A new DiffusionPathIDQuery class has been added to handle repository path lookups and normalization. This component allows users to query path IDs for a list of paths by normalizing them and mapping them against the repository's path table. It also provides utility methods for canonical path normalization, determining parent directories (with specific handling for Windows paths), and expanding a path to its full hierarchy of parent directories up to the root.

src/applications/diffusion/query/pathid · high confidence

New Diviner documentation view components

Added four new view classes to the Diviner application to structure generated PHP documentation: DivinerBookItemView for rendering book items with titles, subtitles, and types; DivinerParameterTableView and DivinerReturnTableView for displaying function parameters and return values in structured tables; and DivinerSectionView for organizing documentation content with headers. These components rely on the new 'diviner-shared-css' resource and integrate with existing PHUIHeaderView for section headers.

src/applications/diviner/view · high confidence

New Diviner query and search engine classes for atoms and books

This change introduces new query classes (DivinerAtomQuery, DivinerBookQuery, DivinerLiveBookTransactionQuery) and a search engine (DivinerAtomSearchEngine) within the Diviner application. These classes enable querying documentation atoms and books with filters such as name, type, book PHID, and repository, and support searching for 'ghost' atoms (symbols that no longer exist but have historical metadata). The search engine provides a UI for filtering by name, type, book, and repository, and renders results in the application search interface.

src/applications/diviner/query · high confidence

New Doorkeeper feed workers for Asana and JIRA integration

This change introduces \DoorkeeperFeedWorker\ as a base class for publishing Phabricator feed stories to external systems, along with concrete implementations \DoorkeeperAsanaFeedWorker\ and \DoorkeeperJIRAFeedWorker\. The Asana worker publishes tasks and updates them based on Phabricator object changes, mapping users to Asana accounts and handling OAuth tokens. The JIRA worker posts comments and/or links to JIRA issues when configured, using the JIRA Issues field to identify linked objects. Both workers respect the new \phabricator.silent\ configuration to suppress outbound events.

src/applications/doorkeeper/worker · high confidence

New Drydock SSH command interface with configurable timeouts and suppressed host-key warnings

The Drydock application now includes a new SSH-based command interface (DrydockSSHCommandInterface) that allows remote command execution over SSH. This interface supports configurable connection timeouts via setConnectTimeout, suppresses the 'Permanently added ... to the list of known hosts' warning by disabling strict host key checking and setting LogLevel to ERROR, and uses batch mode for non-interactive execution. It loads SSH credentials from a PassphraseSSHKey and applies working directory context to commands.

src/applications/drydock/interface/command · high confidence

New Drydock blueprint policy capabilities

This change introduces three new policy capabilities for Drydock blueprints: 'Can Create Blueprints' (drydock.blueprint.create), 'Default Blueprint Edit Policy' (drydock.default.edit), and 'Default Blueprint View Policy' (drydock.default.view). These capabilities allow administrators to define specific permissions for creating, editing, and viewing blueprints, with the view policy explicitly allowing public policy settings.

src/applications/drydock/capability · high confidence

New Drydock management CLI commands for lease and resource lifecycle

The \bin/drydock\ CLI now includes a suite of management workflows for controlling Drydock resources and leases. Users can acquire leases with \bin/drydock lease\ (supporting JSON attributes, blueprint filtering, and multiple counts), run commands on leased resources via \bin/drydock command\, and manage the lifecycle through \release-lease\, \release-resource\, \update-lease\, \update-resource\, and \reclaim\ commands. These changes introduce explicit release and reclaim capabilities, allowing administrators to manually free resources or reclaim unused active ones, and ensure leases are released if the acquisition process is interrupted.

src/applications/drydock/management · high confidence

New EditEngine-based configuration for Calendar Events, Imports, and Exports

Users can now configure Calendar Events, Imports, and Exports through dedicated EditEngine forms. Event editing supports fields for name, host, invitees, description, icon, and recurrence, with specific controls for all-day events and series editing (this event vs. all future events). Import configurations allow users to set automatic update frequencies (hourly or daily) and manually reload or delete imported events. Export configurations let users define query keys and policy modes for exporting calendar data.

src/applications/calendar/editor · high confidence

New Fact application controllers for charting and object inspection

This change introduces the controller layer for the new Facts application, enabling users to view fact-driven charts and inspect the data sources for specific objects. PhabricatorFactHomeController serves as the entry point, redirecting to a demo chart. PhabricatorFactObjectController generates a detailed report for any object, listing facts extracted by various engines, their current values, and timing costs, while PhabricatorFactChartController handles the rendering of stored charts, supporting both synchronous page loads and asynchronous data fetching for dynamic updates.

src/applications/fact/controller · high confidence

New Feed application controllers for listing, details, and transactions

The feed is now its own application with dedicated controllers: PhabricatorFeedListController handles the main feed list and transaction logs, PhabricatorFeedDetailController provides a permalink view for individual feed stories (including a plain-text endpoint), and PhabricatorFeedTransactionListController exposes transaction-specific listings. These controllers establish the routing and page structure for the new feed application.

src/applications/feed/controller · high confidence

New HTTP header parser for key-value pair extraction

Added a new AphrontHTTPHeaderParser class that parses raw HTTP headers into name and content, and further extracts key-value pairs from the content (e.g., Content-Type parameters). The parser handles quoted and unquoted values, semicolon-separated pairs, and throws an exception for unterminated quotes. A corresponding test case validates parsing of various header formats including form-data, charset, and boundary parameters.

src/aphront/headerparser · high confidence

New Harbormaster build log and test result views

This change introduces new view classes for the Harbormaster application to improve the presentation of build logs, lint results, and unit test outcomes. Users can now view build logs with line highlighting and a dedicated 'Download Log' button, see lint messages in a structured table with severity and location details, and view unit test results in a summary table that includes status icons, execution duration, and links to full test details. These views replace previous inline or less structured displays, providing a clearer and more navigable interface for build artifacts.

src/applications/harbormaster/view · high confidence

New Harbormaster build steps for external CI, Drydock, and build control

Harbormaster now includes several new build step implementations to extend build capabilities. You can trigger builds in external CI systems via the 'Build with Buildkite' and 'Build with CircleCI' steps, which integrate with their respective APIs and webhooks. The 'Lease Working Copy' and 'Drydock: Run Command' steps allow builds to acquire and execute commands on Drydock-managed working copies. For build flow control, the 'Abort Older Builds' step can cancel running builds on older diffs, while 'Wait for Previous Commits to Build' ensures sequential processing of commits. Additionally, the 'Make HTTP Request' step enables generic HTTP calls with optional authentication, and 'Arcanist Lint Results' and 'Arcanist Unit Results' steps provide automatic integration for Arcanist tooling.

src/applications/harbormaster/step · high confidence

New Harbormaster management CLI workflows for build and log administration

This change introduces a suite of new command-line management workflows for Harbormaster, providing administrators and developers with direct control over build lifecycles and log data. Users can now manually trigger builds via the \build\ command, restart active or specific builds using \restart\, and force-update build statuses with \update\. Log management is enhanced with \archive-logs\ to compress or decompress stored logs, \rebuild-log\ to regenerate file summaries (with \--all\ and \--force\ options), and \write-log\ to inject arbitrary content for testing live streaming. Additionally, a \publish\ workflow allows manual publication of buildables, and all workflows extend a new base \HarbormasterManagementWorkflow\ class for consistent structure.

src/applications/harbormaster/management · high confidence

New Harbormaster search engines and query classes for builds, targets, and artifacts

This change introduces a comprehensive set of new query and search engine classes for the Harbormaster application, enabling structured searching and filtering of build-related entities. Specifically, it adds search engines and queries for Harbormaster Artifacts, Build Logs, Build Messages, Build Plans, Builds, Build Steps, Build Targets, and Buildables. These classes provide filtering capabilities by ID, PHID, status, date ranges, and associated objects (e.g., searching builds by plan, initiator, or status; searching targets by build, date, or status). The search engines also define custom search fields for user-facing searches, such as filtering build plans by name or status, and buildables by object, container, or manual/automatic type. This infrastructure supports the underlying search and API functionality for Harbormaster.

src/applications/harbormaster/query · high confidence

New Herald actions to manage subscriptions

Users can now use Herald rules to automatically add or remove subscribers from objects. This change introduces four new actions: 'Add me as a subscriber' and 'Remove me as a subscriber' for personal rules, and 'Add subscribers' and 'Remove subscribers' for general rules. The implementation ensures that adding subscribers respects previous unsubscription preferences and does not affect users who are automatically subscribed, while providing clear logging for these edge cases.

src/applications/subscriptions/herald · high confidence

New Herald rules for Maniphest task status and priority

Users can now create Herald rules that automatically change a Maniphest task's status or priority. This change introduces new Herald actions ('Change status to' and 'Change priority to') and corresponding fields ('Status' and 'Priority') for Maniphest tasks, allowing automation based on these specific task attributes.

src/applications/maniphest/herald · high confidence

New ICS file and URI import engines for Calendar

Users can now import calendar events from local .ics files or remote URIs. The new file engine allows uploading an .ics file directly, while the URI engine supports subscribing to external calendar sources via URL. Both engines parse the ICS data, log warnings or errors for invalid entries, and reject events with out-of-range dates or excessively high recurrence frequencies to ensure stability.

src/applications/calendar/import · high confidence

New MFA provider management and status controllers

This change introduces a new set of controllers for managing Multi-Factor Authentication (MFA) providers, enabling administrators to view, edit, and customize enrollment messages for different MFA factors. The new \PhabricatorAuthFactorProviderListController\ displays a list of configured providers with their status, while \PhabricatorAuthFactorProviderEditController\ allows administrators to select and configure specific factor types. A new \PhabricatorAuthFactorProviderMessageController\ provides a UI for customizing the enrollment guidance text shown to users when they add a factor. Additionally, \PhabricatorAuthChallengeStatusController\ supports live-updating the UI status of MFA challenges during login, and \PhabricatorAuthFactorProviderViewController\ provides a detailed view of individual provider configurations.

src/applications/auth/controller/mfa · high confidence

New Maniphest hovercards and mail stamps

This change introduces new engine extensions for Maniphest tasks. Users will now see a modernized hovercard UI when hovering over tasks, displaying owner and project information via the new PHUIHovercard-based implementation. Additionally, email notifications for tasks now include more detailed stamps, such as author, task owner, unassigned status, priority, status, and subtype, providing richer context in mail headers.

src/applications/maniphest/engineextension · high confidence

New Maniphest query and search infrastructure

This change introduces the core query and search classes for Maniphest tasks, including \ManiphestTaskQuery\, \ManiphestTaskSearchEngine\, and \ManiphestTransactionQuery\. \ManiphestTaskQuery\ provides a comprehensive API for filtering tasks by criteria such as ID, PHID, owner, author, subscriber, status, priority, dates (created, modified, closed), parent/subtask relationships, and grouping. \ManiphestTaskSearchEngine\ exposes these capabilities through a standardized search UI, adding fields for assigned users, authors, statuses, priorities, subtypes, columns, open parents/subtasks, and date ranges, while also supporting custom page sizes. \ManiphestTransactionQuery\ handles querying task transaction history. This infrastructure replaces previous ad-hoc query mechanisms with a unified, cursor-paged, policy-aware system.

src/applications/maniphest/query · high confidence

New Owners package queries and search integration

This change introduces new query classes for the Owners application, enabling more robust retrieval and filtering of owner packages. Specifically, it adds PhabricatorOwnersPackageQuery to support filtering by owner or authority PHIDs, repository, paths, status, and name ngrams, while also handling control logic for archived packages. A corresponding search engine (PhabricatorOwnersPackageSearchEngine) is added to expose these capabilities in the application search interface, allowing users to search for packages by authority, name, repository, paths, and status, with built-in queries for 'All Packages', 'Active Packages', and 'Owned' packages. Additionally, PhabricatorOwnerPathQuery is added to load affected paths for a given repository commit, and PhabricatorOwnersPackageTransactionQuery is introduced to handle transaction queries for owner packages.

src/applications/owners/query · high confidence

New PHID query infrastructure for handles, objects, and lists

This change introduces three new query classes in the PHID application to centralize and improve how objects are looked up and handled. PhabricatorObjectQuery now supports loading objects by both PHID and name, with improved handling of in-flight requests to prevent infinite recursion during policy checks. PhabricatorHandleQuery provides a dedicated mechanism for resolving PHIDs to user-facing handles, correctly distinguishing between complete objects, restricted (policy-filtered) objects, and invalid entries without raising policy exceptions. PhabricatorObjectListQuery adds robust parsing for comma-separated lists of object names or monograms, including support for suffixes and type validation, which enhances the reliability of fields like reviewers and subscribers in the CLI and web UI.

src/applications/phid/query · high confidence

New PHID resolvers for Users and Projects

Added new PHID resolver classes for Users and Projects that allow converting usernames and project names into their corresponding PHIDs. The PhabricatorUserPHIDResolver handles @username lookups, while PhabricatorProjectPHIDResolver handles \#project-name lookups, both extending a base resolver that normalizes mixed input lists.

src/applications/phid/resolver · high confidence

New Packages API methods and transaction types

This change introduces the Conduit API endpoints and transaction types required to manage Packages, Publishers, and Versions. Specifically, it adds \packages.package.edit\, \packages.package.search\, \packages.publisher.edit\, \packages.publisher.search\, \packages.version.edit\, and \packages.version.search\ methods, enabling programmatic creation and querying of these entities. It also defines the underlying transaction types (e.g., \packages.package.key\, \packages.publisher.name\) that enforce validation rules, such as ensuring unique keys and preventing modification of immutable fields like package keys or publisher assignments after creation.

src/applications/packages/conduit, src/applications/packages/phid, src/applications/packages/xaction · high confidence

New People Engine Extensions for Hovercards, Menu, Search, and Datasources

This change introduces four new engine extensions in the People application to enhance user interaction and search capabilities. The PeopleHovercardEngineExtension now renders detailed user hovercards, including profile images and availability status, when hovering over user handles. The PeopleMainMenuBarExtension replaces the previous menu implementation, providing a user account dropdown with profile, settings, and logout actions, while ensuring menu items are only shown after a full session is established. Additionally, the PhabricatorPeopleAvailabilitySearchEngineAttachment allows users to filter search results by user availability, and the PhabricatorPeopleDatasourceEngineExtension integrates the People datasource into global search, enabling quick navigation to user profiles or the people directory using the 'u' prefix.

src/applications/people/engineextension · high confidence

New Phame Conduit API endpoints for blog and post management

This change introduces four new Conduit API methods to the Phame application, enabling programmatic interaction with blogs and posts. Users can now create or edit blogs via \phame.blog.edit\, search for blogs using \phame.blog.search\, create or edit blog posts via \phame.post.edit\, and search for posts using \phame.post.search\. These endpoints extend the existing Phabricator edit and search engine frameworks to support Phame-specific content types.

src/applications/phame/conduit · high confidence

New Phame blog and post list views

This change introduces several new view classes for the Phame blogging application, including PhameBlogListView, PhameDescriptionView, PhameDraftListView, PhameNextPostView, and PhamePostListView. These views provide the UI for listing blogs, displaying blog descriptions, managing draft posts, navigating between posts, and listing blog posts with support for external/live URIs and blogger information.

src/applications/phame/view · high confidence

New Phortune UI views for orders, charges, and subscriptions

This change introduces a suite of new view components in the Phortune application to improve the presentation of billing data. Users will now see structured tables for charges (PhortuneChargeTableView), orders (PhortuneOrderTableView), and subscriptions (PhortuneSubscriptionTableView), which display key details like amounts, statuses, and merchant information. Additionally, new views provide detailed breakdowns for individual orders, including item lists (PhortuneOrderItemsView), descriptions (PhortuneOrderDescriptionView), and comprehensive summaries (PhortuneOrderSummaryView) that handle various order states and printable formats. A new credit card form (PhortuneCreditCardForm) is also added to streamline payment method entry with specific validation and security assurance displays.

src/applications/phortune/view · high confidence

New Phrequent Conduit API methods for time tracking

This change introduces three new Conduit API methods for the Phrequent application: \phrequent.push\ to start tracking time on an object, \phrequent.pop\ to stop tracking time on an object, and \phrequent.tracking\ to retrieve the current list of objects being tracked. These methods allow external tools and scripts to programmatically manage time tracking sessions within Phrequent.

src/applications/phrequent/conduit · high confidence

New Phriction query and search engines for documents, content, and transactions

Phriction now uses dedicated query classes (PhrictionDocumentQuery, PhrictionContentQuery, PhrictionTransactionQuery) and search engines (PhrictionDocumentSearchEngine, PhrictionContentSearchEngine) to load and search wiki data. This enables searching documents by path, parentPaths, or ancestorPaths, supports hierarchical policy checks so users only see documents whose ancestors are visible, and introduces a phriction.content.search API method for content queries. The search engines also expose status-based filtering (active/all) and integrate with the application search UI for document listings.

src/applications/phriction/query · high confidence

Users can now reference Diffusion objects directly in text using new Remarkup rules. You can link to specific commits using their PHID, and reference repositories using either their numeric ID (prefix 'R') or their callsign (prefix 'r'). Additionally, a new {src ...} syntax allows flexible linking to source files within a repository, supporting options for specific lines, commits, or branches.

src/applications/diffusion/remarkup · high confidence

New Services section in Config to monitor infrastructure health

A dedicated 'Services' area has been added to the Config application, providing a hierarchical navigation menu and status dashboards for key infrastructure components. Administrators can now view the operational status of database servers (including connection latency, replication delay, and health checks), cache systems (opcode and data cache memory usage and entry counts), and cluster services such as search, notification, and repository servers. The section also includes a 'Schemata Issues' view that lists database schema mismatches by severity, allowing admins to quickly identify and resolve configuration drift.

src/applications/config/controller/services · high confidence

New UI Example Render Controller

A new controller, PhabricatorUIExampleRenderController, has been added to handle the rendering of UI examples. It dynamically loads example classes using PhutilClassMapQuery, groups them by category for navigation, and renders the selected example within a standard page layout, allowing users to view and interact with various UI components directly.

src/applications/uiexample/controller · high confidence

New UI component examples for the redesigned interface

The UIExamples application now includes demonstration pages for the new PHUI component library, showcasing the updated visual design. These examples cover Action Panels, Badges, Big Info views, Boxes, Button Bars, Buttons, Color Palettes, Feed Stories, Hovercards, Icons, Image Masks, Info views, Left-Right layouts, Lists, and Object Item Lists, allowing users to preview the new styling and layout capabilities.

src/applications/uiexample/examples · high confidence

New UI for managing authentication providers

Administrators can now manage authentication providers through a dedicated configuration interface under the 'Login and Registration' section. This includes a list view of all configured providers, a new provider selection dialog, and full create/edit workflows for individual providers. The new controllers support enabling or disabling providers, configuring login and registration permissions, and managing provider-specific settings like email trust and auto-login. The interface also respects the 'auth.lock-config' environment setting to prevent unauthorized changes.

src/applications/auth/controller/config · high confidence

New VCS Password settings panel for HTTP repository access

Administrators and users can now manage their Version Control System (VCS) passwords directly through a dedicated settings panel. This change introduces a new UI for setting, changing, or removing the password required to access Diffusion repositories over HTTP. The panel includes password validation, support for revoking existing passwords, and displays the current hashing algorithm. It also provides a randomly generated password suggestion to help users create strong credentials, with the tone of the suggestion varying based on the 'serious business' configuration.

src/applications/diffusion/panel · high confidence

New \`scripts/sql/manage\_storage.php\` script for database schema management

A new PHP script, \scripts/sql/manage\_storage.php\, has been added to handle database storage and schema versioning. It provides a \storage\ workflow with an \upgrade\ subcommand, allowing administrators to initialize or upgrade the database schema. The script supports explicit connection parameters via \--host\, \--ref\, \--user\, and \--password\ flags, and includes options for dry runs (\--dryrun\) and disabling utf8mb4 support (\--disable-utf8mb4\) for testing purposes. It validates that databases are configured before attempting operations and handles credential management using \PhutilOpaqueEnvelope\ for passwords.

scripts/sql · high confidence

New almanac management CLI script

A new command-line script, scripts/almanac/manage\_almanac.php, has been added to manage the Almanac host directory. The script initializes a Phutil argument parser with a synopsis indicating the feature is new and experimental, and dynamically loads management workflows by querying for classes extending AlmanacManagementWorkflow using PhutilClassMapQuery.

scripts/almanac · high confidence

New application management interface with install/uninstall and policy editing

The Applications meta-application now provides a dedicated detail view for each application, displaying its status (Installed/Uninstalled), description, and policy capabilities. Administrators can now install or uninstall applications directly from this view, with specific protections for essential applications like Home. The interface also includes a new policy editing page that allows administrators to modify access rules for application capabilities, supporting custom policy templates and locked policy settings. Additionally, a new documentation page is available to explain mail commands for interacting with objects via email.

src/applications/meta/controller · high confidence

New authentication UI components for external accounts, SSH keys, and administrative invites

This change introduces several new view classes in the authentication module to enhance the user interface for account management and administrative tasks. Users can now see detailed information for linked external accounts, including display names, provider types, and profile images, via the new PhabricatorAuthAccountView. The interface for managing SSH public keys has been expanded with PhabricatorAuthSSHKeyTableView, which displays key details (ID, name, trust status, comment, type, and creation date) and provides action menus for uploading or generating keys, with support for showing trusted status and key IDs. Additionally, PhabricatorAuthInviteActionTableView presents a table of administrative invite actions, showing raw and parsed addresses, associated users, and any issues, while PhabricatorAuthChallengeUpdate serves as a data structure to handle retry states and markup for authentication challenges.

src/applications/auth/view · high confidence

New authentication providers for Amazon, Asana, Bitbucket, Disqus, and JIRA

Administrators can now configure Amazon, Asana, Bitbucket, Disqus, and JIRA as external authentication providers. The Amazon provider requires HTTPS and provides configuration guidance for its API project. Asana and JIRA providers support linking to external tasks via the Doorkeeper integration. Bitbucket and Disqus providers allow users to log in using their respective OAuth credentials. These new providers integrate with the existing modular authentication infrastructure, allowing them to be enabled, disabled, and configured alongside other providers like Google, GitHub, and Facebook.

src/applications/auth/provider · high confidence

New badge icon selection options available

Users can now choose from a wider variety of icons when customizing badges. This change introduces a new icon set containing 25 distinct options, including themes like Star Wars (Empire, Rebel, First Order), professional roles (Coder, Serious Business), and general concepts (Superstar, Cake Day, Liquid Lunch).

src/applications/badges/icon · high confidence

New bin/auth command-line tool for authentication management

A new \bin/auth\ CLI tool is introduced to manage authentication configuration and troubleshoot issues without requiring web UI access. This tool provides specific subcommands for administrators: \recover\ to generate one-time login links for locked-out accounts (including a \--force-full-session\ flag to bypass MFA), \revoke\ to invalidate leaked credentials (with options to list, filter by type/user, or revoke everywhere), \strip\ to remove multi-factor authentication factors from users, \lock\/\unlock\ to prevent or allow changes to authentication provider configuration, \trust-oauth-client\/\untrust-oauth-client\ to manage OAuth client trust levels, \refresh\ to manually refresh OAuth tokens for debugging, \ldap\ to diagnose LDAP connectivity and configuration, \list-factors\ and \list-mfa-providers\ to inspect available MFA options, \verify\ to manually verify email addresses, \unlimit\ to reset rate-limit counters, and \cache-pkcs8\ to work around SSH key generation issues on macOS. These workflows extend a new base \PhabricatorAuthManagementWorkflow\ class.

src/applications/auth/management · high confidence

New bulk job management and enhanced daemon console

Administrators can now manage background bulk operations through a new 'Bulk Jobs' section in the Daemon console, featuring a list view, a detail page with transaction history, and a monitor page that displays a real-time progress bar and allows users to confirm and start jobs. The Daemon console itself has been updated to show a queue utilization statistic (approximate percentage of time daemons spend working versus overhead) and a table of recently completed tasks with average duration and queue time, providing better visibility into system performance.

src/applications/daemon/controller · high confidence

New calendar parser data model and ICS import/export support

The calendar application now includes a dedicated data model and parser for iCalendar (ICS) files. This change introduces a new set of classes in the \src/applications/calendar/parser/data/\ directory to represent calendar structures, including \PhutilCalendarDocumentNode\, \PhutilCalendarEventNode\, and \PhutilCalendarRecurrenceRule\, along with support for absolute and relative date-times and recurrence sets. Additionally, \PhutilICSParser\ and \PhutilICSWriter\ have been added to enable parsing ICS data into this model and exporting calendar events back to ICS format, allowing users to import and export calendar data using the standard iCalendar format.

src/applications/calendar/parser · high confidence

New calendar utility classes for time calculations and ICS export

Added two new utility classes to the calendar application: CalendarTimeUtil, which provides static methods for generating time ranges and timestamps for different calendar views (such as the conpherence widget and profile view), and PhabricatorCalendarICSWriter, which handles the generation of ICS calendar documents by processing events and their child events. These utilities support the underlying logic for displaying calendar data and exporting calendar events.

src/applications/calendar/util · high confidence

New calendar view components for event display, user availability, and import logs

This change introduces three new view classes in the calendar application to improve the user interface. AphrontCalendarEventView provides the rendering logic for individual calendar events, supporting properties like host, time range, and invitation status. PHUIUserAvailabilityView displays a user's current status (Available, Busy, or Away) with contextual details, including links to the event causing a 'Busy' or 'Away' state. PhabricatorCalendarImportLogView presents a table of calendar import logs, optionally showing the import source, to help users monitor and understand import results.

src/applications/calendar/view · high confidence

New command-line tool for managing caches

A new \bin/cache\ command is introduced to allow administrators to manage readthrough caches. This includes a \purge\ subcommand that can drop data from all caches or specific ones by name, providing a centralized way to clear cache state without restarting services.

src/applications/cache/management · high confidence

New commit search engines and query constraints for Audit

The Audit application now includes dedicated search engines (\DiffusionInternalCommitSearchEngine\, \PhabricatorCommitSearchEngine\) and a transaction query class (\PhabricatorAuditTransactionQuery\) to manage commit data. Users can now filter commits by specific repositories, responsible users, authors, auditors, packages, and audit status. New constraints allow searching for commits by identifier (hash), finding commits that are ancestors of a specific ref, and filtering by reachability (unreachable vs. permanent commits). Prebuilt filters for 'Active Audits', 'Authored', and 'Audited' commits are also available for logged-in users.

src/applications/audit/query · high confidence

New configurable Home profile menu with drag-and-drop upload support

The Home application now uses a new, configurable profile menu engine that structures the sidebar with a Default Home Dashboard, a 'Favorites' label, pinned applications, a launcher, and a manage item. This change enables users to drag and drop files to upload them directly onto the Home page or any Home dashboard, as the new engine explicitly integrates the global upload target view into the menu item content.

src/applications/home/engine · high confidence

New configuration options for Asana integration

Administrators can now configure the Asana integration via two new settings: 'asana.workspace-id' to specify the target workspace for synchronization, and 'asana.project-ids' to map specific applications (like Differential) to Asana projects. The configuration page includes contextual help that lists available workspaces and publisher classes to assist with setup.

src/applications/doorkeeper/option · high confidence

New controllers for transaction comment management and form configuration

This change introduces a suite of new controllers in the transactions application to support granular comment operations and EditEngine form configuration. Comment management is now handled by dedicated controllers for editing, removing, viewing history, quoting, and viewing raw content, including MFA enforcement for signed comments and locking restrictions. Additionally, form configuration is exposed through controllers that allow administrators to reorder, lock, hide, and set defaults for form fields, as well as manage form subtypes, enable/disable forms, and mark them as default create or edit forms.

src/applications/transactions/controller · high confidence

New credential selection control with restricted credential handling

The Passphrase application now includes a dedicated UI control for selecting credentials, allowing users to choose from existing options or add new ones. This control supports optional null selection and default username hints. Crucially, it implements logic to handle restricted credentials: if a user editing a form references a credential they do not have permission to view, the system gracefully displays the credential's monogram (marked as 'Restricted Credential') using an omnipotent user context, ensuring the form can be saved without exposing sensitive details or causing errors, while still validating that any \new\ credential selected is usable by the current actor.

src/applications/passphrase/view · high confidence

New daemon log and task table views

The daemon management interface now uses dedicated view classes to render daemon logs and tasks. PhabricatorDaemonLogListView displays a table of daemon logs with status indicators (Running, Dead, Shutting Down, Exited, Waiting, Unknown) using FontAwesome icons and tooltips, while PhabricatorDaemonTasksTableView presents a table of daemon tasks showing ID, class, owner, lease expiration, priority, failure count, and a link to view the task details.

src/applications/daemon/view · high confidence

New daemon log query with configurable status write-back

Added PhabricatorDaemonLogQuery to allow querying daemon logs by ID, status, class, and daemon ID, with support for excluding IDs via a new withoutIDs method. The query now tracks daemon unique IDs in logs and applies time-based status transitions (marking daemons as unknown or dead if heartbeats are missed), but status updates are written back to the database only when explicitly enabled via setAllowStatusWrites, preventing unintended writes by default.

src/applications/daemon/query · high confidence

New daemon management CLI workflows for debugging, launching, and monitoring

This change introduces a suite of new command-line workflows in the daemon management application to improve daemon lifecycle control and diagnostics. Users can now use \phd debug\ to run a specific daemon in the foreground with verbose diagnostic output, \phd launch\ to start custom or multiple instances of specific daemons, and \phd list\ to view all available daemon classes. The \phd status\ command has been updated to display daemon PIDs and commands directly from the process list, while \phd log\ allows querying daemon logs by ID with a configurable line limit. Additionally, \phd reload\ provides a way to gracefully restart daemon processes in-place, and the \phd stop\ and \phd restart\ commands now support a \--force\ flag to override instance checks and a \--graceful\ period for clean shutdowns. A new \phd lock log\ workflow enables enabling, disabling, and reviewing lock contention logs for debugging.

src/applications/daemon/management · high confidence

New daemon management scripts and launcher

Added \scripts/daemon/launch\_daemon.php\ to start daemons with a full Phabricator environment, utilizing \pcntl\_async\_signals\ when available or falling back to \declare(ticks = 1)\. Introduced \scripts/daemon/manage\_daemons.php\ to provide a CLI interface for managing daemons, automatically discovering management workflows via \PhutilClassMapQuery\. A symlink \phd-daemon\ was created to point to the launcher script.

scripts/daemon · high confidence

New data models for high-security tokens and administrative invites

This change introduces new data classes in the authentication layer to support enhanced security and user management features. PhabricatorAuthHighSecurityToken provides storage for high-security tokens, including a flag to track whether a token is unchallenged, supporting multi-factor authentication workflows. PhabricatorAuthInviteAction introduces a structured model for processing administrative email invites, handling validation, duplicate detection, and status tracking (such as verified, invited, or accepted states) to enable sending emails for email invites. PhabricatorAuthSessionInfo adds a data structure to represent session details, including session type, identity PHID, and partial status, laying the groundwork for more granular session management.

src/applications/auth/data · high confidence

New database schema inspection and comparison infrastructure

The system now includes a new schema inspection framework in the config application that allows comparing actual database structures against expected definitions. This introduces new schema classes (server, database, table, column, and key) and a query mechanism to detect mismatches in column types, character sets, collations, nullability, auto-increment settings, and index properties. It also supports identifying access denied errors and classifying tables by persistence type (data, cache, or index), enabling better validation and troubleshooting of database configurations.

src/applications/config/schema · high confidence

New edge types for commit relationships

This change introduces new edge types to explicitly model relationships between commits and other objects. Specifically, it adds \DiffusionCommitHasPackageEdgeType\ to link commits to packages, \DiffusionCommitHasRevisionEdgeType\ to associate commits with Differential revisions, \DiffusionCommitHasTaskEdgeType\ to link commits to Maniphest tasks, and \DiffusionCommitRevertsCommitEdgeType\ (along with its inverse \DiffusionCommitRevertedByCommitEdgeType\) to track which commits revert others. These new edges enable more structured querying and display of commit associations within the Diffusion application.

src/applications/diffusion/edge · high confidence

New edge types for dashboard panel usage and profile menu items

Added new edge types to track relationships between objects and dashboard panels, as well as profile menu items. Specifically, \PhabricatorObjectUsesDashboardPanelEdgeType\ and \PhabricatorDashboardPanelUsedByObjectEdgeType\ establish a bidirectional link (edge constants 71 and 72) to identify which dashboard panels are used by which objects and vice versa, enabling users to see where panels are utilized. Additionally, \PhabricatorProfileMenuItemAffectsObjectEdgeType\ (edge constant 70) defines the relationship for profile menu items affecting objects.

src/applications/search/edge · high confidence

New edit engines for configuring profile menu items

Users can now edit profile menu item configurations through a dedicated interface. This change introduces \PhabricatorProfileMenuEditEngine\ and \PhabricatorProfileMenuEditor\ in the search editor application, enabling the creation, modification, and reordering of menu items (including links, projects, and dashboards) with specific validation for properties like URIs and visibility.

src/applications/search/editor · high confidence

New edit engines for contact numbers, MFA providers, and auth messages

Administrators can now manage contact numbers, multi-factor authentication (MFA) providers, and authentication messages through dedicated edit engines. The new PhabricatorAuthContactNumberEditEngine allows editing user contact numbers, while PhabricatorAuthFactorProviderEditEngine enables configuring MFA provider names and statuses. Additionally, PhabricatorAuthMessageEditEngine provides a way to customize authentication-related messages. These changes introduce new transaction types and validation logic for these specific authentication components.

src/applications/auth/editor · high confidence

New email address utility for normalization and validation

A new utility class, PhabricatorMailUtil, has been added to handle email address processing. It provides methods to normalize addresses by stripping configured reply prefixes and standardizing casing, as well as to compare addresses for equality. The utility also introduces logic to identify reserved system addresses (such as 'admin', 'noreply', and void/placeholder addresses) and to verify if an address belongs to a user, which supports preventing inbound processing of invalid or shadowing addresses.

src/applications/metamta/util · high confidence

New email body parser with command and signature stripping

The system now includes a new email body parser (PhabricatorMetaMTAEmailBodyParser) that processes incoming email replies. This parser automatically detects and executes commands prefixed with '!' (such as !assign or !claim) found at the start or end of the message body. It also cleans the message content by stripping quoted reply text (including patterns from Outlook, GMail, and generic 'On \<date\>... wrote:' formats) and removing common email signatures from clients like Mailbox, HTC, and iPhone, ensuring that only the relevant user response is processed.

src/applications/metamta/parser · high confidence

New email commands for task assignment, claiming, status, and priority

Users can now manage Maniphest tasks via email using new commands: \!assign\ to assign a task to a specific user (or yourself if omitted), \!claim\ to assign the task to yourself, \!close\ to set the task to the default closed status, \!status\ to change the task status by keyword, and \!priority\ to change the task priority by keyword. These commands support disabled statuses and priorities, ignoring invalid inputs or disabled options.

src/applications/maniphest/command · high confidence

New extensible charting engine with stacked area support and mathematical functions

The charting system in the Fact application has been replaced with a new, extensible engine that supports stacked area charts and a modular function architecture. Users can now visualize data using stacked area charts, which group nearby points to prevent overlap and provide clearer visual summaries. The engine introduces a suite of new chart functions, including mathematical operations like \sin()\, \cos()\, \scale()\, and \shift()\, as well as data manipulation functions like \accumulate()\, \sum()\, \compose()\, \min()\, and \max()\. This change also adds a tabular view for chart data and ensures that chart function labels are provided explicitly rather than generated ad-hoc, improving the clarity of the visualized metrics.

src/applications/fact/chart · high confidence

New extensible transaction engine architecture with mail stamps and subtype support

This change introduces a new modular extension system for the transaction engine, allowing different components to hook into editing, mail generation, destruction, and fulltext indexing. Key additions include a mail engine extension that enriches notification emails with stamps (such as acting user, content source, and object details), an edit engine extension that enables changing object subtypes via bulk actions and comment forms, and a fulltext engine extension that indexes the first 1,000 comments per object to prevent performance issues with high-comment items. The system also includes a destruction engine extension to properly clean up associated transactions when objects are deleted.

src/applications/transactions/engineextension · high confidence

New feed management workflow to republish feed events

A new management workflow has been added that allows administrators to republish a specific feed event (identified by its story key) to all consumers. This is achieved by scheduling a FeedPublisherWorker task, ensuring the event is re-delivered to subscribers. The workflow extends a new base management class for feed operations.

src/applications/feed/management · high confidence

New feed story publisher for Differential revisions

A new publisher class has been added to handle the creation of feed stories for Differential revisions. This component determines which revisions trigger stories based on actions like creation, closure, or abandonment, and formats the story details including the object title, URI, description, and responsible users (reviewers and subscribers). It also defines the logic for identifying active and passive users associated with the revision.

src/applications/differential/doorkeeper · high confidence

New feed story publisher for Doorkeeper commit audits

A new \DiffusionDoorkeeperCommitFeedStoryPublisher\ class has been added to handle the generation of feed stories for Doorkeeper audit actions on commits. This component determines which users should be notified (active vs. passive) based on audit request statuses and ensures that feed stories correctly reflect the closure state of commits when they are accepted or closed, improving the visibility of audit outcomes in the application feed.

src/applications/diffusion/doorkeeper · high confidence

New feed transaction search and query infrastructure

This change introduces the core query and search engine classes for the activity feed, enabling users to browse and filter feed transactions. The new PhabricatorFeedTransactionQuery and PhabricatorFeedTransactionSearchEngine allow filtering transactions by author, object type, and date range, with results displayed in a table view. Additionally, the PhabricatorFeedQuery and PhabricatorFeedSearchEngine provide a higher-level 'Feed Stories' view that aggregates these transactions, supporting filters for users and projects, and date ranges. The transaction search engine also supports exporting results to CSV/Excel formats.

src/applications/feed/query · high confidence

New file management CLI workflows for integrity, migration, and maintenance

The \bin/files\ command-line interface now includes a suite of new management workflows to help administrators maintain file storage. You can verify, compute, or strip file integrity hashes with \bin/files integrity\, and safely print file contents to stdout with \bin/files cat\ (including a dangerous \--salvage\ mode to bypass integrity checks). Storage maintenance is supported by \bin/files compact\, which merges identical files to share storage, and \bin/files rebuild\, which updates MIME types and image dimensions. For storage infrastructure changes, \bin/files migrate\ moves files between engines (with options to copy data, filter by size, or import from local disk backups), \bin/files encode\ changes storage formats, and \bin/files cycle\ rotates encryption keys. Additional utilities include \bin/files engines\ to list available storage backends and \bin/files generate-key\ to create new encryption keys.

src/applications/files/management · high confidence

New file query and search infrastructure

This change introduces a new set of query classes for the Files application, including PhabricatorFileQuery, PhabricatorFileAttachmentQuery, PhabricatorFileChunkQuery, and PhabricatorFileSearchEngine. These classes provide a structured way to retrieve files, attachments, and chunks with support for policy-aware filtering, pagination, and search capabilities. The PhabricatorFileSearchEngine enables searching files by author, name, and creation date, while the new query classes support filtering by file properties such as visibility, transformation status, and storage engine. This infrastructure allows for more efficient and flexible file retrieval and search operations within the application.

src/applications/files/query · high confidence

New help documentation and keyboard shortcut views

The help application now includes dedicated controllers for displaying application-specific documentation and keyboard shortcuts. Users can access a help page for any application, which lists its available help menu items, and can view a comprehensive keyboard shortcut reference dialog that groups shortcuts by category (such as Page Shortcuts, Diff Navigation, and Global Shortcuts) with support for special key symbols.

src/applications/help/controller · high confidence

New hierarchical module configuration interface

A new controller for the Config application now provides a full-width, hierarchical layout for managing configuration modules. Users can navigate a sidebar list of all available modules, each identified by a puzzle-piece icon, and view the status and settings for the selected module within a two-column view.

src/applications/config/controller/module · high confidence

New image transformation infrastructure for saving image data

The Files application now includes a new \PhabricatorImageTransformer\ class that provides a structured way to save image resources to string data. This component supports saving images in PNG, GIF, and JPG formats, automatically falling back between formats if the preferred one is unavailable or fails. It also implements PNG compression (level 6) to balance file size and processing time, and ensures graceful handling when specific image extension functions are not available in the PHP environment.

src/applications/files · high confidence

New inbound mail webhooks for Mailgun, Postmark, and SendGrid

The MetaMTA application now supports receiving inbound email via webhooks from Mailgun, Postmark, and SendGrid. New controllers handle incoming payloads from these providers, verifying authenticity (via Mailgun signatures or Postmark IP whitelisting) and processing the email content, headers, and attachments into Phabricator's internal mail objects for further handling.

src/applications/metamta/controller · high confidence

New invoice management workflow for subscriptions

Added a new command-line workflow to manually invoice a subscription for a specific billing period. This tool allows administrators to specify the subscription, define the billing range (either explicitly via start/end times or automatically based on the next scheduled trigger), and optionally override the current time for testing. It includes safety checks to prevent double-billing and requires explicit confirmation unless the force flag is used, ultimately scheduling the billing task with the correct epoch parameters.

src/applications/phortune/management · high confidence

New lunar phase policy rule and policy rule framework updates

This change introduces a new 'Lunar Phase' policy rule, allowing access control based on the current moon phase (full, new, waxing, waning) via a select control in the policy editor. It also updates the base \PhabricatorPolicyRule\ class to support object-specific policies through the \getObjectPolicyKey()\ method and adds transaction hinting mechanisms to prevent users from locking themselves out during policy edits. The base rule class now extends \Phobject\ and includes methods for handling control types (text, select, tokenizer) and rule ordering.

src/applications/policy/rule · high confidence

New manage\_search script for search index management

A new \manage\_search.php\ script has been added to the \scripts/search\ directory, allowing users to manage the Phabricator search index via command-line workflows. The script dynamically discovers available management workflows by querying the class map for classes extending \PhabricatorSearchManagementWorkflow\ and integrates them into the argument parser.

scripts/search · high confidence

New modular configuration options for project icons, colors, and subtypes

Administrators can now customize project appearance and structure through new configuration options. The 'projects.icons' option allows defining and selecting default project icons, including special milestone icons. The 'projects.colors' option enables relabeling existing project colors. Additionally, the 'projects.subtypes' option allows defining project subtypes (such as 'Team'), and custom field definitions for projects are now configurable via 'projects.custom-field-definitions'.

src/applications/project/config · high confidence

New modular system engines for destruction, caching, and rate limiting

This change introduces a set of new, extensible engine classes in the system engine application to handle core infrastructure tasks more modularly. The DestructionEngine now supports a plugin-based architecture via DestructionEngineExtension, allowing specific object types to define custom destruction logic and post-destruction hooks. A new CacheEngine and its extensions provide a standardized way to discover linked objects and invalidate caches when data changes. Additionally, the SystemActionEngine implements a generic rate-limiting infrastructure that tracks action scores per actor to prevent abuse, while the UnlockEngine standardizes how object policies (view, edit, owner) are unlocked. These engines replace ad-hoc implementations with a unified, extensible framework for system-level operations.

src/applications/system/engine · high confidence

New panel management controllers for listing, editing, and archiving dashboard panels

This change introduces a set of new controllers in the dashboard panel subdirectory to handle panel lifecycle operations. The Panel List Controller provides a searchable interface for browsing and creating panels. The Panel Edit Controller manages the creation and modification of panels, including a dialog to select panel types and support for editing within dashboard or container contexts. The Panel Archive Controller allows users to archive or reactivate panels via a confirmation dialog. The Panel View Controller displays panel details, including a live preview, usage information (showing which dashboards or panels use it), and a transaction timeline. The Panel Render Controller handles the rendering of individual panels, supporting both standalone views and AJAX-based rendering for dashboards. The Panel Tabs Controller specifically manages the addition, removal, reordering, and renaming of tabs within tab-type panels, ensuring proper redirection back to the originating dashboard or panel context after edits.

src/applications/dashboard/controller/panel · high confidence

New parser for Maniphest custom status fields

A new parser class, ManiphestCustomFieldStatusParser, has been added to handle status-related keywords in Maniphest custom fields. It recognizes prefixes like 'Fixes' and 'Reopens', infixes such as 'task' or 'issue', and suffixes for status transitions (e.g., 'as wontfix'). The parser also supports parsing multiple task monograms (e.g., 'T123, T456, and T789') within a single string. Tests confirm it correctly identifies these patterns and extracts the associated task IDs and status modifiers.

src/applications/maniphest/field/parser · high confidence

New policy codex system for custom policy descriptions

This change introduces a new policy codex system that allows objects to provide custom strings, descriptions, and explanations for the policy system. The new \PhabricatorPolicyCodex\ class and \PhabricatorPolicyCodexInterface\ enable objects to render custom policy information, while \PhabricatorPolicyCodexRuleDescription\ provides a structure for defining policy rules with descriptions, capabilities, and active status. This system helps users understand complex policies by providing more detailed and contextual information about policy rules.

src/applications/policy/codex · high confidence

New policy explanation UI components

This change introduces three new view classes to improve how policy rules and references are displayed to users. PHUIPolicySectionView provides a structured container for policy sections, supporting headers, icons, documentation links, and inline rule lists. PhabricatorPolicyRef handles the rendering of policy names with explicit pathways for capability links and transaction links, including type hints for project or masked policies. PhabricatorPolicyRulesView renders custom policy rules in a readable, ordered list with allow/deny indicators and handle rendering, clarifying how access decisions are made.

src/applications/policy/view · high confidence

New policy rules for LegalPad signatures, administrators, and users

This change introduces three new policy rule classes that define access control logic for specific user groups. In the LegalPad application, a new rule allows access based on whether a user has signed a specific LegalPad document. In the People application, new rules enable access control for administrators (checking the admin flag) and for specific users (checking if the viewer's PHID is in the allowed list). These rules provide the foundational policy logic for restricting access to LegalPad documents and People-related objects based on signature status, administrative role, or explicit user inclusion.

src/applications/legalpad/policyrule, src/applications/people/policyrule · high confidence

New profile menu items for Badges, Commits, Revisions, and Tasks

This change introduces new profile menu items that allow users to view specific activity sections on user profiles, including Badges, Commits, Revisions, and Tasks. Each item is implemented as a distinct menu component (e.g., PhabricatorPeopleBadgesProfileMenuItem) that links to dedicated pages (such as /people/badges/{id}/) and displays relevant icons. The User Details and Manage User items are also present, with the latter being non-hideable. The User Picture item displays the user's profile image. These changes enhance the profile navigation by providing direct access to key user contributions and management options.

src/applications/people/menuitem · high confidence

New profile menu items for project side navigation

This change introduces a set of new profile menu item classes for the project side navigation, including Project Details, Manage, Members, Picture, Points, Reports, Subprojects, and Workboard. These items provide users with direct access to key project sections and features, such as managing project settings, viewing members, and accessing the workboard. The Points item specifically displays a progress bar for milestones, while the Reports item is currently a prototype. These menu items are designed to enhance the user experience by organizing project-related actions and information in a structured and accessible manner.

src/applications/project/menuitem · high confidence

New project and workboard card views with enhanced member and watcher management

This change introduces new view classes for the project application: PhabricatorProjectCardView and PhabricatorProjectListView provide updated UI for displaying individual projects and lists, including support for profile images, display icons, and subtype tags. PhabricatorProjectMemberListView and PhabricatorProjectWatcherListView replace or enhance the previous member/watcher lists, adding clearer UI feedback for disabled users, membership notes, and distinct remove actions for members versus watchers. Additionally, ProjectBoardTaskCard introduces a new workboard card view that supports cover images, task points, subtype tags, and visual indicators for editability and archived status, improving the workboard experience.

src/applications/project/view · high confidence

New project search, UI, and indexing extensions

This change introduces a suite of new engine extensions for the Project application that enhance search capabilities, user interface, and data indexing. For search, it adds support for filtering objects by project tags, exposes project ancestors, members, and watchers via search attachments, and indexes project milestones to accurately reflect membership. For the user interface, it adds a new hovercard for projects, integrates project tags into the 'Curtain' view (showing workboard column locations for tasks), and enables bulk editing of project tags and subscribers in the Maniphest editor. Additionally, it implements a materialized index for project memberships to improve query performance and adds a quick-search datasource for projects.

src/applications/project/engineextension · high confidence

New query and search engine classes for OAuth Server entities

This change introduces dedicated query and search engine classes for OAuth Server entities, specifically \PhabricatorOAuthClientAuthorization\, \PhabricatorOAuthServerClient\, and \PhabricatorOAuthServerTransaction\. The new \PhabricatorOAuthServerClientQuery\ and \PhabricatorOAuthClientAuthorizationQuery\ classes extend \PhabricatorCursorPagedPolicyAwareQuery\ to provide filtered access to OAuth clients and authorizations based on PHIDs, user IDs, and client IDs, while enforcing policy checks. A new \PhabricatorOAuthServerClientSearchEngine\ enables searching for OAuth clients by creator and displays them in a list view, supporting built-in queries for 'All Applications' and 'Created' by the current user. Additionally, \PhabricatorOAuthServerTransactionQuery\ is added to handle transaction queries for OAuth server objects, and \PhabricatorOAuthServerSchemaSpec\ defines edge schemata for the OAuth server client.

src/applications/oauthserver/query · high confidence

New query and search engine classes for the Auth application

This change introduces a comprehensive set of new query and search engine classes within the \src/applications/auth/query\ directory, enabling structured database access and search capabilities for various authentication-related entities. Specifically, it adds queries for auth challenges, contact numbers, MFA factor configurations and providers, email invites, auth messages, password hashes, provider configurations, SSH keys, sessions, temporary tokens, and external account identifiers. These classes provide standardized filtering (by ID, PHID, status, and other attributes) and policy-aware loading, supporting features like customizable onboarding flows, SMS/contact number management, configurable MFA providers, and external account linking.

src/applications/auth/query · high confidence

New query and search engines for project workboard columns, triggers, and positions

This change introduces dedicated query classes and search engines for workboard-related project entities, enabling users to search and filter workboard columns, triggers, and column positions. The new PhabricatorProjectColumnQuery and PhabricatorProjectColumnSearchEngine allow searching columns by project, status, and proxy, while PhabricatorProjectTriggerQuery and PhabricatorProjectTriggerSearchEngine enable filtering triggers by activity status and viewing their usage counts. Additionally, PhabricatorProjectColumnPositionQuery provides the ability to query column positions by board, object, or column. These additions support the broader workboard feature set by providing the backend query infrastructure for these specific sub-resources.

src/applications/project/query · high confidence

New query and search infrastructure for Calendar events, imports, and exports

This change introduces a comprehensive set of new query classes and search engines within the Calendar application to modernize how data is retrieved and filtered. It adds dedicated queries for calendar events, invitees, transactions, imports, import logs, and exports, all extending the standard cursor-paged policy-aware query base to ensure consistent access control and pagination. Corresponding search engines are provided for events, imports, and export logs, enabling users to filter results by criteria such as host, invitees, date ranges, and import sources. Additionally, new typeahead datasources for invitees allow users to search for users, projects, and the current viewer when managing event invitations.

src/applications/calendar/query · high confidence

New query and search infrastructure for EditEngine configurations

This change introduces a new set of query classes and search engines within the transactions application to manage EditEngine configurations. Users can now search for and filter edit forms by specific criteria, including whether they are designated as 'Create' or 'Edit' forms, whether they are disabled, and their subtype. The new \PhabricatorEditEngineConfigurationSearchEngine\ provides a dedicated search interface for these forms, allowing administrators and users to easily locate and manage form configurations based on their purpose and status.

src/applications/transactions/query · high confidence

New query class for external Doorkeeper objects

A new \DoorkeeperExternalObjectQuery\ class has been added to the Doorkeeper application's query layer. This class allows users to retrieve external objects by filtering on PHIDs or object keys, extending the existing cursor-paged policy-aware query infrastructure to support these specific lookups within the Doorkeeper context.

src/applications/doorkeeper/query · high confidence

New query class for retrieving fact datapoints

A new \PhabricatorFactDatapointQuery\ class has been added to the fact application, enabling users to query and examine the specific datapoints generated by facts. This class supports filtering by fact keys and object PHIDs, allows setting a result limit, and can optionally return raw vectors for the retrieved data, providing a dedicated mechanism for inspecting fact data.

src/applications/fact/query · high confidence

New query classes for Diffusion repository data and events

This change introduces a suite of new query classes in the Diffusion repository application to support querying repository metadata, identities, and various event logs. Specifically, it adds PhabricatorRepositoryQuery for filtering repositories by status, type, and hosted location; PhabricatorRepositoryIdentityQuery for managing user identity associations; and dedicated query engines for push logs, pull events, and synchronization events. These additions enable more granular searching and filtering of repository-related data, including the ability to filter push logs by blocking Herald rules and to query repository identities by assigned or effective user PHIDs.

src/applications/repository/query · high confidence

New remarkup rules for embedding files and external images

This change introduces two new remarkup rules to the file application: \PhabricatorEmbedFileRemarkupRule\ and \PhabricatorImageRemarkupRule\. The file embedding rule allows users to embed files (images, audio, video) directly in comments and posts, with logic to distinguish between files intended for attachment versus those merely referenced in quoted text. It supports various layouts and sizes, including a new 'wide' option for documents. The external image rule enables embedding images from external URLs using \{img ...}\ syntax, featuring a caching mechanism to serve direct image tags for previously fetched images and falling back to a proxy for new ones. These changes enhance the ability to display rich media content within the platform's markup.

src/applications/files/markup · high confidence

New search and query infrastructure for People and Account Activity Logs

This change introduces a modernized search and query layer for the People application, replacing older query patterns with a unified ApplicationSearch engine. For user discovery, the new PhabricatorPeopleSearchEngine and PhabricatorPeopleQuery provide advanced filtering capabilities, including search by username, name substring, administrative status, disabled state, bot/mailing-list classification, and account creation date; administrators can also filter by Multi-Factor Authentication enrollment. For auditing, a new PhabricatorPeopleLogSearchEngine and PhabricatorPeopleLogQuery allow users and administrators to search account activity logs by user, actor, action type, IP address, session, and date range, with non-administrators automatically restricted to viewing only logs related to their own account. The implementation also includes dedicated queries for user emails and transactions, ensuring consistent policy enforcement and efficient data loading across these new search interfaces.

src/applications/people/query · high confidence

New storage layer for user profiles, external accounts, and activity logs

This change introduces a new set of storage classes in the People application to support modernized user management features. It adds \PhabricatorExternalAccount\ and \PhabricatorExternalAccountIdentifier\ to manage linked third-party accounts and their identifiers, \PhabricatorUserProfile\ to store user display details like titles and icons, and \PhabricatorUserLog\ to record and display user activity history. Additionally, it includes \PhabricatorUserCache\ for performance optimization, \PhabricatorRegistrationProfile\ to configure registration flows, and updated \PhabricatorUser\ and \PhabricatorUserEmail\ classes with new validation and policy interfaces. These components provide the underlying data structures and caching mechanisms required for the new registration workflow, external account linking, and user activity logging capabilities.

src/applications/people/storage · high confidence

New storage schema for authentication challenges, contact numbers, and MFA providers

This change introduces a new set of database-backed storage classes in the Auth application to support multi-factor authentication (MFA) and contact management. Specifically, it adds \PhabricatorAuthChallenge\ to track and validate MFA challenge responses, \PhabricatorAuthContactNumber\ to store and manage user phone numbers with primary/active status, and \PhabricatorAuthFactorProvider\ along with \PhabricatorAuthFactorConfig\ to define and configure MFA factor types (like TOTP or SMS) and their per-user settings. These classes establish the underlying data structures required for the new MFA workflow, including challenge binding, session tracking, and contact number verification.

src/applications/auth/storage · high confidence

New storage schema for named queries, saved queries, and profile menu configuration

This change introduces new database tables and DAO classes to support advanced search and profile customization features. Specifically, it adds \PhabricatorNamedQuery\ and \PhabricatorSavedQuery\ to store named and saved search queries with distinct scopes (global vs. personal) and metadata like engine class names and parameters. It also introduces \PhabricatorProfileMenuItemConfiguration\ and its associated transaction class to manage the visibility, order, and properties of items in profile menus, allowing users to customize their interface. Additionally, \PhabricatorSearchIndexVersion\ is added to track indexer versions and epochs for indexed objects, and a stopwords table schema is defined for future fulltext index optimization.

src/applications/search/storage · high confidence

New system controllers for debugging, status, and read-only mode explanations

This change introduces several new controllers in the system application to improve operational visibility and user experience during maintenance or failures. A new debug controller allows administrators to run arbitrary diagnostic scripts via /debug/ by placing them in /support/debug.php. A status controller provides a simple 'ALIVE' endpoint for health checks. A read-only mode controller now displays specific, user-friendly explanations for why the system is in read-only mode (e.g., administrative configuration, missing master database, or unreachable master), rather than failing silently or with generic errors. Additionally, a favicon controller handles hard-coded /favicon.ico requests to prevent 404s, and a generic object redirection controller allows resolving PHID-based names to their actual URIs.

src/applications/system/controller · high confidence

New tables for viewing Almanac bindings and interfaces

Users can now view detailed lists of Almanac bindings and network interfaces through new table views. The binding table displays service, device, and network associations along with active or disabled status icons, while the interface table lists address and port details with edit and delete actions (disabled when editing is not permitted).

src/applications/almanac/view · high confidence

New transaction infrastructure interfaces for subscriptions, mentions, and timelines

This change introduces four new interfaces in the transactions layer to support advanced object interactions. PhabricatorApplicationTransactionInterface allows objects to define how transaction editors and templates are created, enabling features like subscription CCs and build notifications. PhabricatorInlineCommentInterface enables inline comment storage objects to generate their own runtime instances. PhabricatorMentionableInterface provides the foundation for automatically creating 'mentioned' edges when users are referenced. Finally, PhabricatorTimelineInterface allows objects to provide their own timeline engine, facilitating more flexible timeline rendering.

src/applications/transactions/interface · high confidence

New typeahead datasources for Diffusion repositories, refs, symbols, and auditors

This change introduces a suite of new typeahead datasources within the Diffusion application to improve search and navigation. Users can now search for repositories, branches/tags/refs, and code symbols directly via typeahead, with repositories displaying monograms, names, and version control system types. A new 'tagged(...)' function allows filtering repositories by project. Additionally, auditing workflows are enhanced with datasources for selecting auditors (users, projects, or packages) and assignees, including a specific 'unassigned()' function to explicitly find unassigned results.

src/applications/diffusion/typeahead · high confidence

New typeahead datasources for Harbormaster build configuration

Users can now use typeahead search when configuring Harbormaster build plans. New datasources allow selecting build plans, build dependencies (steps), build initiators (users, applications, or Herald rules), and build statuses directly from the configuration UI, replacing manual entry or less structured selection methods.

src/applications/harbormaster/typeahead · high confidence

New typeahead datasources for application emails and mailable entities

Users can now search for application email addresses and a broader set of mailable entities (users, projects, packages, mailing lists, and functions) via new typeahead datasources. The \PhabricatorMetaMTAApplicationEmailDatasource\ enables searching for application-specific email addresses, while \PhabricatorMetaMTAMailableDatasource\ and \PhabricatorMetaMTAMailableFunctionDatasource\ provide composite search capabilities for subscribers, integrating existing datasources for people, projects, owners packages, and viewers to support more flexible recipient selection in mailing contexts.

src/applications/metamta/typeahead · high confidence

New user hovercards and activity log views

Users can now see detailed hovercards for other people, which display profile images, account status tags (such as 'Disabled', 'Unapproved', or 'Email Not Verified' with specific colors), creation dates, and calendar availability if the Calendar application is installed. Additionally, users can review their own account activity logs through a new table view that lists actions, actors, associated users, IP addresses, session IDs, and timestamps, with links to filter by IP address.

src/applications/people/view · high confidence

New user preferences query and search infrastructure

This change introduces the backend query and search engine classes for user preferences, enabling administrators to configure and manage global default settings. The new PhabricatorUserPreferencesQuery class supports filtering by IDs, PHIDs, and user objects, and includes logic to attach global default settings to user preferences when needed. The PhabricatorUserPreferencesSearchEngine provides a search interface for browsing and editing these settings, while the transaction query class supports tracking changes to user preferences.

src/applications/settings/query · high confidence

New user profile custom fields for title, blurb, and icon

Users can now edit and view their profile title, blurb, and icon through a new custom field system. The 'Title' and 'Blurb' fields are editable via the profile editor and appear in user property views, while the 'Icon' field allows users to select an icon from a predefined set. These fields are integrated with the application transaction system, meaning changes are tracked and can be managed via API. Additionally, the 'Availability' field is now conditionally displayed only if the Calendar application is installed, and it is hidden for disabled users.

src/applications/people/customfield · high confidence

New utility scripts for adding image macros and emitting test events

Added two new command-line utilities in scripts/util: add\_macro.php, which allows administrators to programmatically import images as image macros (with support for specifying a custom name and enabling CDN delivery), and emit\_test\_event.php, which helps developers test event listeners by installing specified listeners and dispatching a test event.

scripts/util · high confidence

New workboard column ordering and grouping options

Workboards now support additional ways to organize tasks. Users can group columns by Owner, Author, Status, or Priority, with headers that allow drag-and-drop updates to those properties. New sorting options include Points, Created Date, and Title, providing more flexibility in how tasks are displayed on the board.

src/applications/project/order · high confidence

New workboard management and configuration controllers

This change introduces a suite of new controllers in the project application to support the redesigned workboard system. Users can now configure workboard background colors, set default filters and sort orders, disable or enable workboards, and import column structures from other projects. It also adds dedicated interfaces for managing columns, including creating, editing, reordering, hiding, and bulk-editing or bulk-moving tasks within columns.

src/applications/project/controller · high confidence

Nuance GitHub import cursors split into repository and issues event importers

The Nuance application now supports importing raw GitHub event data through dedicated import cursors. The previous single import cursor has been split into two distinct types: one for repository events and another for issues events. This allows Nuance sources to provide specific import cursors for different GitHub API endpoints, enabling more granular and efficient polling of GitHub activity data into the system.

src/applications/nuance/cursor · high confidence

Owners application adds hovercard and search path attachment

The Owners application now provides richer context and searchability for owner packages. Users can view a hovercard on owner package objects that displays the package ID, name, dominion, auto-review status, archived status, owners, and a truncated description. Additionally, search queries can now filter or display the specific file paths associated with each owner package via a new 'Included Paths' search attachment.

src/applications/owners/engineextension · high confidence

Owners application storage schema and data models

This change introduces the core database schema and data access objects for the Owners application. It adds the PhabricatorOwnersPackage model, which supports package status (active/archived), auto-review settings (subscribe, review, block), dominion rules (strong/weak), and authority modes. The PhabricatorOwnersOwner model manages package membership, supporting both individual users and project members. Path ownership is handled by PhabricatorOwnersPath, which includes support for path indexing, display paths, and exclusion flags. Custom field support is added via dedicated storage and index classes. The schema also includes ngram indexing for package name search and modular transaction support for package edits.

src/applications/owners/storage · high confidence

Owners packages can now be archived and activated

Users can now archive Owners packages to stop them from triggering audits or appearing in active views, and reactivate them later. This is implemented via a new PhabricatorOwnersArchiveController that handles the archive/activate toggle through a confirmation dialog and applies a status transaction to the package.

src/applications/owners/controller · high confidence

Owners packages now have dedicated PHID types with monogram support

Owners packages are now represented by a specific PHID type (OPKG) that enables monogram-based identification (e.g., 'O123') in command-line interfaces and user interfaces. This change introduces a dedicated icon (shopping bag) for packages and supports mail stamps, allowing packages to be mailable and subscribable. Users can now reference owners packages using their monogram in fields like 'Reviewers', improving usability and consistency with other Phabricator objects.

src/applications/owners/phid · high confidence

Owners typeahead now supports package monogram search and owner-based filtering

The Owners application typeahead now allows users to find packages by entering their monogram (e.g., 'O42') or by using the 'packages(...)' function to filter results by a specific user or project owner. Additionally, package names are now searchable using ngram matching, and archived packages are clearly annotated in the search results.

src/applications/owners/typeahead · high confidence

Paste application now supports email integration and archive access

Users can now create pastes by sending emails to specific addresses, as the Paste application has enabled email integration. Additionally, a new archive endpoint is available for pastes, allowing users to access a bundled version of paste content. The application also exposes default view and edit policies for newly created pastes, giving administrators more control over initial access permissions.

src/applications/paste/application · high confidence

Paste search now supports filtering by language, date range, and status

Users can now filter Paste search results by programming language, creation date range, and active/archived status. The new PhabricatorPasteSearchEngine exposes these filters in the search UI, allowing you to narrow down pastes by author, language, or time period, with built-in queries for active, all, and authored pastes.

src/applications/paste/query · high confidence

Phame blog and post entities now have dedicated PHID types

Phame Blog and Phame Post objects are now represented by their own PHID type classes (PhabricatorPhameBlogPHIDType and PhabricatorPhamePostPHIDType). This enables the system to correctly resolve handles, query objects by PHID, and associate these entities with the Phabricator Phame application, laying the groundwork for features like full-text search and unified object handling.

src/applications/phame/phid · high confidence

Phrequent time tracking now supports filtering, sorting, and real-time status in search results

Users can now view and manage Phrequent time entries through a dedicated search interface that allows filtering by user, tracking status (ended vs. active), and sorting by start or end date. The list view displays current time spent on objects, shows when tracking ended, and provides a direct action to stop tracking for active sessions. This change introduces the PhrequentSearchEngine and PhrequentUserTimeQuery classes to handle these queries, including logic to account for preempting events where a new tracking session overrides an existing one for the same user and object.

src/applications/phrequent/query · high confidence

Phriction documents now appear in typeahead autocomplete

Users can now find and insert links to Phriction documents directly while editing Remarkup by typing "\[\[ ". A new PhrictionDocumentDatasource queries active documents via Ferret search, displaying their titles in the typeahead menu and automatically inserting the correct wiki link syntax (e.g., "\[\[ slug \]\]") when a result is selected.

src/applications/phriction/typeahead · high confidence

Projects application is modularized with new default policies and workboard management

The Projects application is now a distinct, pinned module with its own routing and configuration. This change introduces default view, edit, and join policies for newly created projects, allowing administrators to set baseline access controls. It also adds comprehensive workboard management capabilities, including the ability to disable boards, configure background colors, manage columns (hide/show, edit, bulk edit/move), and attach/remove triggers. New routes support project locking, member/watcher management, reports, and subproject/milestone views, reflecting a structural revamp of how projects are created, edited, and managed.

src/applications/project/application · high confidence

Public XHPAST view interface with iframe and frameset navigation

The XHPAST application now exposes a public-facing view interface, allowing users to access parsed AST results without authentication. This change introduces a new controller hierarchy in src/applications/phpast/controller that structures the view into an iframe-based layout: a main frame controller embeds a frameset, which splits the display into three panels for input, tree structure, and token stream. The controllers handle loading the parse tree by ID, rendering syntax errors gracefully, and displaying token streams and tree nodes with node IDs in tooltips. The view run controller remains the entry point for submitting source code, but the resulting view is now accessible via public URLs (/xhpast/view/{id}/).

src/applications/phpast/controller · high confidence

Rebuilt Conpherence with durable column and room-based architecture

The Conpherence chat application has been rebuilt to support a new 'durable column' interface that displays the user's recent conversations in a persistent sidebar, replacing the previous single-thread view. The application now distinguishes between 'rooms' (group conversations) and 'threads' (individual messages), introducing dedicated controllers for room management, editing, and picture uploads. Users can now search across all rooms, manage per-room notification and sound preferences, and participate in public rooms. The update also introduces draft support for messages, real-time AJAX updates for the conversation list, and a new notification panel that aggregates unread room activity.

src/applications/conpherence/controller · high confidence

Register Phriction as a top-level application

Phriction is now registered as a distinct application within the system, providing its own navigation entry, icon, and help documentation. This change establishes the application's base URI (/w/), defines its routing structure for document management (listing, editing, publishing, moving, and previewing), and configures it to appear pinned by default in the user interface.

src/applications/phriction/application · high confidence

Render linked JIRA issues with a Doorkeeper tag

Doorkeeper now renders linked external objects (such as JIRA issues) as clickable tags in the UI. This change introduces a new DoorkeeperTagView component that generates a PHUITagView linked to the external object's URI, allowing users to navigate directly to the associated issue from the Doorkeeper interface.

src/applications/doorkeeper/view · high confidence

Settings panels are modularized and converted to EditEngine

The Settings UI has been restructured into distinct, modular panels (e.g., Activity Logs, Contact Numbers, Date and Time, Email Preferences, Multi-Factor Auth, Password, SSH Keys, Sessions) that are now grouped into logical categories like Authentication, Applications, and Logs. Many preference panels (Conpherence, Date and Time, Developer, Diff, Display, Email Delivery, Email Format, External Editor, Language, Search) have been converted to use the EditEngine framework, providing a consistent interface for managing user settings. This change also introduces new capabilities such as managing contact numbers for SMS, viewing account activity logs, and enhanced multi-factor authentication enrollment and management.

src/applications/settings/panel · high confidence

Structured import logging for calendar events

The calendar import feature now provides detailed, structured logs for import operations. This change introduces a new logging framework in the importlog application that categorizes events such as successful imports, updates, deletions, duplicates, and various errors (e.g., ICS parse errors, out-of-range dates, unsupported frequencies). Users can now see specific reasons why certain events were ignored or deleted, and receive clear feedback on import status, including when large files are queued for background processing.

src/applications/calendar/importlog · high confidence

Subscriptions now appear in search, edit forms, and the curtain UI

Subscribers are now integrated into the core object engine. You can filter objects by subscriber in search queries, manage subscribers directly through the EditEngine (supporting add, set, and remove actions), and view the subscriber list in the new Curtain panel, which highlights your own subscription and indicates when you lack permission to view certain subscribers. Additionally, subscriber information is included in full-text indexing and mail stamps, and search results now display subscriber counts and your subscription status.

src/applications/subscriptions/engineextension · high confidence

Support Herald rules for Phriction documents

Users can now create Herald rules that react to Phriction wiki documents being created or updated. This change introduces a new Herald adapter for Phriction documents and adds specific fields to check document properties such as the author, title, path, content, and whether the document has been published or changed. This enables automated notifications and actions based on wiki document activity.

src/applications/phriction/herald · high confidence

Support for Diviner symbol references in markup

Users can now use the @{symbol} syntax in text and HTML email bodies to create links to Diviner documentation. This new rule parses references like @{name}, @{type : name}, or @{name \| title} and converts them into clickable links (or plain text links in text mode) that point to the appropriate documentation page, handling invalid references gracefully.

src/applications/diviner/markup · high confidence

Support for HTTP feed hooks via new worker

Users can now configure arbitrary HTTP endpoints to receive feed story notifications by adding URIs to the \feed.http-hooks\ environment configuration. When a feed story is published, the system queues tasks to POST the story data (including \storyID\, \storyType\, \storyData\, \storyAuthorPHID\, \storyText\, and \epoch\) to each configured URI. The worker validates that the target URI is in the allowed list and permanently fails if it is not. Additionally, a \phabricator.silent\ configuration option is available to suppress all outbound feed events, including these HTTP hooks.

src/applications/feed/worker · high confidence

Support for custom UI configuration types

Administrators can now customize the application's user interface through new configuration options. This includes uploading a custom logo image and setting a custom wordmark text via the PhabricatorCustomLogoConfigType, as well as defining custom footer items (with names and optional links) via PhabricatorCustomUIFooterConfigType. The system also introduces a base framework for custom config types, including JSON-based options with validation (such as regex pattern validation) and extensible option types, allowing for more flexible and user-friendly configuration of UI elements.

src/applications/config/custom · high confidence

Support for displaying large subscription lists in dialogs and transaction strings

Users can now view extensive lists of subscribers or transaction participants without cluttering the main interface. The system introduces a dialog builder that renders these lists in a modal window, including profile pictures and hovercards for better context. Additionally, transaction and property views now intelligently summarize long lists by showing the first few subscribers followed by a link (e.g., "and X others") to view the complete list, improving readability when many users are involved.

src/applications/subscriptions/view · high confidence

Support for embedding Pholio mocks in Remarkup

Users can now embed Pholio mock collections directly into text using the \M123/456\ syntax. This new remarkup rule allows linking to specific images within a mock set and supports an \image\ option to display a selected subset of images. The embed renders using the PHUIPinboard UI, providing a visual preview of the mock content within the rendered text.

src/applications/pholio/remarkup · high confidence

Support for emoji, icons, and image macros in Remarkup

Users can now use inline emoji syntax (e.g., :emoji:) in text and HTML emails, render icons with optional spinning and color via the {icon} macro, and embed image macros (including memes) directly in comments and descriptions. These changes enhance the expressiveness of user-generated content by allowing richer visual elements without leaving the markup editor.

src/applications/macro/markup · high confidence

Support for executing commands on Drydock working copies

Harbormaster can now run external commands on Drydock working copies. This is enabled by the new HarbormasterExecFuture class, which wraps an ExecFuture to capture and stream standard output and error logs directly into the Harbormaster build log, allowing users to see command execution output in real-time during builds.

src/applications/harbormaster/future · high confidence

Support for funding initiatives via Phortune cart and product integration

Users can now back Fund initiatives through the Phortune payment system. This change introduces specific cart and product implementations (FundBackerCart and FundBackerProduct) that allow users to select an initiative, complete a purchase, and have the transaction recorded as a backer entry on the initiative. It also handles refunds by creating appropriate refund transactions on the initiative when a purchase is reversed.

src/applications/fund/phortune · high confidence

Support for global drag-and-drop file uploads

Users can now drag and drop files directly onto any page to initiate an upload, rather than relying solely on traditional file picker dialogs. This new global upload target view handles the drag-and-drop interface, automatically hiding the controls for non-logged-in users and applying a restrictive default view policy to uploaded files for security. The feature integrates with the existing file storage engine to support chunked uploads for large files.

src/applications/files/view · high confidence

Support for gzip-compressed request bodies

The request stream handler now detects and automatically decompresses HTTP request bodies encoded with gzip. When a request includes a Content-Encoding header indicating gzip, the system applies a zlib inflate filter to the input stream, allowing the application to read the original uncompressed data. A static utility is also provided to check if the server environment supports this capability.

src/aphront/requeststream · high confidence

Support for landing revisions on hosted Git and Mercurial repositories

Users can now land Differential revisions on hosted Git and Mercurial repositories. This change introduces a new utility class that creates and cleans dedicated workspaces for these repository types, enabling the landing process to function correctly in hosted environments where it previously did not.

src/applications/differential · high confidence

Support for modular application install, uninstall, and policy change transactions

Users can now track application lifecycle and configuration changes through a new modular transaction system. This introduces specific transaction types for installing and uninstalling applications, which update the 'phabricator.uninstalled-applications' configuration and provide clear feed updates (e.g., 'User X installed Y'). Additionally, a new 'application.policy' transaction type allows authorized users to change access policies for application capabilities, with validation ensuring that users can only set policies they are permitted to view or edit, and handling the storage of these policy changes in the application settings.

src/applications/meta/xactions · high confidence

Support for project hashtags in Remarkup

Users can now reference projects using hashtags (e.g., \#project-name) within Remarkup text. This new rule parses these hashtags, matches them against project monograms (including those with internal periods but excluding terminal punctuation to avoid false positives), and renders them as interactive tags with hovercards in rich text mode, or as plain text in text mode.

src/applications/project/remarkup · high confidence

Support for user availability, profile icons, and external account identifiers

Users can now set their availability status (Available, Busy, or Away) which is reflected in user handles and tokenizers, replacing the previous generic status model. User profiles now support custom icons, with a default 'fa-user' icon used in tokenizers, and disabled users are visually distinguished with grey dots. Additionally, the system now supports external account identifiers and mailing list users, with specific PHID types added to handle these new object types in queries and handles.

src/applications/people/phid · high confidence

User-configurable Maniphest statuses, priorities, and subtypes

Administrators can now customize Maniphest task statuses, priorities, and subtypes via the configuration options page. This change introduces new config types (\maniphest.statuses\, \maniphest.priorities\, \maniphest.subtypes\, and \maniphest.points\) that allow admins to edit, add, or remove available options, control locking behaviors (such as preventing comments or edits on specific statuses), and define default values. The configuration supports detailed specifications for each item, including names, colors, icons, and mail-command prefixes, replacing the previous hardcoded defaults with a flexible, user-defined structure.

src/applications/maniphest/config · high confidence

Users can now select from a set of profile icons

The People application now supports user profile icons. A new icon set has been added, allowing users to choose from a variety of icons such as User, Engineering, Operations, Design, and others to represent their profile. This change introduces the backend logic for defining and retrieving these icon specifications.

src/applications/people/icon · high confidence

XHProf sample search and drag-and-drop upload

Users can now search for XHProf samples using the global application search interface, which lists samples with details like execution time, controller, host, and sampling status. Additionally, the XHProf search results page now supports drag-and-drop functionality, allowing users to import .xhprof profile files directly by dropping them onto the list.

src/applications/xhprof/query · high confidence

API

Restructure Maniphest Conduit API with new methods and deprecations

The Maniphest Conduit API has been reorganized into a new class hierarchy, introducing \maniphest.edit\ as the primary method for creating and updating tasks while marking the legacy \maniphest.createtask\, \maniphest.update\, \maniphest.info\, and \maniphest.query\ methods as 'Frozen' (deprecated). A new \maniphest.search\ endpoint is now available for task queries, replacing the older query methods. Additionally, \maniphest.gettasktransactions\ now includes the \transactionPHID\ in its output, and \maniphest.priority.search\ has been added to retrieve available task priority options.

src/applications/maniphest/conduit · high confidence

Architecture

Centralize transaction type and color constants

The application now defines core transaction types (such as comment, subscriber, policy, edge, custom field, inline state, space, create, columns, subtype, history, MFA, and file) and associated UI colors in a single central class. This provides a unified registry for transaction identifiers and visual styling, ensuring consistency across the system.

src/applications/transactions/constants · high confidence

Introduces modular engine architecture for project workboards and profile menus

This change refactors the project application by introducing dedicated engine classes to handle specific concerns, moving away from monolithic logic. The new PhabricatorBoardLayoutEngine manages board and column positioning, while PhabricatorBoardRenderingEngine handles the generation of card HTML and cover images. PhabricatorBoardResponseEngine coordinates the layout and data updates for board interactions. Additionally, PhabricatorProjectEditEngine standardizes project creation and editing via the EditEngine framework, and PhabricatorProjectProfileMenuEngine defines the structure of the project profile menu items. These engines collectively provide a more modular foundation for workboard features and project management UI.

src/applications/project/engine · high confidence

Modularize EditEngine and Core transaction types

This change introduces a new inheritance hierarchy for transaction types to support modularization. It adds abstract base classes \PhabricatorCoreTransactionType\ and \PhabricatorEditEngineTransactionType\ that extend \PhabricatorModularTransactionType\. Corresponding concrete transaction classes (e.g., \PhabricatorCoreCreateTransaction\, \PhabricatorEditEngineNameTransaction\) are created to handle specific operations like creating objects, renaming forms, changing field defaults, and managing subtypes. This refactoring isolates the logic for these specific transaction types under the new modular base classes.

src/applications/transactions/xaction · high confidence

Modularize search engine extensions

The search engine architecture is now modularized via a new extension system in the \engineextension\ directory. This introduces abstract base classes and concrete implementations for various search capabilities, including fulltext indexing (Ferret, Lisk, Ngrams), edge indexing, hovercard rendering, and ID/PHID queries. The system allows third-party code to extend upstream datasources and search behaviors through these extensions, separating concerns like indexing, enrichment, and query constraint application into distinct, pluggable components.

src/applications/search/engineextension · high confidence

Refactor Differential parsing into dedicated parser classes

The diff parsing and commit message handling logic in Differential has been extracted from monolithic classes into dedicated, standalone parser classes. This change introduces \DifferentialChangesetParser\ to handle changeset rendering and line adjustment, \DifferentialHunkParser\ for hunk-level data processing, \DifferentialLineAdjustmentMap\ to track inline comment positions across diff updates, and \DifferentialCommitMessageParser\ to separate commit message field parsing from Conduit. Custom field parsers for 'Depends On' and 'Reverts' are also now distinct classes, improving modularity and testability of the parsing layer.

src/applications/differential/parser · high confidence

Refactor Diffusion file content queries into a dedicated query hierarchy

The file content retrieval logic for Git, Mercurial, and Subversion repositories has been reorganized into a new class hierarchy under src/applications/diffusion/query/filecontent. This change introduces an abstract DiffusionFileContentQuery base class with specific implementations (DiffusionGitFileContentQuery, DiffusionMercurialFileContentQuery, DiffusionSvnFileContentQuery) to handle VCS-specific commands for fetching file blobs. This structural change isolates the command execution logic for each version control system, making the codebase more modular and easier to maintain for future VCS support or command adjustments.

src/applications/diffusion/query/filecontent · high confidence

Refactor commit change parsing into a modular worker hierarchy

The repository commit change parsing logic has been restructured into a new \commitchangeparser\ directory, introducing an abstract \PhabricatorRepositoryCommitChangeParserWorker\ base class and concrete implementations for Git, Mercurial, and Subversion. This change centralizes the parsing workflow—handling lease management, import status flags, and search indexing—while delegating VCS-specific diff parsing to specialized workers. For Git, the worker now uses the Conduit API to retrieve raw diffs; for Mercurial, it parses \hg status\ output to infer directory changes; and for Subversion, it performs complex recursive path resolution to accurately track moves, copies, and deletions. This refactoring improves modularity and testability of the change parsing process.

src/applications/repository/worker/commitchangeparser · high confidence

Refactored repository engine into specialized discovery, pull, and ref management components

The repository engine logic has been reorganized into distinct, specialized classes to improve maintainability and testability. A new \PhabricatorRepositoryDiscoveryEngine\ now handles the initial discovery of commits and refs for Git, Mercurial, and Subversion repositories, including logic for marking repositories as importing during large initial loads. \PhabricatorRepositoryPullEngine\ manages the creation and updating of local working copies, handling VCS-specific commands like \git clone\ or \hg pull\, and installs hooks for hosted repositories. \PhabricatorRepositoryRefEngine\ is responsible for updating ref cursors, tracking branch/bookmark/tag positions, and managing the permanent flag on commits. Additionally, \PhabricatorRepositoryMirrorEngine\ provides dedicated logic for pushing repository changes to configured mirrors, and \PhabricatorRepositoryIdentityEditEngine\ offers a UI engine for editing repository identity configurations. These changes centralize VCS-specific operations and separate concerns between pulling, discovering, and managing references.

src/applications/repository/engine · high confidence

Reorganize Phortune controllers into subdirectories

The Phortune application's controller files have been moved into dedicated subdirectories (product and provider) to improve code organization. This change relocates PhortuneProductListController and PhortuneProductViewController into the product folder, and PhortuneProviderActionController into the provider folder, without altering their underlying functionality.

src/applications/phortune/controller/product, src/applications/phortune/controller/provider · high confidence

Repository storage layer restructured with new entity classes and schema definitions

The storage layer for the Repository application has been reorganized into a set of dedicated entity classes, each managing its own database table and configuration. This change introduces new storage models for core repository data (PhabricatorRepository), commit details and metadata (PhabricatorRepositoryCommit, PhabricatorRepositoryCommitData), and branch tracking (PhabricatorRepositoryBranch). It also adds support for auditing commits (PhabricatorRepositoryAuditRequest), tracking identity mappings for authors and committers (PhabricatorRepositoryIdentity), and managing Git LFS references (PhabricatorRepositoryGitLFSRef). Additionally, the diff includes new classes for recording push and pull events (PhabricatorRepositoryPushEvent, PhabricatorRepositoryPullEvent, PhabricatorRepositoryPushLog), managing reference history and positions (PhabricatorRepositoryRefCursor, PhabricatorRepositoryRefPosition, PhabricatorRepositoryOldRef), and handling commit hints for rewritten or unreadable commits (PhabricatorRepositoryCommitHint). The schema specifications for tables like coverage, filesystem, lint messages, and path changes are also defined within PhabricatorRepositorySchemaSpec, establishing the underlying data structure for these new entities.

src/applications/repository/storage · high confidence

Behavioural changes

2731 commits (308 fixes) modifying webroot

A change to existing behaviour in webroot — 2731 commits (308 fixs), 487 files: “Make "View" links on Differential inline comment previews work again”; “Make server components of inline comment content handling state-oriented”; “Notications mobile menu”; and 2723 more (refs \#666, \#2, \#4902, \#888, \#999).

webroot · medium confidence · unverified

3718 commits (85 fixes) modifying src

A change to existing behaviour in src — 3718 commits (85 fixs), 166 files: “Consolidate repository identity resolution and detection code”; “Remove remaining arcanist project code”; “Converting badge quality property from color to an integer representation for later sorting purposes”; and 3702 more.

src · medium confidence · unverified

444 commits (40 fixes) modifying src/docs

A change to existing behaviour in src/docs — 444 commits (40 fixs), 159 files: “Fixed typo in Phame user guide”; “Normalize Remarkup Diviner article examples”; “Rename Conduit classes”; and 440 more.

src/docs · medium confidence · unverified

Add 'Sign With MFA' comment action to transaction groups

Users can now apply Multi-Factor Authentication (MFA) as a comment action on any transaction group without needing CAN\_EDIT capability. This new 'Sign With MFA' option appears in the edit interface, allowing users to submit transactions while being prompted for MFA verification, effectively decoupling the signing requirement from edit permissions.

src/applications/auth/engineextension · high confidence

Add OwnersPackageReplyHandler stub

A new reply handler class for OwnersPackages has been added. It validates that the receiver is an OwnersPackage instance and explicitly returns null for both private and public reply handler email addresses, while the receiveEmail method is implemented as a no-op, effectively disabling email replies for this entity type.

src/applications/owners/mail · high confidence

Add credential author policy and default view/edit capabilities for Passphrase

Users can now control access to Passphrase credentials based on the user who created them via a new 'Credential Author' policy rule, which grants actions to the credential's author. Additionally, default view and edit policies for Passphrase have been introduced, with view access explicitly allowing public policy settings to be configured.

src/applications/passphrase/capability, src/applications/passphrase/policyrule · high confidence

Add rate limiting to authentication actions

New rate-limiting actions have been introduced for password changes, email login, multi-factor authentication enrollment and verification, and account recovery link generation. These changes restrict the number of attempts users can make within specific time windows, helping to prevent brute-force attacks and abuse of authentication flows.

src/applications/auth/action · high confidence

Add robots.txt handling for blog, short, platform, and resource domains

This change introduces a new controller hierarchy for serving robots.txt files, allowing distinct indexing rules per site type. Blog domains now allow full indexing with a crawl delay, while short and resource domains disallow all content to prevent indexing. The platform domain specifically disallows /diffusion/ and /source/ paths to avoid indexing expensive or less useful content, while still allowing commit pages to be indexed.

src/applications/system/controller/robots · high confidence

Added Aphlict connection validation to setup checks

The setup verification process now includes a specific check for the Aphlict notification server. During setup, the system attempts to establish a connection to the configured notification server; if the connection fails, it presents a clear error message to the user, suggests verifying the configuration or restarting the server, and provides the command to start the service.

src/applications/notification/setup · high confidence

Almanac entities now use EditEngine for editing

Almanac Devices, Services, Interfaces, Networks, Namespaces, and Bindings are now edited through the EditEngine framework. This provides a consistent, unified interface for creating and modifying these resources, including support for custom properties, policy-based access control, and Conduit API integration.

src/applications/almanac/editor · high confidence

Aphlict server rewritten to use WebSockets with message replay and clustering support

The Aphlict server implementation has been replaced with a new architecture that uses WebSockets instead of the previous protocol, enabling real-time push notifications. This change introduces message history buffering, allowing clients to request a replay of recent messages upon reconnection to prevent data loss. The server now supports clustering via peer-to-peer message broadcasting with fingerprinting to avoid loops, and provides a structured status API for monitoring active listeners and message counts. Additionally, the server now integrates with the Javelin library for class definitions and strict mode compliance.

support/aphlict/server · high confidence

Applications selector now uses a typeahead with installation-aware filtering

The pinned applications selector has been converted to a typeahead interface. This new component filters results to show only applications installed for the current user and displays application names alongside their short descriptions, providing a more intuitive way to browse and select applications.

src/applications/meta/typeahead · high confidence

Asynchronous commit-to-revision/task updates via dedicated worker

Updates to Differential Revisions and Maniphest Tasks triggered by commits are now processed asynchronously by a new \DiffusionUpdateObjectAfterCommitWorker\. This worker runs in the task queue, ensuring that commit processing does not block on object updates. It uses the omnipotent viewer to fetch diffs and load objects, allowing it to update edges and statuses (such as closing revisions or changing task status) even when the commit author lacks direct permissions to view the target objects, while still attributing the changes to the commit's author or committer identity where possible.

src/applications/diffusion/worker · high confidence

Audit application merged into Diffusion

The Audit application has been merged into Diffusion, as indicated by the new PhabricatorAuditApplication class which now points to the Diffusion base URI and cannot be uninstalled independently. Users will no longer see Audit as a separate top-level application; instead, audit functionality is integrated within the Diffusion interface, with the application pinned by default alongside Diffusion.

src/applications/audit/application · high confidence

Audit application now uses commit search for navigation

The Audit controller now integrates with the commit search engine to populate its side navigation menu, replacing previous navigation logic. This change ensures that audit-related views are filtered and organized based on commit search results, improving discoverability and consistency with other search-driven interfaces.

src/applications/audit/controller · high confidence

Audit comments and actions are now managed via a transactional editor

The Audit application now uses a new \PhabricatorAuditEditor\ to handle comment posting, inline state changes, and auditor modifications through a unified transaction system. This change replaces previous direct database writes with a structured editor that supports standard transaction types (comments, edges, inline states) and ensures that audit actions like adding auditors or changing status are recorded as explicit transactions, improving consistency with other Phabricator applications and enabling better email threading and history tracking.

src/applications/audit/editor · high confidence

Audit comments now render as inline code comments

The audit view now displays comments as inline annotations on specific lines of code, consistent with how Differential handles code reviews. This change introduces a new view class that groups and sorts inline comments by file path and line number, rendering them via a standard inline summary view rather than as a simple list of transaction logs.

src/applications/audit/view · high confidence

Audit inline comments migrate to transaction-based storage

Inline comments in the Audit application are now stored as transaction comments rather than legacy objects, enabling features like reply threading, persistent editing states, and individual hiding. This change introduces new storage classes (PhabricatorAuditTransactionComment) that support attributes, reply tracking, and integration with the standard comment infrastructure, while maintaining backward compatibility for existing comment data.

src/applications/audit/storage · high confidence

Audit status and action constants are now defined in dedicated classes

Audit-related constants are now centralized in new dedicated classes: PhabricatorAuditActionConstants defines action identifiers (such as 'concern', 'accept', 'add\_ccs', and 'add\_auditors'), while PhabricatorAuditRequestStatus defines request statuses (like 'audit-required', 'accepted', and 'resigned') along with their display names, icons, and Conduit values. This change provides a structured, reusable source for audit UI strings and API values, ensuring consistency between the interface and backend.

src/applications/audit/constants · high confidence

Automatic repository identity updates on user or email destruction

The system now automatically updates repository identities when associated users or email addresses are destroyed. A new destruction engine extension schedules a background task to refresh these identities, ensuring that manual user associations are cleared if the user no longer exists and that identities are correctly resolved. This change also includes a new engine for resolving and updating identities, supporting a dry-run mode for testing.

src/applications/diffusion/identity · high confidence

Badge recipients list now shows awarder and date

The badge recipients view has been updated to display additional context for each recipient. In addition to the recipient's name and profile link, each entry now shows who awarded the badge and when it was granted (e.g., 'Awarded by \[User\] on \[Date\]'). This information is rendered using the standard PHUIObjectItemView styling, consistent with the rest of the badges interface.

src/applications/badges/view · high confidence

Badges now use EditEngine for creation and editing

The Badges application now uses the EditEngine framework to manage badge creation and editing. This change introduces a unified interface for configuring badge properties such as name, flavor text, icon, quality, and description, as well as managing award and revoke recipients. It also enables commenting on badges and integrates badge activity into the standard transaction and mail notification system, ensuring users receive updates when badges are created, modified, or commented on.

src/applications/badges/editor · high confidence

Build steps are now organized into categorized groups

Harbormaster build steps are now organized into distinct groups (Builtins, Flow Control, Drydock, External Build Systems, Testing Utilities, Prototypes, and Other) to improve navigation and selection. This change introduces a new \HarbormasterBuildStepGroup\ base class and specific group implementations that define display names, sort orders, and visibility rules (such as hiding groups when empty or conditionally enabling Drydock and Prototype groups based on application availability and configuration).

src/applications/harbormaster/stepgroup · high confidence

Calendar events and imports now use modular transactions

Calendar event and import operations are now handled through a modular transaction system, replacing the previous implementation. This change introduces specific transaction types for managing event properties (such as name, description, dates, recurrence, host, and invitees) and import settings (including ICS file/URI sources, update frequency, and enable/disable states). For users, this provides more granular and consistent tracking of changes to calendar events and import sources, with clearer audit trails for actions like accepting/declining invitations, editing recurrence rules, or reloading import sources.

src/applications/calendar/xaction · high confidence

Centralized Harbormaster build status definitions with UI metadata

Build statuses for builds, buildables, and unit tests are now defined in dedicated constants classes (HarbormasterBuildStatus, HarbormasterBuildableStatus, HarbormasterUnitStatus) that specify human-readable names, icons, and colors. This change standardizes how status labels and visual indicators are rendered in the UI and ensures consistent display of build states like building, passed, failed, and paused.

src/applications/harbormaster/constants · high confidence

Centralized email body rendering with Remarkup support

Application emails now use a new centralized view class (PhabricatorMetaMTAMailBody) to build and render message bodies section-by-section. This change enables proper processing of Remarkup syntax in both plaintext and HTML email bodies, ensuring consistent formatting across notifications. It also introduces dedicated methods for adding links and attachments, and provides context objects to fix relative URI rendering in emails.

src/applications/metamta/view · high confidence

Centralized repository type definitions and metadata

The system now uses a dedicated constants class to define supported version control types (Git, Mercurial, Subversion) and their associated display metadata, including human-readable names, icons, and UI labels for repository creation. This change centralizes the configuration of repository type specifications, ensuring consistent presentation across the application.

src/applications/repository/constants · high confidence

Centralized transaction-based email reply handling with space and command support

This change introduces a new abstract base class, PhabricatorApplicationTransactionReplyHandler, which consolidates the logic for processing incoming emails that create or modify application objects. For users, this means that email replies are now handled through a unified, robust framework that automatically subscribes recipients to new objects, supports mail-based commands (like !edit or !close) with clear error messages for invalid inputs, and correctly assigns new objects to their appropriate Spaces when created via email. This refactoring ensures consistent behavior across different application types while providing a stable foundation for future extensions.

src/applications/transactions/replyhandler · high confidence

ChatLog application marked as deprecated

The ChatLog application is now officially deprecated, indicated by the '(Deprecated)' short description in its application metadata. The application remains functional with its existing routes and icon, but users should be aware that this feature is no longer actively supported.

src/applications/chatlog/application · high confidence

Clean up flags and notifications when objects are destroyed

When an object is deleted, the system now automatically removes associated flags and notifications to prevent orphaned data. Specifically, deleting an object clears all flags attached to it (where it is the target) and all flags owned by it, as well as any feed story notifications linked to that object's PHID.

src/applications/flag/engineextension, src/applications/notification/engineextension · high confidence

Configurable user profile fields and real name requirements

Administrators can now control which fields appear on user profiles (such as real name, title, blurb, icon, roles, status, and since date) and whether real names are mandatory. The new PhabricatorUserConfigOptions class exposes these settings, allowing admins to enable or disable specific profile fields and enforce real name requirements via configuration.

src/applications/people/config · high confidence

Configuration edits are now tracked via transactions

The configuration editor now uses a transactional model to record changes to application settings. This enables the system to maintain an edit history for configuration values and supports features like draft revisions and explicit validation of complex attributes when changes are applied.

src/applications/config/editor · high confidence

Conpherence Conduit API methods restructured and marked as frozen

The Conpherence Conduit API methods have been reorganized into a new class hierarchy (ConpherenceConduitAPIMethod) and standardized with protected visibility for parameters, returns, and errors. The 'conpherence.createthread' and 'conpherence.updatethread' methods are now explicitly marked as frozen with a deprecation notice directing users to use 'conpherence.edit' instead. New methods 'conpherence.querythread' and 'conpherence.querytransaction' have been added to allow querying threads and transactions respectively. The 'conpherence.edit' method is introduced as the new unified way to create or edit Conpherence rooms using the EditEngine.

src/applications/conpherence/conduit · high confidence

Conpherence message rendering and pagination logic

The Conpherence application now uses a new \ConpherenceTransactionRenderer\ to handle how messages are displayed and paginated. This renderer groups messages from the same author within 120 seconds to reduce visual clutter, inserts date markers to separate messages by day, and provides 'Show Older Messages' and 'Show Newer Messages' buttons to allow users to load message history incrementally rather than all at once.

src/applications/conpherence · high confidence

Conpherence rooms now use the EditEngine for creation and editing

Conpherence room creation and editing are now handled by the new ConpherenceEditEngine, providing a standardized form interface for setting the room name, topic, and initial participants. This change replaces the previous mechanism with a unified EditEngine integration, allowing users to configure room details through a consistent UI flow that aligns with other Phabricator applications.

src/applications/conpherence/editor · high confidence

Conpherence threads now use modular transactions

Conpherence thread updates are now handled via a modular transaction system, replacing the previous approach. This introduces specific transaction types for managing thread participants, titles, topics, profile pictures, and date markers, allowing for more granular and consistent handling of thread state changes. Users will see updated activity feed entries reflecting these modular actions, such as joining/leaving rooms, renaming threads, or updating topics and images.

src/applications/conpherence/xaction · high confidence

Consolidate script initialization and add bulk management entry point

The scripts directory now uses a unified initialization entry point (\_\_init\script\\_.php) that delegates to the shared init-script.php, ensuring consistent environment setup for all CLI tools. Additionally, a new manage\_bulk.php script has been added as a symlink to the existing setup/manage\_bulk.php, providing a convenient entry point for performing silent bulk edits via the command line.

scripts · high confidence

Countdown application controllers refactored to use EditEngine and SearchEngine

The Countdown application's controller layer has been restructured to delegate core functionality to dedicated engine classes. The EditController now utilizes PhabricatorCountdownEditEngine for handling edits, while the ListController and ViewController rely on PhabricatorCountdownSearchEngine for data retrieval and response building. This change introduces public access for both listing and viewing countdowns (via shouldAllowPublic) and integrates the edit engine into the navigation breadcrumbs. The view controller also adopts the new PHUITwoColumnView layout and PHUIHeaderView for displaying countdown details, status, and author information.

src/applications/countdown/controller · high confidence

Countdowns can now be sorted by end date and filtered by author or status

Users can now sort countdown lists by their end date (either past-to-future or future-to-past) and filter results to show only upcoming countdowns or those authored by the current user. This is enabled by new query and search engine classes that support ordering by the 'epoch' column and filtering by author PHIDs and an 'upcoming' flag.

src/applications/countdown/query · high confidence

Countdowns now use the EditEngine and support email notifications

The Countdown application has been migrated to use the standard EditEngine framework, providing a unified interface for creating and editing countdowns with fields for name, end date, and description. This change also introduces email notifications for countdown activity, including details about changes, comments, and other actions, with support for rendering remarkup in email bodies.

src/applications/countdown/editor · high confidence

Daemon status and logs are now tracked via event listeners

The system now uses a new event listener (PhabricatorDaemonEventListener) to monitor daemon lifecycle events such as launch, heartbeat, logging, graceful shutdown, and exit. This replaces previous mechanisms (likely Conduit-based) with a more robust event-driven approach, ensuring that daemon logs, status changes, and unique IDs are accurately recorded in the Phabricator daemon logs.

src/applications/daemon/event · high confidence

DarkConsole core logic moved to new application class

The core functionality for the DarkConsole debugging tool has been extracted into a new \DarkConsoleCore\ class within the \src/applications/console/core\ directory. This change introduces a plugin-based architecture where the core class automatically discovers and initializes \DarkConsolePlugin\ instances using \PhutilClassMapQuery\. It also implements logic to sanitize plugin data for JSON storage, specifically truncating large strings to prevent encoding errors, and manages the lifecycle of these plugins during request startup and shutdown.

src/applications/console/core · high confidence

DarkConsole settings and data retrieval moved to dedicated controllers

DarkConsole toggle and tab-switching actions are now handled by DarkConsoleController, which persists user preferences and forces a user settings cache regeneration to prevent misleading cache-fill metrics. Data retrieval for the console panels is handled by DarkConsoleDataController, which fetches cached console data, decodes it using phutil\_json\_decode, and renders panel content while stripping session cookies from the output for security.

src/applications/console/controller · high confidence

Database schema migrations for new features and modernization

This update applies a large set of database schema migrations to support new application features and modernize existing storage. Key changes include introducing the Dashboard application with its own tables and transaction logs, adding multi-factor authentication (MFA) support via the \auth\_factorconfig\ table, and enabling SMS messaging with a new \sms\ table. The schema also migrates user status to Calendar events, modernizes Differential comment storage by dropping legacy tables and using transaction-based comments, and updates Harbormaster to use build messages and steps with transaction logs. Additionally, it adds support for Drydock blueprint names, Legalpad document signature secrets, and expands password hash storage to 128 characters.

resources/sql/autopatches · high confidence

The \repository.query\ Conduit API method is now marked as frozen and will eventually be deprecated. Users should migrate to the \diffusion.repository.search\ method for querying repositories. The existing \repository.query\ implementation remains functional but explicitly directs new code toward the replacement API.

src/applications/repository/conduit · high confidence

Deprecate slowvote.info and add slowvote.poll.search API method

The Conduit API for the Slowvote application has been updated with a new search capability and the deprecation of an older endpoint. A new 'slowvote.poll.search' method is now available, leveraging the standard search engine infrastructure to read information about polls. Concurrently, the existing 'slowvote.info' method has been marked as deprecated with a status indicating it is replaced by the new search method, though it remains functional for retrieving specific poll details by ID.

src/applications/slowvote/conduit · high confidence

Deprecation of legacy feed.http-hooks configuration

The legacy 'feed.http-hooks' configuration option in the Feed application settings is now locked and marked as deprecated. Users are advised that this option will be removed in a future version and should migrate to Webhooks configured via Herald for feed story delivery.

src/applications/feed/config · high confidence

Deprecation of repository push reply handlers

The system no longer supports receiving replies to repository push notifications via email. The dedicated reply handler for push events has been removed, meaning users can no longer interact with or reply to push notification emails through the previous mechanism.

src/applications/repository/mail · high confidence

Differential commit message fields are now modular custom fields

Commit message fields (such as Title, Summary, Test Plan, Reviewers, Auditors, Tasks, and Tags) have been refactored into a modular system of dedicated classes extending a new base class. This change allows these fields to be managed as standard custom fields, enabling them to be enabled, disabled, and ordered via the custom field configuration UI. It also introduces support for custom ad-hoc commit message fields, making the parsing and storage of commit messages more flexible and consistent with other Phabricator data.

src/applications/differential/field · high confidence

Differential revision actions are now modular transaction types

Core revision actions—such as Accept, Reject, Plan Changes, Close, Reopen, Abandon, Reclaim, Commandeer, and Resign—have been refactored into dedicated, modular transaction classes (e.g., DifferentialRevisionAcceptTransaction). This change standardizes how these actions are recorded, validated, and exposed via the Conduit API, ensuring consistent behavior for reviewer states, draft handling, and action conflicts across the web UI and CLI.

src/applications/differential/xaction · high confidence

Differential revision edges modernized with explicit type classes and inverse transaction support

The edge definitions for Differential revisions have been refactored into dedicated \PhabricatorEdgeType\ subclasses (e.g., \DifferentialRevisionDependsOnRevisionEdgeType\, \DifferentialRevisionHasTaskEdgeType\). This change introduces modern language in user-facing messages (e.g., "parent revision" instead of generic terms), enables automatic inverse transaction writing for relationships like parent/child and task associations, and exposes these edges via the \edge.search\ API. Notably, the reviewer relationship (\DifferentialRevisionHasReviewerEdgeType\) no longer writes inverse transactions, while dependency and task edges now explicitly define conduit keys and descriptions for better discoverability and consistency.

src/applications/differential/edge · high confidence

Display project workboard column context in property lists

The property list view for objects tagged with projects now includes annotations showing which workboard columns the object appears in, providing immediate context for task status. This feature is currently limited to Maniphest tasks; for other object types, only the project tags are displayed. Additionally, the view on Diffusion commits is explicitly configured to show build status while suppressing the Projects, Subscriptions, and Tokens properties.

src/applications/project/events · high confidence

Diviner books now support configurable view and edit policies

Users can now control access to Diviner books through specific policy capabilities. The system introduces default view and edit policies, allowing administrators to define who can view or modify these books. This change enables more granular permission management for Diviner content, ensuring that sensitive documentation can be restricted while still allowing public visibility if desired.

src/applications/diviner/capability, src/applications/diviner/editor · high confidence

Diviner documentation now accessible without login

The Diviner application controllers have been updated to allow public access to documentation. All new controllers (DivinerAtomController, DivinerAtomListController, DivinerBookController, DivinerFindController, and DivinerMainController) now return true from shouldAllowPublic(), meaning users can view documentation books, atom details, and search results without being logged in. This change improves discoverability and usability of the documentation system for external visitors.

src/applications/diviner/controller · high confidence

Diviner search now indexes Live Books and Live Symbols with correct open/closed status

The Diviner search index now includes full-text support for Live Books and Live Symbols via new fulltext engine classes. Live Book entries are indexed by title and preface, while Live Symbol entries are indexed by title and summary. Crucially, Live Symbols are now correctly associated with an 'open' or 'closed' relationship based on their graph hash, fixing a previous issue where this status was flipped. This allows users to search for and filter Diviner documentation by the current state of symbols.

src/applications/diviner/search · high confidence

Drydock query and search infrastructure modernized with policy awareness and name search

The Drydock application's query layer has been restructured to use a new \DrydockQuery\ base class that integrates with the \PhabricatorCursorPagedPolicyAwareQuery\ framework, ensuring that all queries (Blueprints, Resources, Leases, Logs, Authorizations, and Repository Operations) respect user permissions and access controls. This change introduces a dedicated \DrydockAuthorizationQuery\ to manage and filter authorizations, and updates the \DrydockBlueprintQuery\ and its search engine to support searching blueprints by name substring and filtering by disabled status. Additionally, the search engines for all Drydock entities now leverage the \PhabricatorApplicationSearchEngine\ interface, providing consistent, policy-aware search capabilities across the application.

src/applications/drydock/query · high confidence

Enforce strict validation for notification server configuration

The system now strictly validates the 'cluster.notifications' configuration, requiring at least one enabled 'admin' server and one enabled 'client' server. Each server entry must specify a valid type ('admin' or 'client'), protocol ('http' or 'https'), host, and port, while 'admin' servers are prohibited from using the 'path' property. Duplicate host:port combinations are also rejected to prevent configuration errors.

src/applications/notification/config · high confidence

The search engine now recognizes Phabricator URIs pasted into the search box and redirects users directly to the target resource, including a fix for URIs lacking a trailing slash to prevent redirection errors. Additionally, self-referential links in the format '/X123' within remarks are now resolved to actual objects, rendering them as clickable handles and treating them as object mentions.

src/applications/meta/engineextension · high confidence

Enhanced typeahead search with owner functions and user availability

The People typeahead now supports advanced query functions like 'anyone()' to find results assigned to any owner, 'none()' for unassigned results, and 'viewer()' to reference the current user, allowing for more dynamic and reusable queries. The user search interface has been modernized to display real-time availability status (away or busy) via colored dots, includes specific handling for mailing list accounts, and provides a unified browse experience for owners, viewers, and project members.

src/applications/people/typeahead · high confidence

Enhanced user mention rendering with availability status and access control

The mention markup system now displays user availability indicators (colored dots) and access restrictions directly within @username mentions. When a user is mentioned, the system checks their availability to apply specific dot colors: grey for disabled users, violet for unresponsive users, red for those marked as away, and orange for others. Additionally, if a mentioned user lacks permission to view the object they were mentioned in, the mention is visually marked with an 'eye-slash' icon and styled as 'exiled' (greyed out) to clearly indicate they cannot see the context. This applies to both HTML email bodies and standard web markup.

src/applications/people/markup · high confidence

Extract workboard view state into a dedicated class

The logic for managing workboard view state—specifically ordering, filtering, and hidden columns—has been moved from the View controller into a new \PhabricatorWorkboardViewState\ class. This change centralizes how request parameters (such as \order\, \filter\, and \hidden\) are read, validated, and serialized back into URIs, decoupling the state management from the broader view controller logic.

src/applications/project/state · high confidence

Favorites menu now appears in the main navigation bar

The Favorites menu has been moved from the profile menu to the main top-level navigation bar via the new PhabricatorFavoritesMainMenuBarExtension. Users will now see a dedicated 'Favorites' button (with a bookmark icon) in the main menu bar, providing quicker access to their saved items without needing to open the profile menu first.

src/applications/favorites/engineextension · high confidence

File operations now use ModularTransactions

File-related actions such as setting alternate text, deleting files, and updating names are now handled through the ModularTransactions system. This change introduces specific transaction types (file:alt, file:delete, file:name) that extend the new PhabricatorFileTransactionType base class, enabling consistent tracking and feed updates for these file modifications.

src/applications/files/xaction · high confidence

Files application controllers rewritten with new UI, chunked uploads, and granular policies

The Files application controllers have been completely rewritten to modernize the user experience and underlying architecture. Users can now upload files via HTML5 chunked transfers and global drag-and-drop, with partial uploads supported for large files. The interface includes a new lightbox view with inline commenting, a profile image composer for selecting icons and colors, and a 'curtain' UI for attaching or detaching files from objects. Access control is more granular, allowing explicit view policies on uploads and enforcing restrictive defaults for files dropped onto objects. File serving now supports HTTP Range requests for better media playback, automatic gzip compression, and secure downloads via one-time tokens or alternate CDN domains.

src/applications/files/controller · high confidence

Files editing and commenting moved to EditEngine

The Files application now uses the centralized EditEngine for editing file properties and adding comments. Users can now explicitly configure view policies on files and edit file names and alt text through a unified editing interface, replacing the previous ad-hoc editing mechanism.

src/applications/files/editor · high confidence

Files now use /Fxxx URIs and handles

File references in the system now use a concise handle format (e.g., F123) and corresponding URIs, replacing previous naming conventions. This change ensures that file handles are displayed as 'F{id}: {name}' and that files can be loaded by their short ID-based name, improving consistency and readability in file-related interactions.

src/applications/files/phid · high confidence

Flag color constants and icon mapping updated

The flag application now uses a new constants class to define flag colors (Red, Orange, Yellow, Green, Blue, Pink, Purple, Checkered) and maps them to FontAwesome CSS classes (e.g., 'fa-flag pink') instead of the previous Sprite-Icons system. This change ensures that flag colors are rendered correctly using the new icon library, with specific attention to correcting the purple flag's icon mapping.

src/applications/flag/constants · high confidence

Flags are now private by default with owner-only access

The Flag storage layer now enforces strict privacy: flags are visible and editable only by their owner. This is implemented by adding PhabricatorPolicyInterface support to PhabricatorFlag, which defaults to POLICY\_NOONE and grants automatic CAN\_VIEW and CAN\_EDIT capabilities exclusively to the user whose PHID matches the flag's ownerPHID. Users will no longer see flags belonging to other users, and only the creator can modify their own flags.

src/applications/flag/storage · high confidence

Guidance warnings for open registration are now conditional on provider capabilities

The system now only displays warnings about open user registration if at least one configured authentication provider actually allows new users to register. Previously, these warnings appeared regardless of the provider settings; now, if no providers permit registration, the guidance engine returns no results, preventing confusing or irrelevant warnings for administrators.

src/applications/auth/guidance · high confidence

Harbormaster build plans now support modular transactions

Build plan configuration changes (such as updating the name, status, or behavior settings) are now handled through a modular transaction system. This allows these specific plan properties to be tracked, validated, and exposed via Conduit as distinct transaction types, providing a more structured way to manage plan history and API interactions.

src/applications/harbormaster/xaction/plan · high confidence

Harbormaster engine refactored to use dependency-based build graphs and modular engines

The Harbormaster build engine has been restructured to rely on a dependency-based execution model. A new HarbormasterBuildGraph class computes the topological order of build steps, ensuring tasks run in the correct sequence based on their dependencies. The build lifecycle is now managed by a dedicated HarbormasterBuildEngine that handles queuing targets, releasing artifacts, and updating build statuses, while HarbormasterTargetEngine automates the creation of build steps and targets from autotarget keys. This change introduces modular engines for buildables and targets, allowing for more flexible and parallelizable build execution, and adds support for build parameters and initiator tracking via HarbormasterBuildRequest.

src/applications/harbormaster/engine · high confidence

Harbormaster integration now respects Differential revision context and authorship

The Harbormaster integration for Differential has been updated to handle buildable publishing and authorship more accurately. Build results are no longer published to bare diffs that are not attached to a revision, preventing errors when no target revision exists. Additionally, the system now passes commit authorship information (name and email) to external build systems like Buildkite, ensuring correct attribution of builds to the actual code authors rather than just the committer.

src/applications/differential/harbormaster · high confidence

Herald fields are modularized and reorganized into logical groups

The Herald field system has been refactored to support modular, standalone field classes, introducing a new base \HeraldField\ class that standardizes field types, conditions, and value rendering. This change reorganizes available fields into distinct groups (such as 'Herald', 'Edit Attributes', 'Transactions', and 'Related Fields') to improve usability. New fields have been added, including 'Acting user', 'Comment content', 'Content source', 'Is newly created', and 'Another Herald rule', while existing functionality is now structured to allow for easier extension and maintenance.

src/applications/herald/field · high confidence

Herald rule indexing and transcript cleanup

Herald now indexes objects affected by rule conditions and actions, enabling more accurate identification of objects related to specific rules. Additionally, when a Herald transcript's associated object is destroyed, the system now automatically cleans up the related transcript records.

src/applications/herald/engineextension · high confidence

Herald rules for Differential now use modular field and action classes

Herald integration with Differential has been refactored to use dedicated, modular classes for fields and actions. This introduces specific Herald fields for Differential revisions and diffs—including author, affected files, content changes, repository, packages, and JIRA issue URIs—and modular actions for adding reviewers (including blocking reviewers and self-reviewers) and blocking diffs. The change also adds state-reason explanations to clarify why certain rules (like mail or builds) do not trigger, such as when a revision is a draft, unchanged, or automatically updated in response to a commit.

src/applications/differential/herald · high confidence

Herald storage layer refactored to use modular transactions and new webhook models

The Herald storage layer has been restructured to support transactional history and new webhook capabilities. Herald rules and webhooks now implement PhabricatorApplicationTransactionInterface, enabling their edits to be tracked via HeraldRuleTransaction and HeraldWebhookTransaction respectively. New storage models have been introduced: HeraldActionRecord and HeraldCondition store rule actions and conditions as separate child entities linked by ruleID, while HeraldWebhook and HeraldWebhookRequest manage webhook configurations and delivery status (including firehose, enabled, and disabled states) with HMAC key support and error backoff logic.

src/applications/herald/storage · high confidence

Herald transcripts now provide structured, detailed rule and condition evaluation logs

The Herald application now records a much more detailed and structured history of rule evaluations. Instead of simple pass/fail flags, transcripts now capture specific outcomes for conditions (e.g., 'Passed', 'Failed', 'Forbidden', 'Invalid', 'Exception') and rules (e.g., 'Matched', 'Failed', 'Recursion', 'Version Issue'). This allows users to see exactly why a rule did or did not trigger, including error messages and dependency cycle details. Additionally, the system now tracks which specific transaction PHIDs were applied by each rule effect, and object field values in transcripts are truncated to 4096 characters to improve performance and storage efficiency.

src/applications/herald/storage/transcript · high confidence

Implement real dashboard panels for the homepage

The homepage view now renders actual dashboard panels instead of hardcoded placeholders. It displays 'Active Revisions' (if Differential is installed), 'Assigned Tasks' (or 'Open Tasks' for guests) via Maniphest, 'Active Repositories' via Diffusion, and a 'Recent Activity' feed. This provides a functional, multi-column dashboard layout on the home page rather than static content.

src/applications/home/view · high confidence

Improved JSON formatting for configuration values

Configuration values are now displayed with better readability. Arrays with sequential numeric keys are formatted as lists, while other arrays are formatted as objects, and forward slashes in strings are unescaped to make paths easier to read.

src/applications/config/json · high confidence

Improved error reporting for configuration file issues

The configuration loading logic now surfaces syntax errors and other problems within config files to the user instead of failing silently. When a config file cannot be parsed, the system captures PHP errors and throws a clear exception detailing the failure. Additionally, if a specified config file is missing, the error message now lists the valid configuration files available in the directory, helping users correct their setup more easily.

conf · high confidence

Improved file upload error messaging and new exception types

Users now receive more specific and actionable error messages when file uploads fail. The system distinguishes between server-side configuration limits (showing the current \upload\_max\_filesize\ and suggesting a php.ini change) and other upload issues like partial transfers or missing temporary directories. Additionally, new exception classes (\PhabricatorFileIntegrityException\, \PhabricatorFileStorageConfigurationException\, and \PhabricatorFileUploadException\) have been introduced to handle integrity checks, storage configuration errors, and upload failures respectively, allowing for more precise error handling in the file application.

src/applications/files/exception · high confidence

Improved project name generation and test data creation

The lipsum tool now generates more realistic project names by using a context-free grammar that combines technical terms (like 'Backend', 'Drones') with actions and suffixes (like 'Automation', 'Optimization'). Additionally, the project test data generator has been updated to use modular transactions for setting project names, statuses, and members, replacing the previous approach.

src/applications/project/lipsum · high confidence

Introduce 'Draft' revision state and modernize Differential status constants

Differential now supports a new 'Draft' revision status, allowing authors to save work-in-progress revisions without triggering review workflows. The application's status constants have been migrated from legacy numeric values to modern string keys (e.g., 'accepted', 'published', 'needs-review'), with 'Published' replacing the previous 'Closed' terminology for committed revisions. This change also standardizes lint and unit test statuses (e.g., 'Not Applicable' vs 'Skipped') and introduces a 'Changes Planned' state, providing clearer visual indicators and more granular control over revision lifecycle management.

src/applications/differential/constants · high confidence

Introduce AphrontApplicationConfiguration for request building and startup orchestration

The system now uses a new AphrontApplicationConfiguration class to manage the core request lifecycle. This change centralizes how HTTP requests are constructed (parsing POST data and query strings) and orchestrates the startup sequence, including preflight setup checks, environment initialization, and access logging. It also establishes the base URI for the application based on the incoming request headers if not explicitly configured.

src/aphront/configuration · high confidence

Introduce AphrontMalformedRequestException for client errors

The system now distinguishes malformed client requests from other exceptions via a new AphrontMalformedRequestException class. This exception allows the framework to handle requests that fail early or fundamentally in processing, and supports an 'unlogged' mode to prevent non-actionable client errors from cluttering server logs.

src/aphront/exception · high confidence

Introduce Application Email PHID type and refine object handle data model

Users can now reference application email addresses as distinct objects with their own PHIDs (type 'APPE'), enabling them to be handled consistently with other Phabricator entities in lists and queries. Additionally, the underlying object handle system has been updated to explicitly separate 'status' (e.g., open/closed) from 'availability' (e.g., full/partial/restricted), allowing the UI to more accurately reflect when an object is restricted by policy versus when it is simply unavailable or disabled.

src/applications/phid · high confidence

Introduce Application metadata and lifecycle management

The system now tracks application status (installed, prototype, uninstalled) and metadata (name, group, icon) via the new PhabricatorApplication base class, allowing users to see which applications are active and enabling the uninstallation of optional applications like Support.

src/applications/base · high confidence

Introduce CLI mail management and inbound processing scripts

This change adds two new command-line scripts to manage email operations. The \scripts/mail/mail\_handler.php\ script replaces the previous web-based inbound mail handling by processing incoming emails via stdin, including robust UTF-8 transcoding for text and HTML bodies, MIME header decoding, and attachment handling (specifically skipping inline text attachments while preserving other file types). The \scripts/mail/manage\_mail.php\ script provides a CLI interface for mail management workflows, dynamically loading them via class map queries. This moves mail processing out of the web UI and into the CLI, improving reliability and allowing for better error handling and duplicate processing controls.

scripts/mail · high confidence

Introduce Conpherence Thread PHID type with ZXXX monograms

Users can now reference Conpherence threads using a simplified 'ZXXX' monogram format (e.g., Z123) in global search and handles. This change unifies the previous distinction between rooms and messages, presenting all threads under a single 'Conpherence Room' type. The monogram is derived from the thread's internal ID, allowing for more concise and useful references in the UI.

src/applications/conpherence/phid · high confidence

Introduce EditEngine for Drydock Blueprint creation and management

Users can now create and edit Drydock blueprints through a unified EditEngine interface, replacing previous ad-hoc editing mechanisms. This change enables blueprint creation via the Conduit API (requiring a type transaction) and supports searching for blueprints by name. The editor handles blueprint type selection, name validation, and policy-based access control for creating new blueprints.

src/applications/drydock/editor · high confidence

Introduce EditEngine-based editing for Harbormaster builds, plans, steps, and buildables

This change adds dedicated EditEngine and ApplicationTransactionEditor classes for Harbormaster entities (builds, build plans, build steps, and buildables), replacing ad-hoc editing logic with a unified, transaction-driven edit interface. Users can now create and edit build plans with named fields and configurable behaviors (e.g., hold drafts, affect buildables, warn on landing, restartable, runnable) via standard edit forms; build steps support name, description, and dependency edits through transactions; and builds/buildables gain consistent edit workflows. The build plan editor exposes a name field and behavior selectors that map to specific transaction types, while step editors handle create, name, depends-on, and description changes. This provides a consistent, policy-aware editing experience across Harbormaster objects.

src/applications/harbormaster/editor · high confidence

Introduce EditEngine-based transaction generation for bulk edits

The bulk editor now uses a new EditEngine architecture (PhabricatorEditType and subclasses) to generate transactions, replacing previous hard-coded ad-hoc definitions. This change restores and standardizes bulk edit capabilities for fields such as Tags, Subscribers, Assign To, Status, Priority, and Remarkup comments in Maniphest, while also improving Conduit type handling and supporting stacked actions and draft saving for these edits.

src/applications/transactions/edittype · high confidence

Introduce HandlePool and HandleList for improved handle caching and batching

Users benefit from more efficient loading of object handles through the new PhabricatorHandlePool and PhabricatorHandleList classes. The HandlePool coordinates bulk loading and caching of handles, while the HandleList provides a convenient, array-like interface that supports iteration, counting, and subset creation. This change improves performance by deferring handle fetches until necessary and reusing cached results across requests, reducing redundant database queries when displaying multiple handles in lists or mentions.

src/applications/phid/handle/pool · high confidence

Introduce InnoDB fulltext search support and new search document schema

The search storage layer now supports InnoDB fulltext indexes when the database engine is available, automatically detecting capability via the \@@innodb\_ft\_max\_token\_size\ system variable and configuring the query compiler accordingly. This change introduces the \PhabricatorSearchDocument\ and \PhabricatorSearchDocumentRelationship\ data access objects, defining the column schemas and key indexes for storing search documents and their relationships, and prepares the system to use a stopwords table for future fulltext indexing optimizations.

src/applications/search/storage/document · high confidence

Introduce NuanceConduitAPIMethod base class

A new abstract base class, NuanceConduitAPIMethod, has been added to standardize Nuance-related Conduit API methods. This class extends ConduitAPIMethod, automatically associates methods with the PhabricatorNuanceApplication, and marks them as unstable.

src/applications/nuance/conduit · high confidence

Introduce PHID type handlers for Pholio Images and Mocks

Added PholioImagePHIDType and PholioMockPHIDType classes to register Pholio objects with the PHID system. This enables Pholio images and mocks to be referenced by their PHIDs rather than internal IDs, providing consistent handle loading, URI generation, and named object resolution for these entities within the application.

src/applications/pholio/phid · high confidence

Introduce PhabricatorFact base class and specific fact implementations

The Fact application now uses a new \PhabricatorFact\ abstract base class to manage facts, replacing the previous structure. This change introduces \PhabricatorCountFact\ and \PhabricatorPointsFact\ as concrete implementations for tracking counts and points. The base class provides standardized methods for retrieving all facts, managing fact keys, and generating chart function arguments (specifically for project and owner dimensions), enabling a more modular and consistent approach to fact-based data retrieval and visualization.

src/applications/fact/fact · high confidence

Introduce VCS-specific Diffusion request classes

Diffusion now uses dedicated request classes for each version control system (Git, Mercurial, and Subversion) instead of a single monolithic request object. This change allows each VCS type to implement its own logic for identifying stable commits (e.g., 40-character hex hashes for Git/Mercurial vs. numeric revisions for Subversion) and handling repository-specific details like Subversion subpaths, resulting in more accurate branch resolution and commit identification across different repository types.

src/applications/diffusion/request · high confidence

Introduce application and object mail receivers

The mail receiving system now uses a new extensible architecture with \PhabricatorMailReceiver\ as the base, \PhabricatorApplicationMailReceiver\ for application-level emails (supporting default authors and public replies), and \PhabricatorObjectMailReceiver\ for object-specific replies (validating sender identity and security hashes). This allows multiple receivers to handle incoming mail and provides better error messages when mail processing fails, such as when the sender is unrecognized or the security hash is invalid.

src/applications/metamta/receiver · high confidence

Introduce application-scoped PHID type infrastructure

The system now distinguishes PHID types by their owning application, ensuring that document types for uninstalled applications are hidden from search results and that handle loading is scoped to the correct application context. This change introduces the \PhabricatorPHIDType\ base class with an abstract \getPHIDTypeApplicationClass()\ method, allowing the platform to filter and load PHID-related data based on which applications are currently installed for the viewing user.

src/applications/phid/type · high confidence

Introduce background worker for transaction publishing side effects

A new \PhabricatorApplicationTransactionPublishWorker\ has been added to handle backgroundable work associated with transactions, such as email notifications, feed stories, and search index updates. This worker loads the relevant object and transactions, constructs an editor with a daemon content source, and delegates the publishing process, allowing these side effects to be processed asynchronously rather than synchronously during the initial transaction application.

src/applications/transactions/worker · high confidence

Introduce caching and refined output for Diffusion blame queries

The blame query system now caches results to improve performance, using path digests to generate cache keys and storing data for up to 14 days. For Git repositories, the query now suppresses '^' boundary markers on root commits by passing the '--root' flag, ensuring consistent commit hash display. Mercurial blame queries have been updated to prefer the '--template' argument for cleaner output, falling back to '--debug' only if templates are unavailable, with debug output filtered during parsing.

src/applications/diffusion/query/blame · high confidence

Introduce code-based mail delivery reasons and actor query infrastructure

This change adds a new set of query classes in the MetaMTA application (including PhabricatorMetaMTAActorQuery, PhabricatorMetaMTAMailQuery, and PhabricatorMetaMTAMemberQuery) to support a redesigned mail system. It introduces a structured, code-based approach to tracking why recipients were included or excluded from mail delivery, replacing previous ad-hoc logic. Users will now see specific, human-readable reasons for mail delivery status (such as 'Disabled Recipient', 'Bot Recipient', 'Address Not Verified', or 'Muted') in the mail interface, providing greater transparency into why certain notifications were or were not sent.

src/applications/metamta/query · high confidence

Introduce configurable edit forms and transaction-based editing for Pastes

Users can now create and edit Pastes through a new EditEngine interface that allows configuring creation and editing forms. This change introduces transaction-based editing for Paste properties including title, language (with syntax highlighting support), content, and active/archived status. The system now supports policy-based access control (view and edit policies), comments on Pastes, and email notifications for content changes, comments, and other activity. Language selection is now handled via a typeahead datasource for easier syntax highlighting configuration.

src/applications/paste/editor · high confidence

Introduce dedicated SSH key data structures and interface

This change introduces new internal data structures, \PhabricatorAuthSSHPrivateKey\ and \PhabricatorAuthSSHPublicKey\, along with the \PhabricatorSSHPublicKeyInterface\, to handle SSH key management. The private key class adds robust parsing and validation logic using \ssh-keygen\, specifically improving error reporting to distinguish between format issues and passphrase errors, and includes logic to strip passphrases from stored keys. The public key class adds support for \ssh-ed25519\ keys and implements PKCS8 conversion with caching. The interface defines how different parts of the application (like user settings or device pages) should handle SSH key management workflows.

src/applications/auth/sshkey · high confidence

Introduce dedicated controllers for Phortune cart lifecycle actions

This change restructures the Phortune application by introducing a set of specialized controllers in the \src/applications/phortune/controller/cart\ directory to handle distinct cart operations. A new abstract \PhortuneCartController\ base class manages cart retrieval and enforces authority checks (account vs. merchant) via \shouldRequireAccountAuthority\ and \shouldRequireMerchantAuthority\. Concrete controllers now handle specific workflows: \PhortuneCartCheckoutController\ manages the payment selection and charge application process; \PhortuneCartCancelController\ and \PhortuneCartVoidController\ allow merchants to cancel or void orders with appropriate policy checks; \PhortuneCartAcceptController\ enables manual review acceptance; \PhortuneCartUpdateController\ refreshes charge statuses with payment providers; and \PhortuneCartViewController\ displays the order summary, timeline, and action curtain. This separation clarifies the cart workflow and isolates the logic for checkout, cancellation, voiding, updating, and viewing cart states.

src/applications/phortune/controller/cart · high confidence

Introduce dedicated interfaces for fulltext and ngram search capabilities

The search application now defines specific interfaces to distinguish between general indexability, fulltext search, and ngram-based search. PhabricatorIndexableInterface serves as the base marker, while PhabricatorFulltextInterface extends it to require a newFulltextEngine method, and PhabricatorNgramsInterface extends the base to require a newNgrams method. This structural change allows the system to explicitly support ngram search capabilities for entities like Owners Package names, separate from standard fulltext indexing.

src/applications/search/interface · high confidence

Introduce default view and edit policies for pastes

Users can now configure default access controls for new pastes. The system introduces specific capability classes to define the default view policy (allowing public policy settings) and the default edit policy, establishing the baseline permissions applied when pastes are created.

src/applications/paste/capability · high confidence

Introduce default view and edit policy capabilities for Countdown

The Countdown application now exposes specific policy capabilities for default view and edit permissions. Users can configure default view policies, which now explicitly allow public policy settings, and default edit policies for Countdown resources through the new \PhabricatorCountdownDefaultViewCapability\ and \PhabricatorCountdownDefaultEditCapability\ classes.

src/applications/countdown/capability · high confidence

Introduce explicit file attachment model and chunked storage support

The Files application now distinguishes between files explicitly uploaded by users and those created automatically (e.g., via URL download or system generation) using a new \isExplicitUpload\ flag, which allows users to filter their file lists to show only their own uploads. Additionally, the storage layer has been expanded to support large files through a chunking mechanism (\PhabricatorFileChunk\) and a dedicated attachment table (\PhabricatorFileAttachment\) that manages the relationship between files and objects with specific modes (attach, reference, detach), replacing the previous edge-based attachment system.

src/applications/files/storage · high confidence

Introduce extensible Ferret search function architecture

The Ferret fulltext search engine now uses a modular, extensible class structure for search functions. A new abstract base class, FerretSearchFunction, defines the interface for search functions and includes validation logic for function names and field keys. A concrete subclass, FerretConfigurableSearchFunction, allows for configurable function parameters. The system now automatically discovers and registers search functions provided by fulltext engine extensions via the newFerretSearchFunctions() method, ensuring unique names and keys across all extensions.

src/applications/search/ferret/function · high confidence

Introduce modern Differential storage schema and data models

This change replaces the legacy Differential storage layer with a new, modern schema. It introduces dedicated storage classes for core objects including revisions, diffs, changesets, hunks, reviewers, and inline comments, alongside supporting tables for custom fields, view states, and transaction comments. This restructuring provides a more robust foundation for features like draft revisions, modern transaction handling, and improved inline comment threading.

src/applications/differential/storage · high confidence

Introduce modular SearchField classes for Conduit and UI integration

The search field implementation has been refactored into a modular system of dedicated classes (such as PhabricatorIDsSearchField, PhabricatorPHIDsSearchField, PhabricatorSearchCheckboxesField, and PhabricatorSearchDateField) that extend a new PhabricatorSearchField base. This change standardizes how search parameters are handled across the application, ensuring that UI controls (like text inputs, checkboxes, and date pickers) are consistently mapped to their corresponding Conduit API parameter types. Users benefit from more robust type validation in API calls (e.g., preventing empty lists for ID/PHID fields) and improved handling of saved query data, including better support for deprecated option aliases and modern date parsing.

src/applications/search/field · high confidence

Introduce modular dashboard layout configuration system

The dashboard layout configuration has been refactored into a modular class-based system, introducing new classes in the \layoutconfig\ directory to define layout modes and panel references. This change adds support for distinct layout modes including a single full-width column, two equal columns, and two columns with asymmetric splits (one-third/two-thirds and two-thirds/one-third). The new \PhabricatorDashboardPanelRefList\ class manages the storage and manipulation of panel positions, enabling operations such as adding, removing, and moving panels between columns, which underpins the updated dashboard flow for managing panel content.

src/applications/dashboard/layoutconfig · high confidence

Introduce modular guide system for installation and quick-start

The Guides application now uses a modular architecture to structure onboarding content. A new abstract base class, PhabricatorGuideModule, defines the interface for individual guide sections, which are automatically discovered and sorted by position. Two initial modules are provided: the 'Install' module, which helps users resolve setup issues, configure authentication, and set up notifications; and the 'Quick Start' module, which guides new users through creating repositories, projects, and tasks, as well as personalizing the installation. This change replaces the previous flat guide structure with a scalable, module-based approach.

src/applications/guides/module · high confidence

Introduce modular image transform system with ImageMagick support

The file transformation logic in src/applications/files/transform has been refactored into a modular system using new classes (PhabricatorFileTransform, PhabricatorFileImageTransform, PhabricatorFileThumbnailTransform). This change introduces support for ImageMagick as an alternative backend for image processing, alongside the existing PHP GD library. It also standardizes how various image types (profile, pinboard, preview, workcard) are generated, ensuring consistent scaling and cropping behavior across different view contexts.

src/applications/files/transform · high confidence

Introduce modular relationship sources for Differential, Diffusion, Maniphest, and Pholio

The relationship selection UI now uses a new modular architecture where each application (Differential, Diffusion, Maniphest, Pholio) provides its own relationship source. This allows the system to dynamically enable or disable relationship actions based on whether the corresponding application is installed for the current viewer. For example, Differential and Maniphest tasks are now available as relationship targets only if their respective applications are active, while Diffusion commits and Pholio mocks are similarly gated. This change also standardizes the available filters (e.g., 'Assigned to Me', 'Created By Me') across these sources, with specific sources like Diffusion and Pholio explicitly removing the 'assigned' filter as it is not applicable to their object types.

src/applications/search/relationship · high confidence

Introduce modular transaction storage and policy-aware project models

The Projects application now uses a modular transaction system for storing changes to projects, columns, and triggers, replacing previous ad-hoc storage mechanisms. This change introduces policy-aware models for PhabricatorProject and PhabricatorProjectColumn, allowing users to configure View, Edit, and Join policies, lock membership, and manage subprojects and milestones with granular access control. Additionally, workboard columns now support triggers with customizable rulesets, and the system automatically handles transactional history for metadata changes like names, icons, and colors, ensuring consistent audit trails and mail notifications.

src/applications/project/storage · high confidence

Introduce modular user editing infrastructure

The user editing workflow is now handled by a new modular architecture consisting of three core components in the People application. PhabricatorUserEditEngine provides a configurable UI engine for managing user creation and editing forms, exposing fields for disabling and approving users. PhabricatorUserEditor centralizes the logic for creating, updating, and managing user attributes (such as roles, emails, and system agent status) while ensuring data integrity and logging changes. PhabricatorUserTransactionEditor manages the transactional history and feed stories for these user modifications. This change consolidates previously scattered user editing logic into a unified, transaction-based system.

src/applications/people/editor · high confidence

Introduce new Differential controller architecture

Replaces the legacy Differential controller implementation with a new set of specialized controllers (including DifferentialController, DifferentialRevisionViewController, and DifferentialDiffCreateController) that utilize modern query classes like DifferentialRevisionQuery and DifferentialDiffQuery, integrate with the Owners application for package-based authority, and support updated UI components such as PHUIObjectBoxView and PHUIDiffTableOfContentsListView.

src/applications/differential/controller · high confidence

Introduce new Differential view components for changesets, reviewers, and revision lists

This change adds a suite of new PHP view classes in src/applications/differential/view to modernize the Differential UI. The new components include DifferentialChangesetDetailView and DifferentialChangesetListView for rendering file diffs and their associated lists, DifferentialReviewersView for displaying reviewer statuses (such as Accepted, Requested Changes, or Resigned) with specific icons and authority indicators, DifferentialRevisionListView for the main revision table with reviewer limits and status icons, DifferentialLocalCommitsView for showing local commit history, DifferentialRevisionUpdateHistoryView for comparing diff versions, and DifferentialTransactionView for grouping and rendering inline comments. These views replace older rendering logic with a more structured, component-based approach using PHUIObjectItemView and PHUIStatusListView.

src/applications/differential/view · high confidence

Introduce new Diffusion data model classes for repository browsing and commit metadata

This change adds a suite of new data classes in src/applications/diffusion/data to support structured handling of repository information. DiffusionBrowseResultSet manages file paths and includes logic to identify and prioritize README files (e.g., .remarkup, .md) for display. DiffusionCommitRef and DiffusionCommitHash encapsulate commit details like authorship, committer info, and hash types, replacing direct property access with wrapped methods. DiffusionRepositoryRef and DiffusionRepositoryTag provide generic and tag-specific metadata for repository references. DiffusionGitBranch adds parsing for local and remote branch outputs, while DiffusionLocalRepositoryFilter enforces cluster device safety by rejecting updates to repositories not bound to the current host. DiffusionRepositoryPath and DiffusionPathChange handle file path metadata and change types, facilitating conversion to Arcanist and Differential formats. These classes collectively enhance the data layer's ability to manage repository state, commit metadata, and cluster-aware operations.

src/applications/diffusion/data · high confidence

Introduce new search query compiler with field operators and stemming

The search application now uses a new query compiler (PhutilSearchQueryCompiler) that adds 'absent' and 'present' field operators (e.g., 'title:-' and 'title:\~') and supports substring matching via the tilde operator. The compiler also enforces stricter parsing rules, such as rejecting spaces inside or after operators, and implements token stemming for unquoted terms to improve search relevance. Additionally, field functions like 'title:' now apply to subsequent unquoted tokens and persist across quoted tokens unless the function is 'present' or 'absent'.

src/applications/search/compiler · high confidence

Introduce policy-aware queries and search engine for Ponder questions and answers

This change adds new query classes (PonderQuestionQuery, PonderAnswerQuery, and their transaction counterparts) that extend the policy-aware base classes, ensuring that Ponder questions and answers are filtered by application permissions and user access rights. It also introduces PonderQuestionSearchEngine, which provides a unified search interface for Ponder questions with built-in filters for author, answerer, and status, and supports standard query views like 'Recent', 'Open', 'Resolved', 'Authored', and 'Answered'. These components work together to enforce consistent access control and improve searchability within the Ponder application.

src/applications/ponder/query · high confidence

Introduce silent transaction support in Herald rules

Herald rules can now apply changes silently, preventing mail and other notifications from being sent. This is achieved through new state classes (\HeraldBuildableState\, \HeraldMailableState\) and a specific reason code (\core.silent\) that explains when a change was applied without triggering notifications, allowing for bulk edits or background updates that do not disturb users.

src/applications/herald/state · high confidence

Introduce streaming commit graph parsing and smart scheduling for the local pull daemon

The repository pull daemon now uses dedicated streaming classes (PhabricatorGitGraphStream and PhabricatorMercurialGraphStream) to parse commit history incrementally, which deduplicates parent commits in Git and optimizes Mercurial parent resolution. Additionally, the daemon implements a smarter scheduling mechanism that respects individual repository update intervals, hibernates when no updates are needed, and wakes up immediately when a repository is marked as needing an update, improving responsiveness and reducing unnecessary polling.

src/applications/repository/daemon · high confidence

Introduce strict type checking for Conduit API requests

The Conduit API now supports strict parameter type checking. A new \ConduitAPIRequest\ class has been added to handle request data, featuring a \isStrictlyTyped\ flag that enables validation logic. This change allows the API to enforce stricter data integrity on incoming parameters, moving away from loose typing for better reliability and security in API interactions.

src/applications/conduit/protocol · medium confidence

Introduce structured policy and policy type constants

The system now defines explicit constants for policy access levels (public, users, admin, no-one) and policy types (global, object, user, custom, project, masked) via new classes in the policy constants directory. This change provides a standardized way to reference and order policy types, including a helper to determine the most open policy allowed by the installation's configuration, laying the groundwork for more granular and flexible access control rules.

src/applications/policy/constants · high confidence

Introduce structured policy filtering and exception handling

This change introduces the \PhabricatorPolicyFilter\ and \PhabricatorPolicyFilterSet\ classes to centralize and optimize how the system checks user capabilities (such as CAN\_VIEW and CAN\_INTERACT) against objects. The new filter supports forced policies for validation, handles application visibility checks, and short-circuits checks for omnipotent viewers. It also introduces \PhabricatorPolicyException\ to provide structured, detailed error messages when policy checks fail, replacing generic exceptions with specific rejection reasons and context for the user.

src/applications/policy/filter · high confidence

Introduce structured setup issue reporting model

The system now uses a dedicated \PhabricatorSetupIssue\ object to represent configuration problems, replacing ad-hoc error handling with a structured model. This change allows setup checks to attach specific metadata to issues, such as related configuration keys (e.g., \mysql.host\, \mysql.pass\), original PHP configuration values (to display accurate limits like \memory\_limit\ before runtime alterations), and associated commands. It also introduces grouping capabilities for organizing issues and supports marking issues as fatal or ignorable, providing users with more precise and actionable feedback during the setup process.

src/applications/config/issue · high confidence

Introduce transactional editors and webhooks for Herald rules

Herald rules are now managed via a new transactional editor (HeraldRuleEditor) that supports generic Edge transactions, allowing rules to be disabled rather than deleted and enabling rule-driven rule changes. The editor includes serialization logic for rule components and sends email notifications with a direct link to the rule detail page. Additionally, a new webhook system is introduced, featuring an edit engine and editor for creating and managing webhook configurations (name, URI, status) with appropriate policy controls.

src/applications/herald/editor · high confidence

Introduces configurable audit rule options for Owners packages

A new constant class, PhabricatorOwnersAuditRule, has been added to define the available auditing behaviors for Owners packages. This change introduces five distinct audit modes—No Auditing, Audit Unreviewed Commits, Audit Commits With No Owner Involvement, Audit Unreviewed Commits and Commits With No Owner Involvement, and Audit All Commits—each with associated display names and icons. The implementation also handles mapping between legacy string values (such as empty strings or numeric flags) and the new standardized keys, ensuring backward compatibility while providing a more flexible and structured way to configure audit rules.

src/applications/owners/constants · high confidence

Introduces default policies and permissions for Harbormaster build plans

Users can now configure default view and edit policies for Harbormaster build plans, as well as control who has permission to create new plans. This change adds three new policy capabilities: 'Default Build Plan View Policy' (with public policy setting allowed), 'Default Build Plan Edit Policy', and 'Can Create Build Plans' (which provides a specific rejection message for unauthorized users).

src/applications/harbormaster/capability · high confidence

Introduces specific exception classes for Herald rule evaluation errors

The Herald engine now uses dedicated exception classes to distinguish between different types of rule evaluation failures. Users will see more granular error handling for invalid actions, invalid conditions, recursive conditions, and general rule evaluation errors, replacing the previous generic exception handling with specific types for better debugging and error reporting.

src/applications/herald/engine/exception · high confidence

Legalpad documents now use modular transaction types

Legalpad document changes are now tracked using a modular transaction system. This introduces specific transaction types for updating the document title, text, preamble, signature requirements, and signature type. Users will see detailed change logs for text and preamble edits, while changes to signature requirements are restricted to administrators.

src/applications/legalpad/xaction · high confidence

Macro edits now use modular transactions with expanded name support

Macro editing now relies on a new modular transaction system (PhabricatorMacroTransactionType) to handle changes, introducing specific transaction types for the macro name, file, audio, audio behavior, and disabled status. This change allows macro names to include emoji and other Unicode characters (while enforcing a minimum length and uniqueness), and provides structured, user-facing titles for feed updates when macros are renamed, have their image or audio changed, or are disabled and restored.

src/applications/macro/xaction · high confidence

Maniphest adopts modular application mail receivers and transaction-based reply handling

The Maniphest application now uses a new modular mail architecture: new classes (ManiphestCreateMailReceiver, ManiphestTaskMailReceiver, ManiphestReplyHandler) replace the previous hardcoded reply-handler logic. Creating a task via email now initializes a ManiphestTask and processes the message through a transaction-based reply handler that emits CREATE, title, description, and subscriber transactions, while existing task replies are routed through ManiphestTaskMailReceiver which loads the task by ID and delegates to the same reply handler. This change standardizes how Maniphest processes inbound email and stores changes as transactions, aligning it with the broader application-email framework.

src/applications/maniphest/mail · high confidence

Merchant management UI restructured with dedicated controllers

The Phortune merchant interface has been reorganized into a set of specialized controllers (e.g., \PhortuneMerchantDetailsController\, \PhortuneMerchantProvidersController\, \PhortuneMerchantManagersController\) that extend a new \PhortuneMerchantController\ base class. This change introduces a consistent side-navigation menu for merchant sections (Overview, Details, Payment Providers, Orders, Subscriptions, Managers) and enforces capability-based access control for editing versus viewing. Users will see a more structured merchant dashboard with distinct views for managing payment providers, viewing order history, and managing merchant managers, replacing the previous flatter or less organized interface.

src/applications/phortune/controller/merchant · high confidence

MetaMTA worker now handles permanent mail failures

The MetaMTA worker implementation has been updated to catch permanent mail delivery errors (PhabricatorMetaMTAPermanentFailureException) and convert them into permanent worker failures. This ensures that if a mail message cannot be delivered due to a permanent issue, the task is marked as permanently failed rather than retrying, and the failure is logged appropriately.

src/applications/metamta · high confidence

Migrate Differential editing to EditEngine and ApplicationTransactions

Differential revision and diff editing now uses the EditEngine framework and ApplicationTransactions instead of legacy controllers. This change introduces modular transaction types for creating and updating diffs, managing reviewers, and handling inline comments, while integrating Herald validation to block diff creation based on rules. The new editor supports draft revisions, custom fields like Test Plan and Summary, and provides a more consistent API for both web and CLI interactions.

src/applications/differential/editor · high confidence

Migrate Pholio to modular transaction framework

Pholio now uses the modular transaction framework for tracking changes to mocks and images. This introduces specific transaction types for updating mock names, descriptions, and status, as well as managing image details like names, descriptions, sequences, and file attachments (adding, removing, or replacing images). Users will see more granular and consistent change history entries in the activity feed for these operations.

src/applications/pholio/xaction · high confidence

Migrate Project settings to modular transactions

Project configuration changes (color, icon, name, image, status, workboard, slugs, parent/milestone, sort/filter defaults, and lock state) are now handled by dedicated modular transaction classes. This refactoring standardizes how these settings are applied and audited, ensuring consistent validation and rendering of change history for all project attributes.

src/applications/project/xaction · high confidence

Migrate project editing to modular transaction editors

Project editing operations (including workboard columns, triggers, and core project attributes) are now handled by new modular transaction editors (\PhabricatorProjectTransactionEditor\, \PhabricatorProjectColumnTransactionEditor\, \PhabricatorProjectTriggerEditor\) instead of the legacy \PhabricatorProjectEditor\. This change enforces stricter validation rules, such as preventing a project from being both a subproject and a milestone, and automatically inheriting membership for parent/milestone projects. It also standardizes how project changes are tracked, published to feeds, and communicated via email notifications.

src/applications/project/editor · high confidence

Migrate user management actions to modular transactions

The People application now uses a modular transaction system for user management, replacing previous state-based or session-based mechanisms. This change introduces specific transaction types for approving users (PhabricatorUserApproveTransaction), disabling/enabling users (PhabricatorUserDisableTransaction), promoting/demoting administrators (PhabricatorUserEmpowerTransaction), renaming usernames (PhabricatorUserUsernameTransaction), and sending test notifications (PhabricatorUserNotifyTransaction). Administrators can now disable users via a dedicated 'Can Disable Users' capability, and user renames allow case-only changes without conflict errors. Empowerment and username changes now require one-shot MFA verification. The system also hides sensitive actions like disabling and approving from the public feed, while ensuring proper email notifications are sent for approvals and renames.

src/applications/people/xaction · high confidence

Modernize Conduit API with new authentication workflow and method status tracking

The Conduit API application has been refactored to support a modern client handshake and improved method management. Users can now authenticate via a new \conduit.connect\ method that supports token-based signatures and session establishment, replacing older connection patterns. The \conduit.getcapabilities\ method allows clients to discover supported authentication protocols (token, asymmetric, session, sessionless, and OAuth) and wire formats. Additionally, the \conduit.query\ method now returns structured metadata including parameter definitions, return types, and descriptions for all available API methods. The base \ConduitAPIMethod\ class introduces a status system (stable, unstable, deprecated, frozen) to help users identify which API methods are production-ready versus those that are subject to change or removal.

src/applications/conduit/method · high confidence

Modernize Diffusion browse and blame views with new UI components

The Diffusion browse and blame views have been modernized to use the new PHUI component library (PHUIHeaderView, PHUIObjectBoxView, PHUIPagerView) and the DocumentEngine rendering system. This change updates the visual presentation of file browsing, directory listings, and blame annotations to be more consistent with the rest of the application, while also improving mobile responsiveness and performance through AJAX-loaded branch/tag information and batched queries.

src/applications/diffusion/controller · high confidence

Modernize Drydock lease and resource status handling

Drydock now uses dedicated status classes (DrydockLeaseStatus and DrydockResourceStatus) that extend PhabricatorObjectStatus, replacing the previous constant-based approach. This change introduces a more structured status lifecycle for both leases and resources, including specific states like 'pending', 'acquired', 'active', 'released', 'broken', and 'destroyed'. Each status is now associated with metadata such as display names, icons, colors, and behavioral flags (e.g., whether a status is releasable, commandable, or activating), enabling more consistent and modern UI treatment and logic enforcement across Drydock components.

src/applications/drydock/constants · high confidence

Modernize Herald rule management and introduce webhooks

The Herald application's user interface and navigation have been modernized, replacing the legacy side navigation with a new filter-based menu and updating rule views to use the PHUI (Phabricator UI) component library. Users can now manage rules with a clearer workflow, including the ability to disable rules without deleting them. Additionally, a new Webhooks section has been added to the Herald utilities, allowing administrators to configure, test, and monitor outbound webhook requests, including HMAC key management and error backoff status.

src/applications/herald/controller · high confidence

Modernize Maniphest task edge types with inverse transactions

The Maniphest application now uses modern \PhabricatorEdgeType\ subclasses for task relationships, including parent/subtask, commit, revision, mock, and duplicate/merged-in links. These new edge types automatically write inverse transactions, ensuring that relationships are consistently maintained in both directions (e.g., linking a task to its parent also links the parent to the task). This improves data integrity and simplifies how task relationships are managed and queried within the system.

src/applications/maniphest/edge · high confidence

Modernize commit audit actions and status tracking

This change introduces a new, modular transaction system for Diffusion commit audits, replacing older status checks with specific action types. Users can now explicitly Accept, Raise Concern, Resign as an Auditor, or Request Verification for commits, with each action governed by strict permission and state validations (e.g., authors cannot accept or raise concerns on their own commits, and auditors cannot resign if they are not active). The system also adds a "Needs Verification" state to handle the workflow after concerns are raised, and modernizes how auditors are added or removed from commits. Additionally, buildable status transactions are updated to correctly reflect Harbormaster build outcomes in the commit history.

src/applications/diffusion/xaction · high confidence

Modernize global search typeahead with composite datasource and document type support

The global search typeahead now uses a new composite datasource that aggregates results from all quick-search sources, rendering them with a consistent browse style. Additionally, a dedicated datasource for document types has been introduced, which displays available document types in the autocomplete dropdown along with their associated application names, improving discoverability and context for users filtering by document type.

src/applications/search/typeahead · high confidence

Modernize project edge types to use PhabricatorEdgeType

Project edge types (member, object, and materialized membership) now extend the base \PhabricatorEdgeType\ class, standardizing how project relationships are handled internally. This change updates the underlying edge definitions for project membership and object associations, ensuring consistent behavior for adding, removing, and editing project members and associated objects.

src/applications/project/edge · high confidence

Modernize settings architecture with transactional updates and timezone conflict resolution

The Settings application has been refactored to use a transactional model for applying user preferences, replacing direct edits with explicit transactions via the new PhabricatorSettingsAdjustController. This change introduces a new PhabricatorSettingsTimezoneController that detects discrepancies between the user's browser timezone and their profile setting, prompting them to reconcile the conflict or ignore it. Additionally, the system now raises an 'Account Setup Issue' for users with unverified primary email addresses, surfaced via the new PhabricatorSettingsIssueController, and administrators can now configure global default settings through the updated PhabricatorSettingsListController.

src/applications/settings/controller · high confidence

Modernize user API methods and deprecate legacy endpoints

The Conduit API for user management has been refactored to introduce modern, flexible methods while deprecating older ones. A new 'user.search' method is available for querying users, and 'user.edit' now handles user modifications, replacing the previously separate 'user.enable' and 'user.disable' methods which are now marked as deprecated. The legacy 'user.query' method is marked as frozen, and 'user.find' is deprecated in favor of 'user.query'. Additionally, the 'user.whoami' method now returns the user's primary email if it is verified, and user information dictionaries include an 'availability' status instead of the previous 'status' field.

src/applications/people/conduit · high confidence

Modernized Herald rule and webhook request displays

The Herald application now uses updated UI components to present rule lists and webhook request logs. The rule list view displays personal, object, and global rules with icons, author information, and disabled status indicators, while the webhook request list view presents a table of recent requests showing status icons, associated objects, error types, and timestamps.

src/applications/herald/view · high confidence

Modernized Macro editing with EditEngine and transactional updates

The Macro application now uses a new EditEngine-based workflow for creating and editing macros, replacing the previous implementation. This change introduces a dedicated editor class that handles object creation, field configuration (including name and image file uploads), and policy enforcement. It also implements modular transaction handling for macro updates, ensuring that changes are recorded as discrete transactions. Additionally, email notifications for macro edits have been updated to include a direct link to the macro detail page, improving user visibility into the modified content.

src/applications/macro/editor · high confidence

Modernized Maniphest controller architecture and task graph visualization

The Maniphest application controllers have been refactored to use a new base \ManiphestController\ and the \ManiphestEditEngine\, replacing legacy edit workflows. This change introduces a dedicated \ManiphestTaskGraphController\ that provides a standalone view for task dependency graphs, including overflow handling for large graphs. Additionally, a new \ManiphestBulkEditController\ allows bulk editing of tasks, specifically supporting workboard contexts, while the task list and detail views now delegate to the \ManiphestTaskSearchEngine\ and \ManiphestEditEngine\ for consistent behavior.

src/applications/maniphest/controller · high confidence

Modernized file upload and search APIs with chunked upload support

The Conduit API for file operations has been restructured to support resumable, chunked uploads for large files and to provide a more structured search interface. A new 'file.allocate' method prepares uploads, enabling clients to resume interrupted JavaScript-based chunked transfers by identifying partial files. The legacy 'file.uploadhash' method is now deprecated in favor of this new allocation flow. Additionally, a new 'file.search' method replaces the older 'file.info' endpoint for querying file metadata, while 'file.uploadchunk' and 'file.querychunks' handle the granular transfer and status of file parts.

src/applications/files/conduit · high confidence

Modular transaction system for Maniphest tasks

Maniphest task changes (status, priority, title, description, owner, points, cover image, attachments, merging, and subtask blocking) are now handled by a new modular transaction architecture. This provides consistent, human-readable activity feed stories, richer change details (such as text diffs for descriptions), and improved validation—for example, preventing accidental removal of task titles during bulk edits and ensuring cover images are valid, transformable images. The system also tracks who closed a task and when, and allows closing a subtask to automatically update its parent without requiring special permissions on the parent.

src/applications/maniphest/xaction · high confidence

Modular transaction types for badge management

The Badges application now uses a modular transaction system for managing badge changes. This introduces specific transaction types for awarding and revoking badges, as well as updating badge metadata such as name, description, icon, flavor, quality, and status. These changes enable detailed change history and feed updates for badge operations.

src/applications/badges/xaction · high confidence

Modularize Almanac transaction handling for devices, interfaces, bindings, and services

The Almanac application now uses a modular transaction system to manage changes to devices, interfaces, bindings, and services. This change introduces specific transaction types for each entity, allowing users to update properties, rename items, change statuses, and modify relationships (such as binding a service to an interface or attaching an interface to a device) through a consistent, auditable history. Key behaviors include enforcing unique names for networks, namespaces, devices, and services; validating that interfaces have required addresses, ports, and network associations; and preventing the deletion of interfaces that are currently in use by services. Additionally, changing a binding's interface now automatically recalculates the cluster binding status for the associated device.

src/applications/almanac/xaction · high confidence

Modularize Config Application with dedicated status modules

The Config application's status display has been restructured into a modular system using a new \PhabricatorConfigModule\ base class and specific sub-modules. This change introduces dedicated configuration views for Garbage Collectors (showing retention policies), Edge Types, HTTP Parameter Types, PHID Types (displaying associated applications and icons), Exception Handlers, Setup Checks (distinguishing preflight checks), and Sites. Users will now see these distinct categories organized in the Config interface, with specific details like custom retention policies highlighted and application icons linked to PHID types.

src/applications/config/module · high confidence

Modularize Differential email handling with dedicated mail views and receivers

Differential's email processing has been refactored to use a modular architecture. New mail receiver classes (DifferentialCreateMailReceiver, DifferentialRevisionMailReceiver) handle incoming emails for creating diffs and replying to revisions, while dedicated mail view classes (DifferentialChangeDetailMailView, DifferentialInlineCommentMailView, DifferentialMailView) manage the rendering of change details and inline comments in both HTML and plaintext formats. This separation improves code organization and allows for more flexible email configuration and rendering.

src/applications/differential/mail · high confidence

Modularize Drydock Blueprint transactions

The Drydock application now uses a modular transaction system for managing blueprint changes. This introduces specific transaction types for disabling/enabling blueprints, renaming them (with validation for required names and length limits), and setting the blueprint type (restricted to creation time). These changes allow for more granular control and clearer audit trails when editing Drydock blueprints.

src/applications/drydock/xaction · high confidence

Modularize Harbormaster build control commands into dedicated transaction classes

Harbormaster build control commands (pause, resume, restart, abort) are now implemented as distinct, modular transaction classes (e.g., HarbormasterBuildMessagePauseTransaction) rather than a monolithic structure. This change introduces specific validation logic for each command—such as preventing pause/resume on autobuilds, enforcing build plan edit permissions for sending commands, and handling state transitions like discarding progress on abort or restarting. Users benefit from clearer confirmation prompts and more precise error messages when issuing these control commands, as each action now has its own dedicated handler with tailored safety checks.

src/applications/harbormaster/xaction/build · high confidence

Modularize Herald field value rendering

Herald field values are now handled by dedicated, modular classes (e.g., HeraldBoolFieldValue, HeraldSelectFieldValue, HeraldTokenizerFieldValue) that extend a common base. This change standardizes how different field types are rendered in transcripts, editors, and rule configurations, ensuring consistent display logic for booleans, text, select options, and tokenizer-based fields.

src/applications/herald/value · high confidence

Modularize Herald rule and webhook transaction types

This change refactors the Herald application by introducing specific transaction classes for managing Herald rules and webhooks. For rules, it adds dedicated transactions to handle editing rule configuration (conditions, actions, match policy), renaming, and enabling/disabling, ensuring proper validation and change-detail views. For webhooks, it adds transactions to manage the name, URI (with validation for valid HTTP/HTTPS URIs), and status, providing clear user-facing titles for these changes. This modularization separates concerns and improves the consistency of how these objects are modified and tracked in the system.

src/applications/herald/xaction · high confidence

Modularize Maniphest task relationships and merge operations

The task relationship system in Maniphest has been refactored into a modular architecture, replacing the previous monolithic implementation with distinct, reusable relationship classes for specific interactions. This change introduces dedicated handlers for closing tasks as duplicates, merging duplicates, and editing parent/subtask hierarchies, as well as linking to commits, revisions, and mocks. For users, this means the 'Edit Blocking Tasks' interface is now split into separate 'Edit Parent Tasks' and 'Edit Subtasks' options, providing clearer distinction between dependency directions. Additionally, the 'Close as Duplicate' action is now restricted to selecting only a single target task, and the underlying merge logic ensures that subscribers from merged tasks are correctly preserved in the surviving task.

src/applications/maniphest/relationship · high confidence

Modularize commit message parsing into dedicated workers

The commit message parsing logic has been extracted from the general commit parser into a dedicated \PhabricatorRepositoryCommitMessageParserWorker\ base class, with specific subclasses for Git, Mercurial, and SVN. This change separates the concerns of parsing commit metadata (author, committer, message) from processing file changes, ensuring that identity resolution and message import are handled in a distinct step before the follow-up change parsing tasks are queued.

src/applications/repository/worker/commitmessageparser · high confidence

Modularize complex HTTP parameter types

The HTTP parameter parsing system has been refactored to use a modular class hierarchy, introducing specific types for booleans, integers, strings, JSON, dates (epoch), files, PHIDs, and lists of users, projects, or strings. This change standardizes how complex values are extracted from requests, providing consistent handling for formats like comma-separated lists, array inputs, and file uploads, which improves reliability and clarity for form and API parameter processing.

src/aphront/httpparametertype · high confidence

Modularize dashboard transaction handling

The dashboard application now uses a modular transaction system to manage changes to dashboard properties. This introduces specific transaction types for updating the dashboard name, icon, status (active/archived), layout mode, and panel configuration. Users will see more granular and descriptive change logs for these actions, and the system now validates inputs such as name length, valid layout modes, and panel specifications before applying changes.

src/applications/dashboard/xaction/dashboard · high confidence

Modularize fulltext indexing with separate engine and extension phases

The search indexing system has been refactored to separate the indexing process into distinct phases and extensible components. New classes \PhabricatorFulltextEngine\ and \PhabricatorIndexEngine\ manage the core indexing logic, while \PhabricatorFulltextEngineExtension\ and \PhabricatorIndexEngineExtension\ allow specific object types to define how they are indexed. The fulltext engine now supports 'enrich' and 'index' phases, allowing extensions to add data before the final indexing step. Additionally, the index engine tracks versioning for each extension, enabling it to skip re-indexing objects that have not changed since the last index, improving performance. A new \PhabricatorSearchAbstractDocument\ class standardizes the structure of indexed documents, including fields, relationships, and metadata like PHID and document type.

src/applications/search/index · high confidence

Modularize mail command handling with a base class and auto-discovery

The mail command system in the MetaMTA application has been refactored to use a modular architecture. A new abstract base class, MetaMTAEmailTransactionCommand, defines the interface for individual commands and provides methods for documentation generation (summaries, syntax, descriptions). Command discovery is now automated using PhutilClassMapQuery, which scans for all subclasses of this base class to build a command map, ensuring unique keyword associations. This change allows new email commands to be added simply by creating a new subclass, and enables the automatic generation of command documentation from the active command set.

src/applications/metamta/command · high confidence

Modularize main menu and password destruction logic

The authentication application now uses dedicated extension classes to manage its integration points. A new PhabricatorAuthMainMenuBarExtension handles the display of the 'Log In' button in the main navigation bar for unauthenticated users, ensuring it links correctly to the primary site. Additionally, a PhabricatorPasswordDestructionEngineExtension ensures that user passwords are properly destroyed when a user account is deleted, maintaining data consistency during account removal.

src/applications/auth/extension · high confidence

Modularize settings into distinct panel groups

The settings interface has been reorganized into distinct, modular panel groups (Account, Applications, Authentication, Developer, Email, and Sessions and Logs). This change structures the settings UI by categorizing options into these specific sections, each with a defined display order, rather than presenting a flat list of settings.

src/applications/settings/panelgroup · high confidence

Modularize user activity log message types

The user activity log system has been refactored to use a modular, class-based structure for log entries. A new abstract base class, PhabricatorUserLogType, now defines the interface for log types, and specific actions (such as login, logout, email changes, and multi-factor authentication events) are represented by distinct subclasses. This change organizes the log message definitions, making it easier to identify and manage individual activity types in the user log.

src/applications/people/userlog · high confidence

Modularize workboard column transactions and add trigger support

Workboard column configuration is now handled through distinct, modular transaction types for name, status, point limit, and triggers, replacing the previous monolithic approach. Users can now attach and remove triggers from columns, with the system automatically updating search indexes to reflect trigger usage changes. The column name transaction now correctly exempts default and proxy columns from the requirement to have a custom name, preventing unnecessary warnings during edits. Additionally, a new point limit transaction allows users to set or remove integer-based point limits for columns, with validation ensuring only non-negative integers are accepted.

src/applications/project/xaction/column · high confidence

Modularized Paste transaction types

Paste actions (content, language, status, title) are now handled by dedicated, modular transaction classes that extend a new base type, improving how changes are tracked and displayed in feeds and change detail views.

src/applications/paste/xaction · high confidence

Modularized cache purging with dedicated purger classes

The cache purging mechanism has been refactored into a modular system where specific cache types are handled by dedicated purger classes extending a common base. This change introduces specific purgers for builtin files, changesets, general markup, remarkup, and user caches, allowing for targeted cache invalidation rather than a single monolithic operation. Users can now rely on more granular control over which cache tables are truncated or destroyed, improving maintenance and clarity for cache management tasks.

src/applications/cache/purger · high confidence

Modularized configuration option types

Configuration options are now handled by a new modular type system in src/applications/config/type, replacing the previous monolithic approach. This change introduces dedicated classes for each config type—including bool, class, enum, int, JSON, regex list, set, string, and string list—each providing specific validation, canonical value conversion, and UI control generation. Users benefit from stricter validation (e.g., ensuring 'bool' values are strictly 'true'/'false', 'int' values are integers, and 'class' values are valid subclasses) and more consistent handling of list and set inputs across web forms and command-line interfaces.

src/applications/config/type · high confidence

Modularized daemon garbage collection into specific collectors

The daemon garbage collection logic has been refactored into distinct, modular collector classes for better maintainability and targeted cleanup. This change introduces specific garbage collectors for archived tasks (retained for 14 days), daemon log events (retained for 7 days), and daemon logs (retained for 7 days, now based on modification date rather than creation date). Additionally, a new collector for daemon lock logs has been added, which deletes entries older than the configured retention period (defaulting to 0, effectively immediate cleanup). These changes ensure that different types of daemon-related data are cleaned up according to their specific relevance and retention policies.

src/applications/cache/garbagecollector, src/applications/daemon/garbagecollector · high confidence

Modularized exception handling with dedicated MFA and policy dialogs

Exception handling in Aphront has been refactored into a modular system of specific handlers, replacing the previous monolithic approach. This change introduces dedicated handlers for different error types: high-security (MFA) exceptions now trigger a structured dialog that distinguishes between session upgrades and one-time challenges; policy exceptions display a clear access-denied dialog with capability details; rate-limiting errors show a 'Slow Down!' message; and AJAX/Conduit requests receive structured error responses instead of generic pages. This results in more consistent, user-friendly error messaging and better separation of concerns for security and permission-related interactions.

src/aphront/handler · high confidence

Modularized repository transaction handling

Repository configuration changes are now managed through a modular transaction system, replacing the previous monolithic approach. This change introduces specific transaction types for individual repository settings—including activation, callsign, default branch, description, encoding, filesize limits, copy time limits, touch limits, maintenance mode, push policy, VCS type, storage service, staging URI, symbol sources/languages, SVN subpath, and identity assignment. It also adds support for automation blueprints, fetch rules, permanent refs, and track-only branch rules, ensuring that each change is validated and recorded with a clear, user-facing title in the repository history.

src/applications/repository/xaction · high confidence

Modularized site routing and relaxed HTTPS for intracluster traffic

The site routing system has been refactored into a modular architecture using new classes (AphrontSite, AphrontRoutingMap) to handle requests for the core platform, static resources, and shortened URLs separately. This change allows for more flexible routing, including the ability for custom sites to define their own 404 controllers. Additionally, the system now permits HTTP traffic for intracluster requests even if the global 'security.require-https' setting is enabled, accommodating common load balancer configurations where SSL is terminated externally.

src/aphront/site · high confidence

New Celerity resource controllers with expanded format support and CORS fixes

The Celerity static resource serving system has been refactored into a new base controller (CelerityResourceController) and a specific implementation (CelerityPhabricatorResourceController) to handle /res/ requests. This change expands supported resource types to include .ico, .woff2, .eot, and .mp3 files. It also fixes cross-origin font loading issues in IE and Firefox by adding an 'Access-Control-Allow-Origin: \*' header for WOFF/WOFF2/EOT resources, and enables HTTP Range header support for static resource requests.

src/applications/celerity/controller · high confidence

New Diffusion-specific exception classes introduced

The Diffusion application now includes several new exception classes to handle specific error scenarios more precisely. Users will see tailored exceptions for commit hook rejections (DiffusionCommitHookRejectException), daemon lock failures (DiffusionDaemonLockException), Mercurial flag injection attempts (DiffusionMercurialFlagInjectionException), and setup issues (DiffusionSetupException). Additionally, a new DiffusionRefNotFoundException class has been added, which allows capturing and exposing the specific reference that failed to resolve, improving debugging and error reporting for repository operations.

src/applications/diffusion/exception · high confidence

New Drydock exception classes for resource and command errors

The Drydock application now includes specific exception classes to handle distinct failure scenarios: DrydockAcquiredBrokenResourceException for when a leased resource fails to activate, DrydockResourceLockException and DrydockSlotLockException for lock acquisition failures (with the latter providing details on which locks are held), and DrydockCommandError to capture command execution details like stdout, stderr, and phase. These changes improve error reporting and handling for resource lifecycle and command execution issues.

src/applications/drydock/exception · high confidence

New HTTP response sink architecture with streaming and security hardening

The HTTP response layer has been refactored into a new sink abstraction (AphrontHTTPSink) with concrete implementations for PHP (AphrontPHPHTTPSink) and isolated testing (AphrontIsolatedHTTPSink). This change introduces support for streaming large file responses by removing execution time limits and processing data in chunks, while explicitly avoiding flush() calls to prevent HTTPS issues under Apache. Security is enhanced by adding validation against HTTP response splitting attacks in header names and values, and by automatically merging Content Security Policy URIs from static resources into all responses.

src/aphront/sink · high confidence

New PhabricatorFeedBuilder with resilient story rendering and hovercard support

The feed builder now uses a dedicated PhabricatorFeedBuilder class that allows enabling or disabling hovercards on feed stories and customizing the empty-state message. A key behavioral improvement is that individual story rendering failures no longer crash the entire feed; instead, the builder catches exceptions per story and displays a fallback error view for that specific item, ensuring the rest of the feed remains visible.

src/applications/feed/builder · high confidence

New and updated Differential Conduit API methods

The Conduit API surface for Differential has been expanded and reorganized. New search endpoints have been added for revisions, diffs, and changesets (differential.revision.search, differential.diff.search, and differential.changeset.search), providing more flexible querying capabilities. The existing differential.query and differential.querydiffs methods are now marked as frozen, directing users toward the new search APIs. Additionally, several methods have been updated or introduced: differential.revision.edit is now available for creating and updating revisions via the EditEngine; differential.creatediff now truncates overly long source paths to prevent errors; differential.createrawdiff allows setting a custom view policy during diff creation; and differential.createinline now correctly accepts JSON false for the isNewFile parameter. Legacy methods like differential.getrevision and differential.getalldiffs are deprecated in favor of the new search endpoints.

src/applications/differential/conduit, src/applications/project/conduit · high confidence

This change introduces three new constant classes in the authentication module to standardize and enhance security behaviors. PhabricatorAuthFactorProviderStatus defines active, deprecated, and disabled states for multi-factor authentication providers, allowing administrators to control provider availability. PhabricatorCommonPasswords adds a blacklist check against common and application-specific weak passwords to mitigate brute-force attacks. PhabricatorCookies consolidates session management by defining specific cookie names (such as phcid, phreg, and next\_uri) and implementing logic to prevent the 'next\_uri' redirect cookie from being overwritten by background resource requests within a short timeframe.

src/applications/auth/constants · high confidence

New centralized configuration for Differential code review

A new configuration file (PhabricatorDifferentialConfigOptions.php) introduces a centralized, programmatic interface for managing Differential settings. This change allows administrators to control specific behaviors such as requiring or making the 'Test Plan' field optional, enabling email-based acceptance actions, treating generated files as hidden via regex patterns, and adjusting how 'Accepted' status persists across updates. It also exposes granular permissions, allowing any user to close or abandon accepted revisions and permitting self-acceptance, while providing a structured way to select and reorder revision fields.

src/applications/differential/config · high confidence

New exception class for configuration validation errors

A new \PhabricatorConfigValidationException\ class has been introduced to handle errors specifically related to configuration validation. This allows the system to explicitly validate configuration settings, including complex attributes, and throw a distinct exception type when validation fails, improving error handling clarity for users.

src/applications/config/exception · high confidence

New exception classes for build abortion, failure, and structured messages

The Harbormaster application now includes three new exception classes: HarbormasterBuildAbortedException, HarbormasterBuildFailureException, and HarbormasterMessageException. The first two are simple exception types likely used to signal specific build states (abortion or failure). The third, HarbormasterMessageException, is a more complex exception that allows attaching a title and a body (array of paragraphs) to the error, enabling richer error reporting for build steps. This supports the ability for build steps to explicitly fail the build with detailed messages.

src/applications/harbormaster/exception · high confidence

New exception classes for permanent mail failures and received mail processing errors

The MetaMTA application now introduces two new exception classes to improve error handling for email operations. PhabricatorMetaMTAPermanentFailureException allows adapters to signal that a mail is permanently undeliverable, enabling better distinction between transient and permanent delivery failures. PhabricatorMetaMTAReceivedMailProcessingException provides structured error reporting for received mail processing issues, including a status code accessor for more detailed diagnostics.

src/applications/metamta/exception · high confidence

New exception types for transaction validation and effects

The system now introduces specific exception classes to handle transaction lifecycle issues more precisely. Users will see clearer error messages when transactions fail validation (PhabricatorApplicationTransactionValidationException), when a transaction is poorly constructed (PhabricatorApplicationTransactionStructureException), or when submitted transactions have no effect (PhabricatorApplicationTransactionNoEffectException). Additionally, a warning exception (PhabricatorApplicationTransactionWarningException) is available for non-fatal transaction issues.

src/applications/transactions/exception · high confidence

New granular permissions for browsing, creating, and disabling users

The People application now enforces distinct policy capabilities for user management actions. Administrators can now control who is allowed to browse the user directory (people.browse), create new non-bot users (people.create.users), and disable or enable existing users (people.disable.users). These changes allow for more precise access control within the People application, separating these privileges rather than relying on broader permissions.

src/applications/people/capability · high confidence

New handle rendering views for improved list and tag display

This change introduces three new view classes in the PHID application to standardize and optimize how object handles are rendered. PHUIHandleView provides a flexible way to render a single handle as a link, text, or tag, with support for hovercards and glyph limits. PHUIHandleListView simplifies rendering a list of handles, improving loading and caching by delaying bulk loads, and supports inline or block display. PHUIHandleTagListView renders handles as a styled tag list (ul/li), supporting annotations, slim styling, hovercards, and a limit with a tooltip for overflow. These views replace older rendering patterns, offering a more consistent and performant user experience for displaying object references across the application.

src/applications/phid/view · high confidence

New hierarchical settings interface with core, advanced, and history views

The configuration settings area now uses a full-width, hierarchical layout organized into distinct sections. Users can browse settings via a new navigation sidebar that separates Core Settings, Advanced Settings, and All Settings, with locked options visually marked as advanced. A dedicated Settings History page displays a timeline of configuration changes, and the edit interface provides clearer status indicators (Hidden, Locked, Editable, Default) and validation feedback for individual configuration entries.

src/applications/config/controller/settings · high confidence

New modular CLI for managing configuration values

The \bin/config\ command has been refactored into a modular system with dedicated subcommands for managing configuration. Administrators can now use \bin/config get\ to view values from both local and database sources (including error handling if the database is unavailable), \bin/config set\ to update values with support for reading complex JSON from stdin and targeting database storage via the \--database\ flag, \bin/config delete\ to remove keys from either storage backend, \bin/config list\ to display all available configuration keys, \bin/config migrate\ to move file-based settings to the new storage system, and \bin/config done\ to mark manual upgrade activities as complete. This change introduces a more robust and flexible interface for configuration management, including validation for complex types and explicit handling of locked or hidden options.

src/applications/config/management · high confidence

New modular setup checks for authentication, base URI, and binaries

The setup check system has been refactored into distinct, modular classes to provide more specific and actionable guidance during installation and configuration. Administrators will now see dedicated checks for authentication provider configuration (including warnings for unlocked auth settings), base URI validation (checking for valid Host headers), and binary availability (verifying required tools like git, svn, and hg). These new checks replace broader, monolithic checks, offering clearer error messages and specific remediation commands for common setup issues.

src/applications/config/check · high confidence

New password validation interface and exception handling

The authentication system now includes a new \PhabricatorAuthPasswordException\ class to handle password-related errors and a \PhabricatorAuthPasswordHashInterface\ that allows password hash implementations to define a blocklist of identifiers (such as usernames) that passwords should not resemble, enhancing security by preventing trivially similar password choices.

src/applications/auth/password · high confidence

New policy locking configuration and stricter public visibility warnings

Administrators can now lock specific application policies (such as user creation) to prevent further editing via the new \policy.locked\ config option, which validates capabilities and policies against the system. Additionally, the description for the \policy.allow-public\ setting has been updated to explicitly warn that enabling it allows anyone on the internet to view objects and access features like the user directory without logging in.

src/applications/policy/config · high confidence

New project membership locking and default policy capabilities

This change introduces new policy capabilities for projects, including the ability to lock project membership (preventing members from leaving) and default policies for viewing, editing, and joining projects. Users can now configure these default policies, with the view policy allowing public settings by default.

src/applications/project/capability · high confidence

New query engine and filters for the Applications list

The Applications list now uses a dedicated search engine (PhabricatorAppSearchEngine) backed by PhabricatorApplicationQuery, allowing users to filter applications by name, installation status, prototype status, provenance (first-party vs. third-party), launchability, and email support. The engine also supports built-in queries for the launcher (showing installed, launchable apps) and all applications, and handles legacy 'beta' parameter names by migrating them to 'prototypes'.

src/applications/meta/query · high confidence

New repository commit import and publishing workers

This change introduces a new pipeline for processing repository commits, splitting the work into distinct parsing and publishing stages. The new \PhabricatorRepositoryCommitParserWorker\ handles the initial ingestion of commits, including legacy task compatibility and checks for unreachable commits. The \PhabricatorRepositoryCommitPublishWorker\ manages the finalization of imports, applying transactions, closing associated revisions and tasks, and handling owner audits. Additionally, \PhabricatorRepositoryPushMailWorker\ now sends push notifications using the recipient's translation locale and formats mail bodies with link sections, while \PhabricatorRepositoryIdentityChangeWorker\ updates repository identities in response to user or email address changes.

src/applications/repository/worker · high confidence

New response classes for transaction previews, warnings, and validation

This change introduces four new response classes in the transaction application to handle specific user-facing outcomes when editing or previewing transactions. PhabricatorApplicationTransactionResponse now renders transaction changes via AJAX, supporting inline comment previews with aural section headers and passing timeline view data to the UI. PhabricatorApplicationTransactionWarningResponse displays a dialog listing grouped warnings for transactions, allowing users to confirm or cancel actions. PhabricatorApplicationTransactionValidationResponse shows a dialog with validation error messages when input is invalid. PhabricatorApplicationTransactionNoEffectResponse handles cases where actions have no effect, prompting the user to apply remaining actions or post a comment anyway.

src/applications/transactions/response · high confidence

New search and query infrastructure for Macros

Users can now filter and search for Macros using specific criteria including status (active, disabled, or any), author, name, creation date range, and flag color. The system introduces a new search engine that supports saved queries for 'Active', 'All', and 'Authored' macros, and allows filtering by whether a macro is marked with any flag or a specific flag color. This change replaces previous global or less granular search mechanisms with a policy-aware, cursor-paged query system that integrates with the application's search panels.

src/applications/macro/query · high confidence

New search field and relationship constants for Ferret engine

The search application now defines explicit constants for document field types and relationship statuses to support the Ferret search engine. A new \PhabricatorSearchDocumentFieldType\ class introduces a 'core' field type, designed to index title and body content together, alongside existing fields for title, body, and comments. Additionally, \PhabricatorSearchRelationship\ constants now explicitly define 'Closed' and 'Unowned' relationship states, enabling the search index to handle these specific relationship types directly.

src/applications/search/constants · high confidence

New search result view components with improved query highlighting

The search interface now uses dedicated view classes (PhabricatorApplicationSearchResultView and PhabricatorSearchResultView) to render results. This change introduces robust query highlighting that bolds matching terms in result titles, correctly handling CJK characters, substring matches, and exact-match operators while ensuring the output is HTML-safe. Additionally, search results now visually indicate when an object is closed by disabling the item and adding a 'Closed' attribute.

src/applications/search/view · high confidence

New status constants for Ponder questions and answers

The Ponder application now defines explicit constants for question and answer statuses. Questions can be Open, Closed (Resolved, Obsolete, or Invalid), and answers can be Visible or Hidden. These constants provide the labels, descriptions, UI tag colors, and icons used to display the state of questions and answers to users.

src/applications/ponder/constants · high confidence

New system interfaces for destruction and unlocking capabilities

This change introduces three new interfaces in the system layer to support advanced object lifecycle management. PhabricatorDestructibleInterface defines the contract for objects that can be permanently destroyed via a destruction engine, while PhabricatorDestructibleCodexInterface provides a factory method for creating destructible codex instances. Additionally, PhabricatorUnlockableInterface establishes the mechanism for objects to specify custom policy unlocking behavior, enabling tasks and other entities to be unlocked by their owners.

src/applications/system/interface · high confidence

New transaction-based repository editor with unique name enforcement

The repository editing interface has been replaced with a new transaction-based editor (PhabricatorRepositoryEditor) that manages changes via specific transaction types (edge, view policy, edit policy). This change enforces unique callsigns and short names for repositories, preventing duplicate key errors during creation or modification. Additionally, the editor automatically assigns a local path based on the repository's ID if none is provided, sets the repository to hosted by default upon creation, and synchronizes the working copy immediately after creation.

src/applications/repository/editor · high confidence

Notifications are now queryable via ApplicationSearch with visibility filtering

Users can now search and filter notifications using the standard ApplicationSearch interface, including a dedicated 'Unread Notifications' view. The new \PhabricatorNotificationQuery\ ensures that users only see notifications for objects they currently have permission to view, preventing 'phantom' notifications for deleted or restricted items. The system also supports cursor-based pagination for reliable paging through large notification lists.

src/applications/notification/query · high confidence

Notify users when mail processing fails

A new error handling mechanism has been introduced for the MetaMTA application. When the system fails to process an email, it now triggers a specific action (PhabricatorMetaMTAErrorMailAction) configured to send an error notification to the user. This ensures that users are informed of delivery issues rather than experiencing silent failures.

src/applications/metamta/action · high confidence

OAuth client management now supports disabling applications and requires high-security authentication to view secrets

The OAuth Server client controllers have been refactored to introduce new capabilities for managing OAuth applications. Administrators can now disable an OAuth application instead of destroying it, preventing users from authenticating against it while preserving the record; the application view page displays a status indicator for enabled/disabled states. Additionally, viewing the application's client secret is now gated behind a high-security session requirement, ensuring that sensitive credentials are only revealed after explicit user confirmation and re-authentication. The client list and edit interfaces have also been updated to use the modern SearchEngine and EditEngine components for a consistent user experience.

src/applications/oauthserver/controller/client · high confidence

OAuth server authorization and token endpoints now enforce visibility policies and support trusted clients

The OAuth server controllers now require users to have visibility into an OAuth application before they can authorize it, using the application's visibility policy to restrict access. Additionally, trusted clients can now be automatically redirected after authorization without requiring an explicit confirmation step, while untrusted clients must still confirm the login. The token endpoint also validates that the client ID provided in the request matches the one in the Authorization header if both are present, and ensures the redirect URI in the token request exactly matches the one stored in the authorization code.

src/applications/oauthserver/controller · high confidence

OAuth server storage schema and client lifecycle model

The OAuth server now persists client authorizations, access tokens, and authorization codes in dedicated database tables, and supports disabling OAuth clients instead of permanently destroying them. Client deletion now cascades to remove all associated authorizations, tokens, and codes, while disabled clients remain in the system with their history intact. Transactional audit trails are added for client name changes, redirect URI updates, and enable/disable state changes.

src/applications/oauthserver/storage · high confidence

Owners application configuration and routing

The Owners application is now configured with a dedicated application class that defines its base URI (/owners/), icon, and group classification. This change introduces specific routes for listing, editing, viewing details, archiving, and managing paths of ownership packages, while also establishing default view and edit policies for newly created packages.

src/applications/owners/application · high confidence

Owners package settings are now managed via modular transaction types

The Owners application now uses a modular transaction system to handle changes to package configuration. This change introduces specific transaction types for managing package auditing rules, authority, autoreview, description, dominion, ignored paths, name, owners, paths, and status. This modularization allows for more consistent validation, clearer change history titles, and better support for mail diff sections when package settings are updated.

src/applications/owners/xaction · high confidence

Owners packages are now editable via a unified EditEngine interface

Users can now create and configure Owners packages through a standardized form-based interface that supports editing package names, owners, dominion and authority rules, auto-review settings, auditing states, descriptions, and status (including archiving). The interface also allows managing ignored path attributes and setting file paths via Conduit transactions, providing a consistent experience for customizing package behavior and ownership rules.

src/applications/owners/editor · high confidence

Passphrase application registration and policy configuration

The Passphrase application is now registered in the system, exposing credential management routes for listing, creating, editing, destroying, revealing, locking, and accessing credentials via Conduit. It includes a remarkup rule for credential references and integrates credentials into application search. Additionally, default view and edit policies for newly created credentials are configured to respect the 'Credential Author' object policy, ensuring consistent access control based on who created the credential.

src/applications/passphrase/application · high confidence

Paste Conduit API methods restructured and status updated

The Paste application's Conduit API methods have been reorganized and their stability statuses adjusted. The \paste.create\ and \paste.query\ methods are now marked as 'Frozen' (deprecated), with \paste.create\ recommending the use of \paste.edit\ and \paste.query\ recommending \paste.search\. A new \paste.edit\ method has been introduced, leveraging the EditEngine to allow creating or editing pastes via transactions. The \paste.info\ method is marked as 'Deprecated' in favor of \paste.query\. Additionally, a new \paste.search\ method is available for reading paste information via the SearchEngine.

src/applications/paste/conduit · high confidence

Paste application controllers refactored and expanded with archive/edit capabilities

The Paste application's controller layer has been restructured into specialized components: a new PhabricatorPasteArchiveController allows users to archive or activate pastes, a PhabricatorPasteEditController enables editing via the EditEngine, and a PhabricatorPasteRawController provides a stable URI for accessing raw paste content. The main PhabricatorPasteViewController now supports line-range highlighting, transaction timelines, and document recommendations, while the abstract PhabricatorPasteController centralizes menu building and source code view generation.

src/applications/paste/controller · high confidence

Paste embeds now support line count and syntax highlighting options

Users can now customize how pastes are embedded in Remarkup by specifying the number of visible lines and highlighting specific line ranges. When embedding a paste, you can pass options such as \lines=10\ to limit the display height, or \highlight=1-5,10\ to emphasize specific lines or ranges within the code block.

src/applications/paste/remarkup · high confidence

Phame blog and post changes now use modular transaction types

The Phame application now tracks changes to blog and post properties through a new modular transaction system. This introduces specific transaction types for managing blog attributes (such as name, description, status, domain, and images) and post attributes (including title, body, subtitle, header image, and visibility). Users will see structured change history and notifications for these updates, with validation rules enforced for fields like blog names, post titles, and custom domains.

src/applications/phame/xaction · high confidence

Phame blogs now use explicit 404 handling and HTTPS enforcement

Phame blogs now have a dedicated 404 error page that displays a custom message ('Wherever you go, there you are.') instead of a generic error, and blogs configured with HTTPS domains are automatically redirected to secure connections. This change introduces new site classes (PhameSite, PhameBlogSite) and a 404 response handler to manage these behaviors explicitly for custom domain blogs.

src/applications/phame/site · high confidence

Phortune accounts, merchants, and payment methods now support modular transaction history

This change introduces a comprehensive set of transaction types for the Phortune application, enabling detailed, auditable history for account and merchant modifications. Users can now track changes to billing addresses and names, merchant contact info, descriptions, invoice emails, and invoice footers, with specific validation rules (such as email format and length limits) applied during updates. Additionally, payment methods and subscriptions now support transactional updates for names, statuses, and automatic payment method configuration, ensuring that all modifications to these financial entities are recorded with clear before-and-after context.

src/applications/phortune/xaction · high confidence

Phriction Conduit API refactoring and new endpoints

The Phriction Conduit API has been restructured with new base classes and methods. A new 'phriction.create' endpoint allows users to create documents via API, while 'phriction.edit' enables updates. Search capabilities are expanded with 'phriction.content.search' and 'phriction.document.search'. Existing methods 'phriction.history' and 'phriction.info' are now frozen and marked for deprecation in favor of the new search endpoints. The API now returns a standardized document info dictionary including slug, version, author, title, content, status, description, and creation date.

src/applications/phriction/conduit · high confidence

Phriction adopts a modern transaction-based editor

Phriction now uses a new \PhrictionTransactionEditor\ and \PhrictionDocumentEditEngine\ to handle document creation, editing, and deletion. This change consolidates business logic into the editor, enabling support for modular transactions such as comments, policy changes, and document moves, while also introducing draft saving capabilities and improved validation for document ancestry and hierarchy.

src/applications/phriction/editor · high confidence

Phriction adopts modular transactions and introduces draft editing

Phriction document edits are now handled by a modular transaction system, replacing the previous monolithic approach with specific transaction types for content, title, publish, delete, and move operations. This change enables a new draft workflow: users can now save edits as drafts without publishing them, and these draft edits are hidden from the activity feed. Additionally, the system now allows the published version of a document to differ from the most recent draft, and fixes a bug where moving a document previously resulted in a copy rather than a true move.

src/applications/phriction/xaction · high confidence

Phriction controllers rewritten to use modular transactions and PHUI views

The Phriction application controllers have been completely rewritten to adopt the new modular transaction system and the PHUI user interface framework. Editing, moving, and deleting documents now rely on PhrictionTransactionEditor and specific transaction types (e.g., PhrictionDocumentContentTransaction, PhrictionDocumentMoveToTransaction) rather than direct database manipulation. The UI has been modernized to use PHUI components like PHUIObjectBoxView, PHUIHeaderView, and PHUICrumbView, replacing the older Aphront views. This change introduces draft support, allowing users to save and publish document versions separately, and improves the history and diff views with better navigation and version tracking.

src/applications/phriction/controller · high confidence

Phriction documents now use modern string-based status constants

Phriction document status management has been refactored to use human-readable string constants (e.g., 'active', 'deleted', 'moved', 'stub') instead of previous numeric values. This change introduces the \PhrictionDocumentStatus\ class, which defines these statuses and provides associated metadata such as display names, icons, and colors for the UI. Additionally, a new \PhrictionChangeType\ class has been added to categorize document changes (Edit, Delete, Move Here, Move Away, Stub) with corresponding labels. This affects how document states are represented internally and exposed via the Conduit API.

src/applications/phriction/constants · high confidence

Phriction introduces transaction-based email reply handling

Phriction now handles incoming email replies through a new PhrictionReplyHandler class that extends PhabricatorApplicationTransactionReplyHandler. This change shifts the application toward a transaction-based architecture for processing replies, ensuring that email receivers are validated as PhrictionDocument instances and properly identified by their object prefix.

src/applications/phriction/mail · high confidence

Phriction objects now have distinct PHID types for documents and content

Phriction wiki pages and their underlying content are now represented by separate PHID types (\WIKI\ for documents, \WRDS\ for content). This allows the system to assign legitimate PHIDs to older wiki page content objects and enables more precise handle loading, such as including document status and URI information for wiki documents in typeahead results.

src/applications/phriction/phid · high confidence

Phriction storage models migrate to PHIDs and modular transactions

Phriction documents and content now use PHIDs instead of numeric IDs for internal references, and document changes are tracked via a new modular transaction system. This enables features like document subscriptions, permanent deletion, and hierarchical policy inheritance from parent documents, while also introducing support for Spaces and improved search capabilities.

src/applications/phriction/storage · high confidence

Phurl URL creation and editing now uses the EditEngine

The Phurl application now uses the standard EditEngine and ApplicationTransactionEditor for managing URL objects. This change introduces a unified editing interface where users can configure Name, URL, Alias, and Description fields via dedicated edit forms. It also enables transactional history, allowing users to comment on URL changes, and ensures that email notifications are sent with Remarkup-rendered descriptions and proper link sections when URLs are created or modified.

src/applications/phurl/editor · high confidence

Ponder Q&A now uses modular transactions for all changes

The Ponder application has been refactored to use a modular transaction system for all question and answer modifications. This change introduces dedicated controllers for editing questions and answers, managing answer comments, and viewing history, replacing previous ad-hoc handling. Users will see a consistent history timeline for both questions and answers, with detailed change tracking for content updates, status changes (such as closing or resolving questions), and answer visibility. The edit workflows now enforce validation (e.g., preventing empty answers) and provide a unified interface for modifying question details and answer status.

src/applications/ponder/controller · high confidence

Ponder questions and answers now use a modular transaction system with EditEngine support

The Ponder application has been refactored to manage questions and answers through a modular transaction architecture. This introduces dedicated editors (PonderQuestionEditor, PonderAnswerEditor) that handle creation, editing, and commenting via specific transaction types, replacing previous ad-hoc logic. Question editing is now driven by PonderQuestionEditEngine, which exposes fields for title, content, answer summary, and status. The change also standardizes email notifications and feed stories for these actions, adds Herald rule support for questions, and enables email reply handlers for both questions and answers.

src/applications/ponder/editor · high confidence

Profile menu items now depend on installed applications

The People profile menu engine now conditionally includes menu items based on whether specific applications are installed for the viewer. The Badges, Tasks, Revisions, and Commits items are only added if the corresponding Badges, Maniphest, Differential, or Diffusion applications are available, respectively. This ensures that profile navigation only presents options for features the user has access to, removing previously static or always-visible links for these sections.

src/applications/people/engine · high confidence

Project descriptions are now stored as standard custom fields

Project descriptions have been migrated from their previous storage mechanism to the standard custom field system. This change introduces new classes (PhabricatorProjectDescriptionField, PhabricatorProjectCustomField, etc.) to handle project-specific custom fields, ensuring that descriptions are indexed for full-text search and managed consistently with other custom field data.

src/applications/project/customfield · high confidence

Project search now supports the Ferret engine and indexes slugs as body content

Project search results can now be powered by the Ferret fulltext engine, providing an alternative to the previous indexing method. Additionally, project slugs are now included in the searchable body content, ensuring that searches for specific slug identifiers will match project results.

src/applications/project/search · high confidence

Rate limiting for adding email addresses

A new action class has been introduced to enforce rate limiting on the 'Add Email' settings action. This change prevents users from adding too many email addresses to their account in a short period, providing a specific error message when the limit is exceeded.

src/applications/settings/action · high confidence

Rate limiting for adding payment methods

Users attempting to add payment methods are now subject to rate limiting to prevent abuse. A new action class enforces a limit of 60 attempts per hour, displaying a clear error message if the threshold is exceeded.

src/applications/phortune/action · high confidence

Rate limiting for outbound file requests

Users initiating outbound requests to fetch remote URIs are now subject to a rate limit. A new action class enforces a threshold of 60 requests per hour, providing a clear explanation when the limit is exceeded.

src/applications/files/action · high confidence

Rebuild Celerity resource map and package definitions

The Celerity static resource system has been restructured to use a new map and package configuration. The resource map now points to the webroot directory, and the package definitions have been completely rewritten to organize JavaScript and CSS assets into logical bundles (e.g., core, Conpherence, Differential). This change ensures that the correct CSS and JS files are loaded for each application area, supporting the broader UI redesign and modernization efforts.

resources/celerity · high confidence

Rebuilt Chatlog application controllers with modern UI components

The Chatlog application controllers have been rewritten to use the new PHUI component library (PHUIObjectItemListView, PHUIObjectBoxView) and the newPage() API, replacing the previous page construction methods. This change introduces a redesigned user interface for the channel list and log views, including updated breadcrumb navigation, cursor-based pagination for log entries, and improved formatting for author and message blocks.

src/applications/chatlog/controller · high confidence

Rebuilt bulk editor to use EditEngine and support silent background jobs

The bulk editor in the transactions application has been rebuilt to define edit actions via the EditEngine rather than using hard-coded definitions, which restores capabilities for editing Tags, Subscribers, and Remarkup fields (description, comments). The system now supports executing bulk edits silently via a new background worker job type, allowing users with CLI access to apply changes without triggering mail or notifications, and provides a generic transaction-oriented bulk job worker to handle these operations.

src/applications/transactions/bulk · high confidence

Redefine Project Burndown and Activity charts with new engine classes

The Project Burndown chart now displays only open tasks rather than total tasks, providing a clearer view of remaining work. A new Activity chart engine has been introduced to track specific task lifecycle events, including tasks created, reopened, moved into the project, closed, and moved out of the project. These changes are implemented via new \PhabricatorProjectBurndownChartEngine\ and \PhabricatorProjectActivityChartEngine\ classes, which replace previous logic with explicit stacked area datasets for better visual separation of these metrics.

src/applications/project/chart · high confidence

Redesign XHProf profile views with modern UI components

The XHProf profile views have been rewritten to use the new PHUIObjectBoxView and PHUIHeaderView components, replacing the previous rendering logic. This change introduces a more structured layout for profile data, including support for tooltips on table headers (e.g., 'Wall Time (Inclusive)' and 'Wall Time (Exclusive)') via Javelin behaviors. The top-level view now supports downloading the raw .xhprof profile file and displays aggregated metrics with inclusive/exclusive wall time breakdowns. The symbol view presents parent and child call relationships in a dedicated table. These changes modernize the visual presentation and improve usability of the profiling interface.

src/applications/xhprof/view · high confidence

Redesigned Drydock UI with modern status views and authorization management

The Drydock application introduces a comprehensive UI redesign that modernizes the display of resources, leases, and logs using new PHUI-based list views. A new 'Blueprint Authorizations' feature allows administrators to manage and view authorization states for repository operations, with dedicated views for listing and inspecting these authorizations. The log interface has been restructured to provide a detailed, table-based view of operations, including live status updates for underway repository operations and clearer error messaging for failed merges or pushes. Additionally, the UI now respects newlines in log text and displays timestamps, improving the readability and usability of Drydock's operational history.

src/applications/drydock/view · high confidence

Redesigned Maniphest task list views with new UI components

The Maniphest task list views have been redesigned to use the new PHUIObjectItemListView and PHUIObjectItemView components. This change updates the visual presentation of task lists, including the display of status icons, priority colors, and task metadata such as assignment and project tags. Closed tasks are now visually disabled, and batch editing controls are integrated into the list view when applicable. The redesign also improves the handling of empty states and grouping of tasks by priority, status, assignee, or project.

src/applications/maniphest/view · high confidence

Redesigned Pholio mock viewing, embedding, and history interfaces

Pholio mock views have been overhauled to improve usability and visual consistency. The main mock view now renders images via a JavaScript-driven interface, supporting features like inline comment counts on thumbnails, image scaling for wide files, and drag-reordering of mock images. A new thumbnail grid view displays the mock's history, showing current revisions, obsolete images, and deleted images in a structured table. Embedding mocks now uses the PHUIPinboardItemView for a standardized look. Additionally, inline comments are now grouped in the transaction history and display a thumbnail of the specific image portion they reference.

src/applications/pholio/view · high confidence

Redesigned Ponder answer submission and display views

The Ponder application introduces new view classes for managing answers: PonderAddAnswerView now displays a notice if a user has already answered a question and shows a 'Log In to Answer' prompt for unauthenticated users; PonderAnswerView renders answers with a header linked to the author, uses the modification date for timestamps, and hides comments and the comment form behind a disclosure link to reduce clutter; PonderFooterView provides the toggle mechanism for showing or hiding these comments.

src/applications/ponder/view · high confidence

Redesigned dashboard management with unified editing and usage visibility

The dashboard application has been refactored to streamline user interactions and improve visibility. The main edit flow now delegates to the EditEngine, consolidating previous separate 'View', 'Arrange', and 'Manage' modes into a single, smoother editing experience. A new 'Adjust' controller handles specific panel operations (add, remove, move) using a new panel storage format, while an 'Archive' controller allows users to toggle dashboard status. Additionally, the dashboard view now includes a 'Used By' section that explicitly lists where the dashboard is surfaced in menus, helping users understand its context and usage across the platform.

src/applications/dashboard/controller/dashboard · high confidence

Redesigned home and profile side navigation with structured menu items

The home and profile side navigation has been redesigned to use a more structured API for menu items. This introduces specific menu item types, including a 'Built-in Homepage' (Home) that links to the dashboard and a 'More Applications' launcher that links to the applications page. These items are now defined as distinct classes (PhabricatorHomeProfileMenuItem and PhabricatorHomeLauncherProfileMenuItem) extending PhabricatorProfileMenuItem, allowing for better configuration of names, icons, and visibility within the profile menu.

src/applications/home/menuitem · high confidence

Redesigned setup issue UI with improved error handling and configuration display

The configuration view now features a redesigned setup issue interface that provides clearer guidance for resolving configuration problems. Users will see a friendlier 'in-flight' error page for unexpected failures, and the main setup issue view now displays detailed PHP, MySQL, and Phabricator configuration contexts, along with specific commands to install missing extensions or restart services. The UI also introduces the ability to ignore non-fatal setup issues, making it easier to proceed with configuration even when minor warnings are present.

src/applications/config/view · high confidence

Refactor Diffusion VCS command execution and protocol handling

The Diffusion application now uses a new \DiffusionCommandEngine\ hierarchy to manage Git, Mercurial, and Subversion repository interactions. This change introduces a unified command execution layer that enforces a 15-minute default timeout on repository commands to prevent indefinite hangs, and ensures Git commands are always executed as the daemon user to satisfy modern Git security requirements. Additionally, the Mercurial engine now filters the 'bundle2' capability to maintain compatibility, and the Git engine supports HTTP proxying for remote operations. The update also includes a new parser for the Git 'upload-pack' wire protocol to handle 'shallow' frames and improves the Subversion wire protocol parser to tolerate extra whitespace in protocol frames.

src/applications/diffusion/protocol · high confidence

Refactor Slowvote transaction handling into dedicated classes

The Slowvote application's transaction logic has been restructured to use specific, dedicated transaction classes for each poll attribute (description, question, responses, shuffle, status, and voting method) instead of a monolithic implementation. This change introduces a base \PhabricatorSlowvoteTransactionType\ and individual handlers that manage the lifecycle of changes for each field, providing clearer audit trails, distinct feed titles, and specific validation rules (such as requiring a poll question). Users will see more precise activity feed entries reflecting exactly which poll property was modified, and the system now enforces stricter validation on poll creation and updates.

src/applications/slowvote/xaction · high confidence

Refactor dashboard panel edit behavior to use EditEngine

Dashboard panel editing now uses the EditEngine framework instead of the previous CustomFields system. This change introduces specific transaction classes for managing panel properties, allowing users to rename panels, archive or activate them, and edit content. For query panels, users can now explicitly set the application search engine, the search query, and the result limit. Text panels support editing their content with remarkup changes surfaced in the activity feed, while chart and tabs panels have dedicated transaction handlers for their respective configuration keys.

src/applications/dashboard/xaction/panel · high confidence

Refactor email delivery into a customizable mail engine

The email system in the People application has been restructured around a new \PhabricatorPeopleMailEngine\ base class, which standardizes validation, sending, and activity logging for all outgoing messages. This change introduces specific mail engines for Welcome, Username Change, and Email Login workflows. For users, this means the Welcome email now supports custom administrator-provided text and adapts its instructions based on whether password authentication is enabled. The Email Login engine now allows administrators to customize the body text for login and password-set messages, and it provides clearer guidance when password authentication is not active. Additionally, the Username Change notification has been simplified to remove one-time login links, focusing solely on the username update details.

src/applications/people/mail · high confidence

Refactor typeahead datasource architecture with composite sources and function support

The typeahead system has been restructured to support more flexible and powerful search capabilities. A new base datasource class introduces a two-phase query model (prefix and content) to optimize result loading, and adds support for parsing function-driven tokens (e.g., \members(projectX)\) that allow datasources to handle complex logical queries. A new composite datasource architecture enables combining multiple data sources into a single typeahead, with proxy and runtime composite classes to manage these aggregations. Additionally, tokenization has been improved to handle Unicode, brackets, and hyphens more aggressively, ensuring better matching for project names and other identifiers.

src/applications/typeahead/datasource · high confidence

Refactored Differential engine into specialized components

The Differential engine logic has been modularized into distinct, single-responsibility classes to improve maintainability and performance. Affected path tracking is now handled by \DifferentialAffectedPathEngine\, which manages the storage and retrieval of repository paths touched by a revision. Changeset analysis, including generated code detection, content hashing, and copied code identification, is centralized in \DifferentialChangesetEngine\. Diff extraction from commits is now performed by \DifferentialDiffExtractionEngine\, which reuses existing diffs when possible to avoid redundant work. The file tree UI is rendered via \DifferentialFileTreeEngine\, which supports a resizable, desktop-only panel with keyboard shortcuts. Draft inline comments are managed by \DifferentialRevisionDraftEngine\, and revision timeline rendering is handled by \DifferentialRevisionTimelineEngine\, which adjusts inline comments based on changeset differences.

src/applications/differential/engine · high confidence

Refactored HTTP response handling with dedicated response classes and enhanced security headers

The response system has been restructured into a hierarchy of specific response classes (such as AphrontHTMLResponse, AphrontJSONResponse, AphrontFileResponse, and AphrontRedirectResponse) to replace the previous monolithic approach. This change introduces robust Content-Security-Policy (CSP) enforcement with directives like 'object-src 'none'' and 'form-action 'self'', adds HTTP Strict Transport Security (HSTS) support, and implements a 'Referrer-Policy: no-referrer' header. User-facing error pages for 403 and 404 errors have been modernized with device-friendly layouts, and file downloads now support HTTP Range requests for resumable transfers. Additionally, a 'stop on redirect' debugging feature allows developers to inspect stack traces when redirects occur.

src/aphront/response · high confidence

Refactored Lipsum CLI with new base workflow and generation arguments

The Lipsum management CLI has been restructured to improve usability and code organization. A new abstract base class, PhabricatorLipsumManagementWorkflow, now extends PhabricatorManagementWorkflow, and the existing PhabricatorLipsumGenerateWorkflow extends this new base. The generate command now accepts --force and --quickly flags to control confirmation prompts and generation speed, and it uses PhutilClassMapQuery to dynamically discover and list available test data generators, allowing users to select specific types of synthetic data to create.

src/applications/lipsum/management · high confidence

Refactored base controller access control and added 404/redirect controllers

The base controller layer has been restructured to centralize access enforcement and improve security. A new PhabricatorController abstract class now enforces a comprehensive set of requirements including login, admin status, enabled user status, email verification, and multi-factor authentication (MFA) enrollment, with specific logic to handle anonymous sessions for CSRF protection and legal document signatures. Additionally, new controllers have been introduced: Phabricator404Controller and PhabricatorPlatform404Controller to handle 404 responses (with the former explicitly allowing public access), and PhabricatorRedirectController to manage URI redirections with support for external flags. These changes ensure that access rules are consistently applied at the controller level before request processing begins.

src/applications/base/controller · high confidence

Refactored lint saving and introduced commit audit status constants

The Diffusion application now uses a dedicated DiffusionLintSaveRunner class to handle lint message persistence, which improves the reliability of saving lint results by properly resolving SVN commit identifiers within Git repositories and storing blame information. Additionally, a new DiffusionCommitAuditStatus class has been added to manage commit audit states (such as 'Audited' or 'Needs Verification') with support for legacy key mapping, replacing the previous PhabricatorAuditCommitStatusConstants.

src/applications/diffusion · high confidence

Refactored script initialization to support optional database configuration and signal handling

The script initialization logic has been restructured to allow specific scripts, such as Aphlict and setup utilities, to run without a valid database connection by passing a 'config.optional' flag. This change enables the notification server to start independently of the database and allows setup scripts to continue even if database configuration is initially missing. Additionally, a new initialization path for scripts handling signals has been introduced to properly configure async signal handling.

scripts/init · high confidence

Refactoring Doorkeeper engine to support multiple display modes and external object bridging

The Doorkeeper engine now supports multiple display variations (full and short) for external object references, allowing story text to be rendered with implied context (e.g., "this revision") for single-object targets like Asana tasks, or full names for multi-object contexts like JIRA issues. This change introduces new engine classes—DoorkeeperObjectRef, DoorkeeperURIRef, DoorkeeperImportEngine, and DoorkeeperFeedStoryPublisher—to manage external object references, handle imports via bridges (such as Asana and JIRA), and control how story text is published. The import engine now uses a timeout for external service calls and leverages PhutilClassMapQuery to discover enabled bridges, ensuring that duplicate references are handled correctly and that story text is not published for "close" events.

src/applications/doorkeeper/engine · high confidence

Replace checkbox lists with typeahead search for task status, priority, assignee, and subtype

Users can now search and select task status, priority, assignee, and subtype using typeahead inputs instead of scrolling through static checkbox lists. This change introduces dedicated typeahead datasources that support fuzzy matching and provide browse dialogs for each field. Status selection is enhanced with new 'open()' and 'closed()' function tokens, allowing users to quickly filter by any open or closed status. Disabled statuses and priorities are now visually marked as closed in the results. Assignee selection combines standard user search with a 'none' option for unassigned tasks. Subtype selection now uses a formal subtype map, providing icons and colors for better visual identification.

src/applications/maniphest/typeahead · high confidence

Replace external Cowsay dependency with native PHP implementation

The Cowsay rule now uses a native PHP implementation instead of the previous external Perl-based tool. This change includes the full Cowsay 3.03 source code (cowsay executable, documentation, and license) and a comprehensive set of built-in ASCII art cow files (such as default, tux, dragon, and bunny) located in externals/cowsay/cows. Additionally, a new custom cow file (companion.cow) has been added to resources/cows/builtin, and a README in resources/cows/custom documents how users can add their own .cow files for use with the Remarkup interpreter.

externals/cowsay, resources/cows · high confidence

Repository destruction now warns about local working copies

When a repository is destroyed, the system now checks if a local working copy exists on disk. If one is present, a notification is displayed to the user explaining that the database records have been removed but the local files remain, and providing the specific path to manually delete the working copy if desired.

src/applications/repository/codex, src/applications/system/codex · high confidence

Repository management UI restructured into modular panels

The Diffusion repository management interface has been refactored from a single form into a modular, sectioned layout. Repository settings are now organized into distinct management panels—Basics, URIs, Policies, Branches, Limits, Storage, Automation, Staging Area, Symbols, and History—each handling specific configuration aspects. This change improves navigation and clarity by grouping related options (such as push policies, branch rules, and storage paths) into dedicated views rather than a monolithic edit page.

src/applications/diffusion/management · high confidence

Restructured Herald rule engine with explicit execution order and application tracking

The Herald engine now enforces a strict, explicit execution order for rules and tracks which rules have already been applied to specific objects. This change introduces a new HeraldEffect class to record rule applications and integrates a 'first-time only' policy, allowing rules to be disabled rather than deleted and ensuring they do not re-trigger on subsequent events. The engine also includes a field value cache and handles recursive condition cycles, providing a more structured and resilient rule evaluation process.

src/applications/herald/engine · high confidence

Restructured Phortune account management with dedicated controllers and merchant-customer views

The Phortune account interface has been refactored into a set of specialized controllers under src/applications/phortune/controller/account, replacing the previous monolithic structure. This change introduces distinct views for account details, payment methods, orders, charges, and managers, each with its own controller (e.g., PhortuneAccountDetailsController, PhortuneAccountPaymentMethodController). A new base controller, PhortuneAccountController, enforces capability-based access (view vs. edit) and introduces a merchant-customer distinction: users accessing an account they do not own are shown as 'customers' linked to specific merchants, with an authority notice explaining their access. The account list page now displays both payment accounts (where the user is a member) and merchant accounts (where the user is a controller). Additionally, new controllers support managing account managers, billing email addresses (with enable/disable/rotate actions), and subscription autopay settings, providing a more granular and secure account management experience.

src/applications/phortune/controller/account · high confidence

Rewritten mail and SMS adapter infrastructure with new configuration options

The mail and SMS adapter system has been completely rewritten to use a new base class and API. This change introduces support for sending SMS messages via new adapters for Twilio and Amazon SNS, in addition to the existing email providers (Amazon SES, Mailgun, Postmark, SendGrid, SMTP, and Sendmail). The new architecture allows for more granular configuration, such as explicitly controlling the 'Message-ID' header behavior for SMTP and Sendmail adapters, and updates the SendGrid and SES adapters to use their modern APIs. The test adapter has also been updated to support both email and SMS message types for testing purposes.

src/applications/metamta/adapter · high confidence

Search indexing now runs in the background worker queue with improved error handling and locking

Search indexing tasks are now executed by the background worker queue (PhabricatorSearchWorker) instead of synchronously, allowing operations like 'bin/search index --background' to function correctly. Indexing tasks are assigned a dedicated PRIORITY\_INDEX priority. The system now uses global locks to prevent contention when indexing the same object concurrently, yielding briefly if a lock cannot be acquired. Additionally, indexing errors are suppressed in the daemon logs unless the 'strict' mode is enabled (used by the CLI tool), preventing non-actionable errors (such as indexing deleted objects) from cluttering the logs.

src/applications/search/worker · high confidence

Settings management is refactored to use the EditEngine framework

The Settings application now uses the EditEngine framework to handle user and global configuration changes. This introduces a modular architecture where settings are managed through \PhabricatorSettingsEditEngine\ and \PhabricatorUserPreferencesEditor\, enabling administrators to configure global defaults and allowing users to edit personal settings via a unified interface. The change also implements caching for user preferences and supports transaction-based updates for individual setting keys.

src/applications/settings/editor · high confidence

Slowvote now supports closing polls and configurable response visibility

Poll creators can now close or reopen polls via a dedicated action, and can configure who sees the results: always visible, only after voting, or only to the owner. Voting logic enforces the selected method (Plurality or Approval) and validates options, while comments are handled through the standard transaction timeline.

src/applications/slowvote/controller · high confidence

Slowvote polls now support transactional editing and email notifications

The Slowvote application now uses a dedicated editor class to manage poll changes via ApplicationTransactions, enabling most poll fields to be edited transactionally rather than through direct object mutation. This change introduces email notifications for poll activity, including details on when poll settings are changed, when votes are cast, and other general activity, with the email body rendering the poll description using Remarkup syntax. Additionally, feed stories are automatically published for poll updates, and the system supports threaded replies to notification emails.

src/applications/slowvote/editor · high confidence

Slowvote storage model and transaction system restructured

The Slowvote application's data layer has been rebuilt to use a modular transaction system and modern DAO patterns. New storage classes (PhabricatorSlowvotePoll, Option, Choice) now implement interfaces for policy control, subscription, and destruction, allowing polls to be edited, watched, and permanently removed. Poll creation defaults to sensible string constants for voting methods and response visibility, and the system now supports transactional edits for most poll fields, enabling a more consistent and flexible user experience for managing polls.

src/applications/slowvote/storage · high confidence

Standardize CLI entry points via symbolic links

The \bin/\ directory has been restructured to use symbolic links that point to specific management scripts in the \scripts/\ directory. This change provides a consistent, unified interface for administrators to manage various system components—including daemons (phd, aphlict), storage, search, repositories, and user policies—by invoking commands directly from the \bin/\ path rather than navigating to individual script locations.

bin · high confidence

Standardize Maniphest custom field implementation

Maniphest custom fields now extend the shared PhabricatorCustomField base class and implement PhabricatorStandardCustomFieldInterface, replacing the previous custom field architecture. This change introduces standardized storage and indexing mechanisms (ManiphestCustomFieldStorage, StringIndex, NumericIndex) and a new configuration-driven field creation process via ManiphestConfiguredCustomField, ensuring that custom fields behave consistently with other Phabricator applications and support features like copying field values when creating similar tasks.

src/applications/maniphest/field · high confidence

Standardize bulk edit field controls via new parameter types

The bulk editor now uses a unified set of parameter types (BulkParameterType and its subclasses) to define how fields are edited, replacing previous ad-hoc definitions. This change restores and standardizes support for editing Tags and Subscribers (via BulkTokenizerParameterType), Remarkup fields like descriptions (BulkRemarkupParameterType), and select-type fields such as status and priority (BulkSelectParameterType). It also adds support for editing task points (BulkPointsParameterType) and ensures the current viewer is correctly passed to these controls, improving consistency and functionality across bulk edit operations.

src/applications/transactions/bulk/type · high confidence

Standardize dashboard editing via EditEngine

The dashboard editor now uses the EditEngine framework for managing dashboards, panels, and portals, replacing the previous custom edit controllers. This change introduces dedicated edit engines and transaction editors for each resource type, enabling consistent policy editing (view/edit permissions) and transaction handling. Users benefit from a unified editing interface that supports creating and modifying dashboards, panels, and portals with standardized fields like name, icon, and layout mode, while also fixing a previous issue where editing a dashboard panel from a dashboard could duplicate the panel.

src/applications/dashboard/editor · high confidence

Standardize policy capability classes across applications

This change introduces a consistent set of policy capability classes for Differential, Diffusion, Legalpad, Macro, Maniphest, Nuance, OAuthServer, Pholio, and Slowvote. Each application now has dedicated capability classes (e.g., \DifferentialDefaultViewCapability\, \DiffusionCreateRepositoriesCapability\) that extend \PhabricatorPolicyCapability\. These classes define specific permissions such as 'Default View Policy', 'Can Create Repositories', 'Can Push', 'Can Bulk Edit Tasks', and 'Can Manage Sources', along with appropriate rejection messages where applicable. This standardization simplifies the implementation of policy checks and ensures uniform behavior for view, edit, push, and management permissions across these applications.

(repo-wide) · high confidence

Standardize relationship editing across Differential, Diffusion, and Pholio

The relationship-editing actions for Differential Revisions, Diffusion Commits, and Pholio Mocks have been migrated to the modern Relationships framework. This change introduces new relationship classes (such as \DifferentialRevisionHasChildRelationship\ and \DiffusionCommitHasRevisionRelationship\) that define how these objects relate to each other and to Maniphest Tasks, ensuring consistent behavior and UI dialogs for managing these connections across the three applications.

src/applications/differential/relationships, src/applications/diffusion/relationships, src/applications/pholio/relationships · high confidence

Standardize task editing and transaction handling via EditEngine

Maniphest task creation and editing are now routed through the unified EditEngine infrastructure, replacing previous ad-hoc implementations. This change introduces a new \ManiphestEditEngine\ to configure task forms and a \ManiphestTransactionEditor\ to handle all task modifications as standard transactions. Users benefit from consistent behavior across bulk edits, inline edits, and API calls, as well as new capabilities such as locking tasks to prevent further interaction, moving tasks between workboard columns via transactions, and improved email notifications that reflect specific transaction types like status changes or column moves.

src/applications/maniphest/editor · high confidence

Standardize user preferences into modular settings

This change converts a wide range of user preferences—such as accessibility, Conpherence notifications and sound, DarkConsole, date/time formats, email delivery, display options, and search scope—into a unified, modular settings system. Users will now find these options organized into dedicated panels within the Settings UI, allowing for more consistent management and clearer configuration of their account and application preferences.

src/applications/settings/setting · high confidence

Structured exception hierarchy for authentication workflows

The authentication system now uses a comprehensive set of specific exception classes to handle various error states, improving how users are informed about issues. This includes distinct exceptions for SSH private key problems (distinguishing between format errors, incorrect passphrases, missing passphrases, and surplus passphrases), invite-related errors (such as invalid codes, login requirements, and registration conflicts), and high-security mode requirements (supporting multi-factor auth with session upgrade indicators). General authentication errors are also categorized into configuration issues, invalid credentials, and user-aborted workflows, allowing for more precise error handling and user feedback.

src/applications/auth/exception · high confidence

Structured workflow for installing dashboards to menus and portals

The dashboard installation process now uses a dedicated set of workflow classes to guide users through adding dashboards to specific locations. Administrators and users can now explicitly choose to add a dashboard to the global or personal Home menu, the global or personal Favorites menu, a specific Project menu, or a Portal menu. This structured approach replaces ad-hoc installation with clear confirmation dialogs and permission checks for each target location.

src/applications/dashboard/install · high confidence

Support for configurable MFA providers, contact numbers, and auth messages

This change introduces transaction types that allow administrators to manage multi-factor authentication (MFA) providers, contact numbers, and onboarding messages. Administrators can now enable or disable MFA providers, designate a primary contact number for SMS, and customize enrollment messages. The system enforces security by preventing users from modifying or disabling their primary contact number while SMS MFA is active, and it blocks the deactivation of the last active MFA provider if multi-factor authentication is required. Additionally, it supports upgrading password hashes and revoking specific passwords.

src/applications/auth/xaction · high confidence

The Doorkeeper application now supports rendering link tags with different display styles (such as 'short' or 'full'). This is implemented via a new DoorkeeperTagsController that accepts tag specifications including a 'view' parameter. When a 'short' view is requested, the controller uses the object's short name; otherwise, it uses the full name. The controller also enforces a 15-second timeout on external service calls to fetch reference data and uses phutil\_json\_decode for parsing input. The resulting tags are rendered using PHUITagView.

src/applications/doorkeeper/controller · high confidence

Support for multiple external account identifiers and provider-specific authentication updates

The authentication adapter system now supports linking accounts via multiple identifiers (such as both email and provider-specific IDs) rather than a single account ID, allowing users to sign in with different credentials for the same account. This change also updates specific providers to match their current APIs: GitHub now uses the Authorization header instead of a URI parameter, Asana reads the new 'gid' field, JIRA prefers the modern 'rest/api/3/myself' endpoint with a fallback to older versions, and Google authentication now captures both email addresses and Google Account IDs.

src/applications/auth/adapter · high confidence

Support for raw diffs against specific commits in Diffusion

The Diffusion raw diff query now allows users to specify a target commit to diff against, rather than only diffing against the previous commit. This change introduces a new \DiffusionRawDiffQuery\ base class and specific implementations for Git, Mercurial, and Subversion repositories. For Git, it handles the edge case of the initial commit by diffing against the root commit. For Mercurial, it uses a revset to diff against \null\ for the first commit. For Subversion, it utilizes a \binary\_safe\_diff\ script to ensure correct handling of binary files. This enables more flexible raw diff generation across different version control systems.

src/applications/diffusion/query/rawdiff · high confidence

Phriction now supports relative links (using ./ and ../ syntax) in wiki markup, resolving them against the current document's path. The system also normalizes link lookups to handle URL-encoded characters (e.g., accepting both \[\[ $doge \]\] and \[\[ %24doge \]\]) and correctly parses anchors within link syntax. Additionally, missing documents are now displayed as red links, while documents that exist but are invisible to the user are shown with a lock icon, providing clearer feedback on link validity and permissions.

src/applications/phriction/markup · high confidence

Support for tracking dashboard panel usage in containers

Dashboard panels are now indexed based on the containers that use them, enabling the system to show where specific panels are utilized. This is implemented via a new \PhabricatorDashboardPanelContainerInterface\ that containers must implement to return their associated panel PHIDs, and a corresponding \PhabricatorDashboardPanelContainerIndexEngineExtension\ that handles the indexing logic for these relationships.

src/applications/dashboard/engineextension, src/applications/dashboard/interface · high confidence

Task edit locking and policy codex

Tasks can now be locked to prevent further edits, restricting modification rights to the task owner only. This change introduces a new policy codex (ManiphestTaskPolicyCodex) that enforces this rule and updates the UI to display a lock icon and 'Edits Locked' tag when applicable. The underlying storage schema for ManiphestTask has been updated to support these policy and status changes, ensuring that locked tasks maintain their integrity while still allowing the owner to interact with them.

src/applications/maniphest/storage · high confidence

Task generation now includes projects, subscribers, and priority keywords

The Lipsum task data generator has been updated to create more realistic test data by assigning generated tasks to random projects, adding random subscribers, and setting task priority using keyword values instead of integers. It also ensures that the majority of generated tasks are created with the default open status.

src/applications/maniphest/lipsum · high confidence

Unbeta Ponder and expose application configuration

The Ponder application is no longer in beta status, making it a standard, fully supported utility within the platform. This change introduces the \PhabricatorPonderApplication\ class, which registers the application's metadata (name, description, icon), defines its URL routes for questions and answers, enables email integration for creating questions, and sets up default moderation and view policies for users.

src/applications/ponder/application · high confidence

Unified Drydock lifecycle management via dedicated update workers

The Drydock worker subsystem has been restructured to use dedicated update workers—DrydockLeaseUpdateWorker, DrydockResourceUpdateWorker, and DrydockRepositoryOperationUpdateWorker—to manage the full lifecycle of leases, resources, and repository operations. These workers centralize state transitions (pending, acquired, active, released, broken, destroyed) and command processing, ensuring that leases are properly released when interrupted or expired, resources are reclaimed when unused, and repository operations correctly acquire and destroy working-copy leases. This change improves reliability by handling activation failures, enforcing expiration, and ensuring follow-up tasks execute even after failures.

src/applications/drydock/worker · high confidence

Update Stripe PHP bindings to version 1.16.0

The Stripe PHP library has been updated to version 1.16.0. This release adds support for metadata on refunds and disputes, allows transfers to be canceled, and supports adding cards to recipients. It also introduces a new \Stripe\_RateLimitError\ class for handling rate limit errors and updates the CA certificate bundle.

externals/stripe-php · high confidence

Updated quickstart SQL schema and added MySQL fulltext stopwords files

The quickstart database setup script has been regenerated to reflect the current schema definitions, ensuring new installations start with the correct table structures. Additionally, dedicated stopwords files for MySQL fulltext search (including a MyISAM-specific variant) have been added to support proper indexing and query parsing behavior.

resources/sql · high confidence

Upgrade to PHPMailer 5.1 with SMTP and SES improvements

The embedded PHPMailer library has been updated to version 5.1. This upgrade introduces native SMTP support, allowing emails to be sent via SMTP servers in addition to the existing mail and sendmail methods. It also improves Amazon SES integration by switching to the sendRawEmail API, which enables the inclusion of custom headers. Additionally, the default SMTP connection timeout has been increased from 10 seconds to 60 seconds to handle slower network conditions, and the library now correctly handles custom Message-ID headers while removing the generation of duplicate or bogus headers.

externals/phpmailer · high confidence

VCS HTTP responses now include custom error messages in headers

The new PhabricatorVCSResponse class changes how Git, Mercurial, and Subversion HTTP interactions report status. For Git clients, error messages are now sent in the X-Phabricator-Message HTTP header (visible with GIT\_CURL\_VERBOSE) since Git does not output the response body, while Mercurial and Subversion continue to use the HTTP status message line. This ensures users can see specific repository error details during clone or fetch operations that previously might have been obscured.

src/applications/repository/response · high confidence

XHProf controller modernization and public access

The XHProf application controllers have been refactored to support modern API patterns and broader accessibility. The profile and sample list views are now publicly accessible, allowing users to view profiling data without authentication. Additionally, the system now supports importing XHProf profiles via drag-and-drop uploads, storing them as JSON data rather than PHP serialization, and provides a dedicated controller to handle these file imports securely.

src/applications/xhprof/controller · high confidence

audit.query API method now delegates to DiffusionCommitQuery

The audit.query Conduit method has been refactored to query audit requests via DiffusionCommitQuery instead of its previous implementation. This change aligns the method with the Diffusion application (as indicated by the new base class returning PhabricatorDiffusionApplication) and allows it to handle both string and integer status values through a mapping to DiffusionCommitAuditStatus constants. The API remains frozen and deprecated in favor of diffusion.commit.search, but continues to support filtering by auditor PHIDs, commit PHIDs, and specific audit statuses (open, concern, accepted, partial).

src/applications/audit/conduit · high confidence

Fixes

Add PHID type handlers for OAuth server clients and authorizations

This change introduces two new PHID type classes, PhabricatorOAuthServerClientPHIDType and PhabricatorOAuthServerClientAuthorizationPHIDType, which enable proper object handle loading for OAuth server clients and their authorizations. The client type now correctly sets both the name and URI on handles, resolving a previous issue where OAuth server client object handles were missing URIs, which caused dialogs to appear without buttons. The authorization type provides similar handle loading functionality for OAuth authorizations.

src/applications/oauthserver/phid · high confidence

Added PhabricatorPHIDInterface to support PHP 5.3 compatibility

Introduced the PhabricatorPHIDInterface interface, which defines the getPHID method. This change serves as a workaround for a bug in PHP 5.3 and earlier versions regarding abstract methods in interfaces, ensuring compatibility with older PHP environments.

src/applications/phid/interface · high confidence

Test coverage

Added basic test for HeraldField::getAllFields; Added cache configuration diagnostics specs; Added infrastructure and acceptance tests for Phabricator; Added test case for Phortune payment provider retrieval; Added test coverage for auth factor and invite logic; Added test coverage for email body parsing and signature stripping; Added test coverage for password engine and SSH key revocation; Added test data generator for Owners Packages; Added test fixtures for diff context parsing; Added test for MetaMTA mail body rendering; Added test for default Phortune account initialization; Added test suite for Differential parse and render logic; Added test suite for file transform implementations; Added tests for Almanac service and device name validation; Added tests for ConduitCall execution and authentication; Added tests for Differential line adjustment and hunk parsing; Added tests for Diffusion URI parsing and generation; Added tests for Diffusion commit remarkup rule parsing; Added tests for Diffusion protocol command engines and wire parsers; Added tests for DiffusionGitBranch remote branch parsing; Added tests for Ferret engine term corpus and ngram extraction; Added tests for GitHub event parsing; Added tests for Harbormaster autotargets and build log line mapping; Added tests for Herald rule execution order and transcript truncation; Added tests for JIRA bridge URI conversion; Added tests for Maniphest task status validation; Added tests for OAuth redirect URI validation; Added tests for PhabricatorObjectListQuery parsing; Added tests for Phrequent time block logic; Added tests for controller access control policies; Added tests for file secret scrambling and visibility policies; Added tests for file storage format encryption and integrity; Added tests for owners package path resolution logic; Added tests for project hashtag remarkup rule; Added tests for the Mercurial wire protocol SSH parser; Added tests for the request cache mechanism; Added tests for typeahead datasource tokenization and function evaluation; Added tests for user registration email validation; Added unit tests for AphrontHTTPSink behavior; Added unit tests for AphrontRequest and routing maps; Added unit tests for CalendarTimeUtil timezone handling; Added unit tests for Celerity postprocessors and resource transformers; Added unit tests for Conpherence room creation and participant management; Added unit tests for Differential parser components; Added unit tests for DiffusionPathIDQuery edge cases; Added unit tests for MetaMTA mail configuration, sending, and received mail handling; Added unit tests for Phortune currency parsing and formatting; Added unit tests for Spaces namespace creation and policy enforcement; Added unit tests for application subclass implementations; Added unit tests for mail receiver address matching and validation; Added unit tests for project core functionality; Added unit tests for repository change parsers; Added unit tests for repository storage logic; Added unit tests for repository working copy discovery and pulling; Added unit tests for the Policy application; Expanded test coverage for differential diff rendering.

Dependencies

Added Stripe PHP library dependency

The project now includes the Stripe PHP library (stripe/stripe-php) as a dependency, enabling integration with Stripe's payment processing API. This addition requires PHP 5.2 or higher along with the curl, json, and mbstring extensions.

(dependencies) · high confidence

Housekeeping

Phabricator is no longer actively maintained; Placeholder added for keys configuration directory.

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 29 → 32 (+3.1)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

Lenses

  • Code Health 42 → 39 (-2.8)
  • Architecture 93 → 93 (-0.3)
  • Maturity 47 → 48 (+1.0)
  • Readiness 17 → 24 (+7.3)
  • Security 27 → 27 (+0.0)

Resolved (256)

  • Duplicated block (10 lines × 16) (src/applications/dashboard/xaction/panel/PhabricatorDashboardPanelStatusTransaction.php)
  • Duplicated block (10 lines × 2) (src/applications/auth/controller/contact/PhabricatorAuthContactNumberViewController.php)
  • Duplicated block (10 lines × 2) (src/applications/harbormaster/xaction/build/HarbormasterBuildMessageAbortTransaction.php)
  • Duplicated block (10 lines × 2) (src/applications/legalpad/query/LegalpadDocumentSignatureSearchEngine.php)
  • Duplicated block (11 lines × 2) (src/applications/badges/xaction/PhabricatorBadgesBadgeStatusTransaction.php)
  • Duplicated block (11 lines × 2) (src/applications/differential/typeahead/DifferentialExactUserFunctionDatasource.php)
  • Duplicated block (11 lines × 2) (src/applications/fact/controller/PhabricatorFactObjectController.php)
  • Duplicated block (11 lines × 2) (src/applications/files/query/PhabricatorFileSearchEngine.php)
  • Duplicated block (11 lines × 2) (src/applications/notification/query/PhabricatorNotificationSearchEngine.php)
  • Duplicated block (11 lines × 2) (src/applications/packages/editor/PhabricatorPackagesPackageEditor.php)
  • Duplicated block (11 lines × 2) (src/applications/phid/PhabricatorObjectHandle.php)
  • Duplicated block (11 lines × 2) (src/applications/phortune/controller/account/PhortuneAccountListController.php)
  • Duplicated block (11 lines × 2) (src/applications/ponder/query/PonderQuestionSearchEngine.php)
  • Duplicated block (11 lines × 3) (src/applications/dashboard/xaction/dashboard/PhabricatorDashboardStatusTransaction.php)
  • Duplicated block (11 lines × 3) (src/applications/uiexample/examples/PHUIObjectItemListExample.php)
  • Duplicated block (11 lines × 4) (src/applications/calendar/xaction/PhabricatorCalendarEventAllDayTransaction.php)
  • Duplicated block (11 lines × 4) (src/applications/uiexample/examples/PHUIColorPalletteExample.php)
  • Duplicated block (11 lines × 6) (src/applications/almanac/controller/AlmanacBindingViewController.php)
  • Duplicated block (11 lines × 6) (src/applications/calendar/controller/PhabricatorCalendarEventJoinController.php)
  • Duplicated block (11 lines × 6) (src/applications/calendar/controller/PhabricatorCalendarImportDisableController.php)
  • …and 236 more

New (489)

  • Duplicated block (11–19 lines × 4) (src/applications/uiexample/examples/PHUIBoxExample.php)
  • Duplicated block (15 lines × 3) (src/applications/dashboard/controller/dashboard/PhabricatorDashboardArchiveController.php)
  • Duplicated block (16 lines × 2) (src/applications/dashboard/controller/dashboard/PhabricatorDashboardArchiveController.php)
  • Duplicated block (19–20 lines × 5) (src/applications/guides/module/PhabricatorGuideInstallModule.php)
  • Duplicated block (26 lines × 5) (src/applications/differential/constants/DifferentialConstantsModule.php)
  • Duplicated block (26–28 lines × 2) (src/applications/uiexample/examples/PHUIBoxExample.php)
  • Edited copies of one member (3 members, 10+ corresponding lines) (src/applications/files/conduit/FileDownloadConduitAPIMethod.php)
  • Edited copies of one member (3 members, 10+ corresponding lines) (src/applications/transactions/storage/PhabricatorApplicationTransaction.php)
  • Edited copies of one member (3 members, 11+ corresponding lines) (src/applications/herald/typeahead/HeraldRuleTypeDatasource.php)
  • Edited copies of one member (3 members, 12+ corresponding lines) (src/applications/drydock/controller/DrydockAuthorizationListController.php)
  • Edited copies of one member (3 members, 13+ corresponding lines) (src/applications/auth/controller/config/PhabricatorAuthProviderViewController.php)
  • Edited copies of one member (3 members, 13+ corresponding lines) (src/applications/diffusion/controller/DiffusionController.php)
  • Edited copies of one member (3 members, 14+ corresponding lines) (src/applications/auth/query/PhabricatorAuthFactorProviderQuery.php)
  • Edited copies of one member (3 members, 14+ corresponding lines) (src/applications/calendar/editor/PhabricatorCalendarEventEditor.php)
  • Edited copies of one member (3 members, 14+ corresponding lines) (src/applications/files/document/PhabricatorAudioDocumentEngine.php)
  • Edited copies of one member (3 members, 14+ corresponding lines) (src/applications/nuance/typeahead/NuanceQueueDatasource.php)
  • Edited copies of one member (3 members, 14+ corresponding lines) (src/applications/project/menuitem/PhabricatorProjectDetailsProfileMenuItem.php)
  • Edited copies of one member (3 members, 14+ corresponding lines) (src/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php)
  • Edited copies of one member (3 members, 15+ corresponding lines) (src/applications/herald/controller/HeraldController.php)
  • Edited copies of one member (3 members, 15+ corresponding lines) (src/applications/packages/view/PhabricatorPackagesPackageListView.php)
  • …and 469 more

Changes since last survey

  • 1 commits — 1 feature/other, 0 fixes

By area

  • externals/stripe-php — 1 commit

Notable commits

  • change: Correct static issues in Stripe library for PHP 8.5

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

phacility/phabricator was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 14 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 7ec88f3b4ed096fc5908f6ecdf961e74ba6ccb43 — the exact code this score is about.
  • Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.65+preprod-36d4cd83012f.