From 55f28afcdc2954190469bd74b83cf2f0b3426bde Mon Sep 17 00:00:00 2001 From: unknown Date: Fri, 21 Jun 2024 17:54:35 -0400 Subject: [PATCH] Fixing link --- content/posts/stamping-builds-with-bazel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/stamping-builds-with-bazel.md b/content/posts/stamping-builds-with-bazel.md index d60751e..e6d9464 100644 --- a/content/posts/stamping-builds-with-bazel.md +++ b/content/posts/stamping-builds-with-bazel.md @@ -15,7 +15,7 @@ tags: --- ## What am I Doing? -In my [last post](/2024/03/the-joy-of-versioning/) I spent some time talking about how more rigorous versioning helped reduce wasted time debugging and upgrading code as it started getting broken into lots of little pieces. +In my [last post](/2024/09/the-joy-of-versioning/) I spent some time talking about how more rigorous versioning helped reduce wasted time debugging and upgrading code as it started getting broken into lots of little pieces. That post was pretty light on direct `bazel` usage but I promise, it'll pay off. Here, we're going to cover how to use these tags *in* your builds to tag docker images or inject build information into compiled binaries.