Skip to content

Commit ca7ab08

Browse files
committed
flagd: add livecheck
We noticed in a recent version bump PR for `flagd` that upstream only appears to mark `core/v1.2.3` releases as "latest", not releases like `flagd/v1.2.3`. This adds a `livecheck` block that checks the `flagd/v1.2.3` tags, omitting unrelated tags. This also adds a comment to explain the situation, so hopefully maintainers will know not to wait for a `flagd` version to be marked as "latest".
1 parent de1dcda commit ca7ab08

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

Formula/f/flagd.rb

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@ class Flagd < Formula
77
license "Apache-2.0"
88
head "https://github.com/open-feature/flagd.git", branch: "main"
99

10+
# The upstream repository contains tags like `core/v1.2.3`,
11+
# `flagd-proxy/v1.2.3`, etc. but we're only interested in the `flagd/v1.2.3`
12+
# tags. Upstream only appears to mark the `core/v1.2.3` releases as "latest"
13+
# and there isn't usually a notable gap between tag and release, so we check
14+
# the Git tags.
15+
livecheck do
16+
url :stable
17+
regex(%r{^flagd/v?(\d+(?:[.-]\d+)+)$}i)
18+
end
19+
1020
bottle do
1121
sha256 cellar: :any_skip_relocation, arm64_sequoia: "73249d24d5e23dc79af8aa5a73b15afdeb956d0fa0eaaf4f1d4cc09f4ec39dda"
1222
sha256 cellar: :any_skip_relocation, arm64_sonoma: "73249d24d5e23dc79af8aa5a73b15afdeb956d0fa0eaaf4f1d4cc09f4ec39dda"

0 commit comments

Comments
 (0)