Skip to content

Incorrect Babel version reported #24

@gaurav

Description

@gaurav

NodeNorm ES's /status endpoint returns both a babel_version and a babel_version_url based on it: https://nodenorm-es.ci.transltr.io/status

However, it currently returns 1.9, which is not a valid Babel version. I believe the data that you've currently loaded is the same as from NodeNorm Redis, which should be 2025sep1: https://nodenorm.ci.transltr.io/status

This is pretty important because ORION and DINGO use the babel_version field to determine when normalization is out of date and needs to be rerun, and the babel_version_url is useful for looking up the changelog.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions