LoginSign Up
← Back to all sparks
A

Amundsen

ANALYTICS
Velocity0.0

Data discovery and metadata engine for improving productivity of data analysts

www.amundsen.io ↗

Amundsen's last release was a config flag, and the feed has been silent for two years

data-catalogmetadatamaintenance-modemonorepo-releasesdependency-churn
◆Current state
Amundsen ships as several separately versioned components — databuilder, metadata, frontend, common — cut from one repository, and the release feed shows the same changelog republished under three different component tags on the same afternoon. Reading past the tag names, the content is overwhelmingly dependabot bumps, Python compatibility-matrix maintenance and mypy upgrades, with real features appearing a couple of times a year. The final release, databuilder 7.5.1 in August 2024, contains exactly one change: a config option for implicit transactions in the neo4j extractor.
◆Where it's heading
The direction is contraction. Python 3.7 support was dropped and the matrix narrowed to 3.8 and 3.9 before 3.10 was cautiously added to everything except the metadata service, contributor names moved to emeritus status, and organisations were removed from the README's adopter list. What feature work exists is small and peripheral — a PowerBI logo, aggregated alerts, a gremlin proxy method — rather than anything touching how the catalog works. Nothing has been published since August 2024.
◆Prediction
There is no signal in these entries of planned work, and a two-year silence following a single-flag release means the practical expectation is no further releases; the component version skew across databuilder, metadata and frontend is now frozen where it stopped.

◆Recent moves

  1. 1y ago

    Databuilder 7.5.1 adds implicit-transaction config for the neo4j extractor

    A single-change release adding a configuration option for implicit transactions in the neo4j extractor. It is the last entry in the feed, which makes a one-line extractor flag the project's final published release.

    View source ↗
  2. 2y ago

    Databuilder 7.5.0 is dependency bumps and a Python 3.10 matrix

    Dependabot upgrades for follow-redirects, express and jinja2, a mypy upgrade with the one type fix it surfaced, and Python 3.10 added to the compatibility matrix for every service except metadata. Housekeeping with no user-facing change, which is the shape of most releases here.

    View source ↗
  3. 2y ago

    Metadata 3.13.0 adds aggregating alerts and a gremlin proxy lookup

    The one release in this window with visible feature content: alert aggregation, a PowerBI dashboard logo, and a get_resources_using_table method on the metadata gremlin proxy. Python 3.7 support is dropped here and the matrix narrowed to 3.8 and 3.9, a contraction that the later 3.10 addition only partly reversed.

    View source ↗
  4. 2y ago

    Frontend 4.3.0 republishes the same changelog under a second tag

    Byte-for-byte the same changelog as metadata 3.13.0 and common 0.32.0, all three tagged within three minutes of each other. It is one release cut under three component version numbers rather than three separate pieces of work — worth knowing when reading this feed's cadence.

    View source ↗
  5. 2y ago

    Common 0.32.0 republishes the same changelog under a third tag

    The third tag carrying the identical March 2024 changelog, alongside metadata 3.13.0 and frontend 4.3.0. Amundsen's per-component versioning inflates the apparent release count without adding distinct content.

    View source ↗
  6. 2y ago

    Metadata 3.12.3 clears frontend dependency vulnerabilities

    A security-driven bump run across axios, browserify-sign, babel/traverse, postcss and wheel in the frontend's static assets. Typical of the releases that keep the shipped artifacts installable without changing the product.

    View source ↗