Changelogs » Glean-parser

PyUp Safety actively tracks 316,954 Python packages for vulnerabilities and notifies you when to upgrade.



- Add a command `data-review` to generate a skeleton Data Review Request for all metrics matching a supplied bug number. ([bug 1704541](
  - Enable custom distribution outside of GeckoView (`gecko_datapoint` becomes optional)


- Transform generated folder into QML Module when building Javascript templates for the Qt platform. ([bug 1707896](
  - Import the Glean QML module from inside each generated file, removing the requirement to import Glean before importing any of the generated files;
  - Prodive a `qmldir` file exposing all generated files;
  - Drop the `namespace` option for Javascript templates;
  - Add a new `version` option for Javascript templates, required when building for Qt, which expected the Glean QML module version.


- Add missing import for Kotlin code ([339](
  - Use a plain Kotlin type in the generated interface implementation ([339](
  - Generate additional generics for event metrics ([339](
  - For Kotlin skip generating `GleanBuildInfo.kt` when requested (with `with_buildinfo=false`) ([341](


- Fix another bug in the Swift code generation when generating extra keys ([334](


- Fix Swift code generation bug for pings ([333](


- Generate new event API construct ([321](


- Add option to add extra introductory text to generated markdown ([298](
  - Add support for Qt in Javascript templates ([bug 1706252](
  - Javascript templates will now accept the `platform` option. If this option is set to `qt`
  the generated templates will be Qt compatible. Default value is `webext`.


- BUGFIX: Remove the "DO NOT COMMIT" notice from the documentation.


- Recommend to not commit as well as to not edit the generated files. ([bug 1706042](
  - BUGFIX: Include import statement for labeled metric subtypes in Javascript and Typescript templates.


- Add support for labeled metric types in Javascript and Typescript templates.


- Raise limit on number of statically-defined lables to 100. ([bug 1702263](
  - BUGFIX: Version 2.0.0 of the schema now allows the "special" `glean_.*` ping names for Glean-internal use again.
  - Remove support for JWE metric types.


- Add parser and object model support for `rate` metric type. ([bug 1645166](
  - Add parser and object model support for telemetry_mirror property. ([bug 1685406](
  - Update the Javascript template to match Glean.js expectations. ([bug 1693516](
  - Glean.js has updated it's export strategy. It will now export each metric type as an independent module;
  - Glean.js has dropped support for non ES6 modules.
  - Add support for generating Typescript code. ([bug 1692157](
  - The templates added generate metrics and pings code for Glean.js.


- **Experimental:** `glean_parser` has a new subcommand `coverage` to convert raw coverage reports
  into something consumable by coverage tools, such as
  - The path to the file that each metric is defined in is now stored on the
  `Metric` object in `defined_in["filepath"]`.


- Leverage the `glean_namespace` to provide correct import when building for Javascript.


- The Kotlin generator now generates static build information that can be passed
  into `Glean.initialize` to avoid calling the package manager at runtime.


- Add support for generating Javascript code.
  - The templates added generate metrics and pings code for Glean.js.


- New versions 2.0.0 of the `metrics.yaml` and `pings.yaml` schemas now ship
  with `glean_parser`. These schemas are different from version 1.0.0 in the
  following ways:
  - Bugs must be specified as URLs. Bug numbers are disallowed.
  - The legacy ping names containing underscores are no longer allowed. These
  included `deletion_request`, `bookmarks_sync`, `history_sync`,
  `session_end`, `all_pings`, `glean_*`). In these cases, the `_` should be
  replaced with `-`.
  To upgrade your app or library to use the new schema, replace the version in
  the `$schema` value with `2-0-0`.
  - **Breaking change:** It is now an error to use bug numbers (rather than URLs)
  in ping definitions.
  - Add the line number that metrics and pings were originally defined in the yaml


- BUGFIX: Linter output can now be redirected correctly (1675771).


- **Breaking change:** `glean_parser` will now return an error code when any of
  the input files do not exist (unless the `--allow-missing-files` flag is
  - Generated code now includes a comment next to each metric containing the name
  of the metric in its original `snake_case` form.
  - When metrics don't provide a `unit` parameter, it is not included in the
  output (as provided by probe-scraper).


- BUGFIX: Ensure Kotlin arguments are deterministically ordered


- Fix deploy step to update pip before deploying to pypi.


- The `SUPERFLUOUS_NO_LINT` warning has been removed from the glinter.
  It likely did more harm than good, and makes it hard to make
  `metrics.yaml` files that pass across different versions of
  - Expired metrics will now produce a linter warning, `EXPIRED_METRIC`.
  - Expiry dates that are more than 730 days (\~2 years) in the future
  will produce a linter warning, `EXPIRATION_DATE_TOO_FAR`.
  - Allow using the Quantity metric type outside of Gecko.
  - New parser configs `custom_is_expired` and `custom_validate_expires`
  added. These are both functions that take the `expires` value of the
  metric and return a bool. (See `Metric.is_expired` and
  `Metric.validate_expires`). These will allow FOG to provide custom
  validation for its version-based `expires` values.


- BUGFIX: Support HashSet and Dictionary in the C\ generated code.


- BUGFIX: Generate valid C\ code when using Labeled metric types.


- BUGFIX: Add missing column to correctly render markdown tables in generated


- **Breaking change:** The internal ping `deletion-request` was misnamed in causing the linter to not allow use of the correctly named ping for
  adding legacy ids to. Consuming apps will need to update their metrics.yaml if
  they are using `deletion_request` in any `send_in_pings` to `deletion-request`
  after updating.


- Rename the `data_category` field to `data_sensitivity` to be clearer.


- Add support for JWE metric types.
  - Add a `data_sensitivity` field to all metrics for specifying the type of data
  collected in the field.


- Add support for generating C\ code.
  - BUGFIX: The memory unit is now correctly passed to the MemoryDistribution
  metric type in Swift.


- BUGFIX: look for metrics in send\_if\_empty pings. Metrics for these kinds of
  pings were being ignored.


- Support for Python 3.5 has been dropped.
  - BUGFIX: The ordering of event extra keys will now match with their enum,
  fixing a serious bug where keys of extras may not match the correct values in
  the data payload. See <>.


- **Breaking change:** (Swift only) Combine all metrics and pings into a single
  generated file `Metrics.swift`.


- `glinter` messages have been improved with more details and to be more
  - A maximum of 10 `extra_keys` is now enforced for `event` metric types.
  - BUGFIX: the `Lifetime` enum values now match the values of the implementation
  in mozilla/glean.


- BUGFIX: yamllint errors are now reported using the correct file name.


- Support for using `timing_distribution`'s `time_unit` parameter to control
  the range of acceptable values is documented. The default unit for this use
  case is `nanosecond` to avoid creating a breaking change. See [bug
  1630997]( for more


- Dependencies that depend on the version of Python being used are now specified
  using the [Declaring platform specific dependencies syntax in
  This means that more recent versions of dependencies are likely to be
  installed on Python 3.6 and later, and unnecessary backport libraries won't
  be installed on more recent Python versions.


- The minimum version of the runtime dependencies has been lowered to increase
  compatibility with other tools. These minimum versions are now tested in CI,
  in addition to testing the latest versions of the dependencies that was
  already happening in CI.


- **Breaking change:** glinter errors found during the `translate` command will
  now return an error code. glinter warnings will be displayed, but not return
  an error code.
  - `glean_parser` now produces a linter warning when `user` lifetime metrics are
  set to expire. See [bug
  1604854]( for additional


- **Breaking change:** The regular expression used to validate labels is
  stricter and more correct.
  - Add more information about pings to markdown documentation:
  - State whether the ping includes client id;
  - Add list of data review links;
  - Add list of related bugs links.
  - `glean_parser` now makes it easier to write external translation
  functions for different language targets.
  - BUGFIX: `glean_parser` now works on 32-bit Windows.


- Dropped the `inflection` dependency.
  - Constrained the `zipp` and `MarkupSafe` transitive dependencies to versions
  that support Python 3.5.


- BUGFIX: Fix rendering of first element of reason list.


- BUGFIX: Reason codes are displayed in markdown output for built-in
  pings as well.
  - BUGFIX: Reason descriptions are indented correctly in markdown
  - BUGFIX: To avoid a compiler error, the `JvmName` annotation isn't
  added to private members.


- **Breaking Change (Java API)** Have the metrics names in Java match the names
  in Kotlin. See [Bug
  - The reasons a ping are sent are now included in the generated markdown


- BUGFIX: The version of Jinja2 now specifies < 3.0, since that version no
  longer supports Python 3.5.


- BUGFIX: Fixes an import error in generated Kotlin code.


- BUGFIX: Generated Swift code now includes `import Glean`, unless generating
  for a Glean-internal build.


- Remove default schema URL from `validate_ping`
  - Make `schema` argument required for CLI
  - BUGFIX: Avoid default import in Swift code for Glean itself
  - BUGFIX: Restore order of fields in generated Swift code


- Support for `reason` codes on pings was added.


- BUGFIX: The version of Jinja2 now specifies < 3.0, since that version no
  longer supports Python 3.5 (backported from 1.17.3).


- BUGFIX: Also allow the legacy name `all_pings` for `send_in_pings` parameter
  on metrics


- BUGFIX: Also allow the legacy name `all_pings`


- Add project title to markdown template.
  - Remove "Sorry about that" from markdown template.
  - BUGFIX: Replace dashes in variable names to force proper naming


- BUGFIX: Use a pure Python library for iso8601 so there is no compilation


- BUGFIX: Add some additional ping names to the non-kebab-case allow list.


- Restrict new pings names to be kebab-case and change `all_pings` to


- `glean_parser` now supports Python versions 3.5, 3.6, 3.7 and 3.8.


- The `translate` command will no longer clear extra files in the output
  - BUGFIX: Ensure all newlines in comments are prefixed with comment markers
  - BUGFIX: Escape Swift keywords in variable names in generated code
  - Generate documentation for pings that are sent if empty


- Reserve the `deletion_request` ping name
  - Added a new flag `send_if_empty` for pings


- The `glinter` command now performs `yamllint` validation on registry files.


- The Kotlin linter `detekt` is now run during CI, and for local
  testing if installed.
  - Python 3.8 is now tested in CI (in addition to Python 3.7). Using
  `tox` for this doesn't work in modern versions of CircleCI, so the
  `tox` configuration has been removed.
  - `yamllint` has been added to test the YAML files on CI.
  - ⚠ Metric types that don't yet have implementations in glean-core
  have been removed. This includes `enumeration`, `rate`, `usage`, and
  `use_counter`, as well as many labeled metrics that don't exist.


- Allow a Swift lint for generated code
  - New lint: Restrict what metric can go into the `baseline` ping
  - New lint: Warn for slight misspellings in ping names
  - BUGFIX: change Labeled types labels from lists to sets.


- Use lists instead of sets in Labeled types labels to ensure that the order of
  the labels passed to the `metrics.yaml` is kept.
  - `glinter` will now check for duplicate labels and error if there are any.


- Add labels from Labeled types to the Extra column in the Markdown template.


- BUGFIX: Don't call `is_internal_metric` on `Ping` objects.


- Don't include Glean internal metrics in the generated markdown.


- Glinter now warns when bug numbers (rather than URLs) are used.
  - BUGFIX: add `HistogramType` and `MemoryUnit` imports in Kotlin generated code.


- Removed unsupported labeled metric types.


- Fix indentation for generated Swift code


- Created labeled metrics and events in Swift code and wrap it in a
  configured namespace


- BUGFIX: `memory_unit` is now passed to the Kotlin generator.


- A new parser config, `do_not_disable_expired`, was added to turn off the
  feature that expired metrics are automatically disabled. This is useful if you
  want to retain the disabled value that is explicitly in the `metrics.yaml`
  - `glinter` will now report about superfluous `no_lint` entries.


- A `glinter` tool is now included to find common mistakes in metric naming
  and setup. This check is run during `translate` and warnings will be
  displayed. ⚠ These warnings will be treated as errors in a future revision.


- BUGFIX: `GleanGeckoMetricsMapping` must include `LabeledMetricType`
  and `CounterMetricType`.


- NEW: Support for outputting metrics in Swift.
  - BUGFIX: Provides a helpful error message when `geckoview_datapoint` is used on
  an metric type that doesn't support GeckoView exfiltration.
  - Generate a lookup table for Gecko categorical histograms in
  - Introduce a 'Swift' output generator.


- Documentation only.


- Added support for generating markdown documentation from `metrics.yaml` files.


- `quantity` metric type has been added.


- BUGFIX: `includeClientId` was not being output for PingType.


- `memory_distribution` metric type has been added.
  - `custom_distribution` metric type has been added.
  - `labeled_timespan` is no longer an allowed metric type.


-   Add a special `all_pings` value to `send_in_pings`.


- First release to start following strict semver.


- First release on PyPI.