Tempo | v2.10.7

Tempo v2.10.7 released on 12-06-2026


Tempo v2.10.7 is out now. It fixes incorrect build/version reporting in –version, the build-info metric and /api/status/buildinfo so operators and monitoring tools see consistent, accurate build information.

For full details and downloadable artifacts see the GitHub release: https://api.github.com/repos/grafana/tempo/releases/latest

What’s in this release

  • Fix: Tempo now reads the build version from a new top-level VERSION file instead of the most-recently-created git tag, correcting –version, the build-info metric and /api/status/buildinfo.
  • Change: official release artifacts no longer include 32-bit ARM (armv7/386); published binaries are amd64 and arm64 only.
  • Advice: verify any automation or monitoring that parses /api/status/buildinfo or the build-info metric after upgrading; plan for 32-bit ARM deployments.

Upgrade notes

  • Dropped 32-bit ARM binaries — if you deploy on armv7/386, build Tempo from source or migrate to arm64/amd64.
  • Rollback: if you need to revert, use previously built 32-bit ARM binaries or rebuild them from source and check any tooling that reads build-info.

Share your experience or report issues on the Grafana Tempo GitHub so others can learn from any upgrade snags.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes