Mozilla releases MozPhab 2.24.0 with VCS and Lando integration fixes
MozPhab 2.24.0 improves development workflow stability by fixing Phabricator stack errors and ensuring compatibility with upcoming Jujutsu (jj) releases.
Summary
Mozilla has released version 2.24.0 of MozPhab, a specialized tooling component used in the Firefox development ecosystem. This update focuses on hardening the internal engineering workflow by addressing several critical bugs related to version control system (VCS) interactions and environment configurations.
The release specifically targets stability issues during reorganization tasks and ensures that the tool remains compatible with future updates to the Jujutsu (jj) version control system. Additionally, it updates network routing for Lando-related services to utilize Fastly WAF-protected domains.
Technical improvements in MozPhab 2.24.0
- Workflow Stability: Fixed a critical failure in the
reorg --forcecommand that previously left the Phabricator stack in a tangled, inconsistent state. - VCS Compatibility: Implemented fixes to prevent breakage caused by the upcoming release of Jujutsu (jj) version 0.47 and removed arguments from the VCS layer to improve abstraction.
- Configuration Management: Introduced a mechanism to resolve command flags and configurations into a frozen options object to ensure predictable execution.
- Network and Environment: Updated hard-coded Lando-dev URLs to point toward domains fronted by Fastly Web Application Firewalls (WAF) and moved Lando warning detection to the submission phase.
Why it matters
While MozPhab is an internal tool for Mozilla engineers, its stability directly affects the velocity and reliability of Firefox development and contributions. Improvements to VCS abstraction and compatibility with tools like Jujutsu ensure that the Firefox engineering pipeline remains robust against upstream changes in the open-source development toolchain.
Original reference: discourse.mozilla.org →