Tempo | v2.10.7

Tempo v2.10.7 released on 12-06-2026


Tempo v2.10.7 is out now. It fixes an incorrect build/version being reported by –version, the build-info metric and /api/status/buildinfo so operators and monitoring see consistent, accurate version strings.

See the Tempo release on GitHub for full details and downloads.

What’s in this release

  • Bugfix: Tempo now reads the build version from a top-level VERSION file instead of inferring it from the most recently created git tag, correcting incorrect version reports.
  • Distribution change: 32-bit ARM (armv7) binary archives are no longer published; release artifacts continue to include amd64 and arm64 binaries.
  • Operational guidance: no config changes are required; operators should validate the build-info metric and /api/status/buildinfo show the expected release string after upgrading.

Upgrade notes

  • No configuration changes required; after upgrading, verify /api/status/buildinfo and the build-info metric to confirm the corrected version string is exposed.
  • If you depend on 32-bit ARM binaries, build from source or migrate to arm64/amd64 images or environments; update package maintenance and CI pipelines that relied on prebuilt armv7 artifacts.

Share comments on the GitHub release or open an issue with any problems or observations after upgrading.

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