From 58e97994945cd008c589fef1b739850fd9285406 Mon Sep 17 00:00:00 2001
From: Sam Ford <1584702+samford@users.noreply.github.com>
Date: Mon, 31 Aug 2026 17:16:48 -0400
Subject: [PATCH] martin: update livecheck

The `livecheck` block for `martin` checks the Git tags and returns
0.15.0 as the newest version (from the `martin-v1.15.0` tag) but
there hasn't been a corresponding release on GitHub after three hours.
This updates the `livecheck` block to use the `GithubLatest` strategy,
as there can be a notable gap between tag and release. Upstream seems
to reliably mark only the main `martin-` tags as latest, so we
shouldn't run into issues with a release for something else being
"latest". If it ever happens, the `livecheck` block regex will ensure
the check fails.
---
 Formula/m/martin.rb | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Formula/m/martin.rb b/Formula/m/martin.rb
index 0bc6ff221803..10e18b12f130 100644
--- a/Formula/m/martin.rb
+++ b/Formula/m/martin.rb
@@ -5,9 +5,13 @@ class Martin < Formula
   sha256 "d75542ee0fa7f0f60975db856de39532035f981f187a6526b61f8b52e53e212b"
   license any_of: ["Apache-2.0", "MIT"]
 
+  # There can be a notable gap between when a version is tagged and a
+  # corresponding release is created, so we check the "latest" release instead
+  # of the Git tags.
   livecheck do
     url :stable
     regex(/^martin[._-]v?(\d+(?:\.\d+)+)$/i)
+    strategy :github_latest
   end
 
   bottle do