Page MenuHomePhabricator

2019 Week 37 (Mid September)
Updated 1,679 Days AgoPublic

Version 1 of 1: You are viewing the current published version of this document.

Summary of changes from September 8, 2019 to September 13, 2019.

CodebaseRepositoryHEADActivity
PhabricatorrPrP3dcb4a7b5023 commits
ArcanistrARCrARC3cdfe1ff0 commits
libphutilrPHUrPHUf51f1b30 commits
Instances (SAAS)rSAASrSAAS7ecf93d0 commits
Services (SAAS)rSERVICESrSERVICESc4bd1190 commits
Core (SAAS)rCORErCOREd8bf7ac0 commits
  • These changes were promoted to stable.

General

  • No notes in this period.

Security

  • No notes in this period.

Migrations

MigrationRiskDurationNotes
20190909.herald.01.rebuild.php31 ms

"Duration" is the duration for this install, and may not be representative.

Upgrading / Compatibility

[] "sql_mode" Setup Warnings: MySQL can be configured to operate in various error modes with the "sql_mode" configuration option.

Phabricator no longer raises a setup warning if the ONLY_FULL_GROUP_BY mode is enabled. Enabling this mode is mildly desirable, and recent versions of MySQL enable it by default. There may be some lurking incompatibilities with this mode so you may not want to actually enable it yet if it isn't already enabled, but we'll make Phabricator run in this mode going forward. See T13404.

Phabricator now raises a less forceful setup warning about the STRICT_ALL_TABLES mode. Enabling this mode is desirable, but you don't really need to enable it if you have some reason that you don't want to.

Previously, the ONLY_FULL_GROUP_BY setup warning could mask the STRICT_ALL_TABLES setup warning. The internal key for the STRICT_ALL_TABLES warning has been changed, so you may be re-prompted with it if you previously ignored it. It is safe to ignore it again if you prefer not to configure this mode.

Minor

  • [] Added a workaround for a rendering engine hang in Chrome 77 when text is word-wrapped in certain ways. See T13413.
  • Fixed a global menu fatal which could occur on the 404 page or other pages with no application context.
  • [] Fixed an error when executing a global search for the install URI with no trailing slash.
  • [] Herald now indexes fields, not just actions, when considering which rules are related to objects like Owners Packages.
  • [] Added a "Remove Flag" action to Herald.
  • When Herald changes the subscribers of an object, the event is no longer published to feeds (these events are universally uninteresting).
  • The "Another Herald rule..." dropdown now labels disabled rules more clearly.
  • [] Removed the "Document Moved From" notice in Phriction, since it didn't serve much of a purpose.
  • [] In Applications, policy edit transactions now render in a more useful way, similar to other applications. Policies are also now linked.
  • [] Capability dialogs (explaining who can see or edit an object) and policy exception dialogs (explaining why you can't take an action) now render custom policy rules inline (provided you have permission to see the object in question).
  • Herald no longer offers fields or actions associated with uninstalled applications when writing new rules (some fields and actions may not be properly associated with related applications yet).
  • [] Herald now offers a "Subtype" field for objects that support subtypes.
  • [] Subtypes now support a "mutations" list. You can use this list to choose which options the UI offers under "Change Subtype", or to hide the control entirely.

The [] icon indicates a change backed by support mana.

Last Author
epriestley
Last Edited
Sep 13 2019, 7:36 PM