Glean-parser

Latest version: v16.2.0

Safety actively analyzes 701475 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 14 of 24

2.0.0

- 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
files.

1.29.1

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

1.29.0

- **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
passed).
- 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).

1.28.6

- BUGFIX: Ensure Kotlin arguments are deterministically ordered

1.28.5

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

1.28.4

- 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
`glean_parser`.
- 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.

Page 14 of 24

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.