FOSSWire
Search/
Distro Planets

Mozilla migrates Bugzilla REST API to native Mojo in latest BMO deployment

Brief written by the FOSSWire AI editor from Planet Mozilla How we write

1 min read

Key Takeaway

Mozilla's bugzilla.mozilla.org instance has completed a major backend migration moving Bug REST resources from legacy code to a native Mojo API implementation.

Summary

Mozilla deployed a new version of its Bugzilla Mozilla instance (BMO) on November 3, 2026, with four focused changes touching the Phabricator integration, core API infrastructure, and notification system testing. The most substantial change is the migration of Bug REST resources to a native Mojo API, covering bug object operations including get, search, create, update, possible_duplicates, and history endpoints. This follows earlier migration work and includes companion cleanup of shared helpers in Bugzilla::API::V1::Util.

The deployment also fixes a Phabricator timestamp issue where last-modified times updated without actual revision changes, and adds database-backed test coverage for flag-event bugmail recipient selection logic. These changes affect Mozilla's internal development infrastructure and the broader community of contributors who interact with BMO's web services and email notifications.

What changed in BMO 20261103.1

  • REST-to-Mojo migration: Bug object REST resources (get, search, create, update, possible_duplicates, history) have been reimplemented using Bugzilla's native Mojo API framework, replacing legacy backend code.
  • API utility cleanup: Shared helper code in Bugzilla::API::V1::Util has been reorganized following the migration, consolidating infrastructure for the new Mojo-based API layer.
  • Phabricator timestamp fix: Bug 2087000 addresses spurious last-modified timestamp updates in Phabricator revisions that occurred without substantive changes.
  • Notification testing: New database-backed tests cover flag-event bugmail recipient selection, specifically testing prev-status tie-breaking behavior and flag-type cc_list handling.

Why it matters

The Mojo API migration modernizes BMO's backend architecture, which serves as a reference deployment for the open-source Bugzilla project used by hundreds of organizations. Contributors and downstream maintainers should monitor this migration pattern, as Mojo-based APIs may become the standard for future Bugzilla development and could influence plugin and integration compatibility.

Original reference: discourse.mozilla.org →