Build Numbers That Actually Make Sense: Branch-Scoped Sequence IDs in Harness CI | Harness Blog
You're tagging Docker images with build numbers. -Build is your latest production release on main. A developer pushes a hotfix to release-v2.1, that run becomes build. -Another merges to develop, build. A week later someone asks: "What build number are we on for production?" You check the registry. -You see,,, on main. The numbers in between? Scattered across feature branches that may never ship. Your build numbers have stopped telling a useful story.