Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?As mentioned in #158963 (comment),
urdfdom
uses tags to indicate a new version, despite upstream having created a few GitHub releases in the past. This adds alivecheck
block using the same approach (and comment) from #158963, to alignurdfdom_headers
.livecheck already checks the Git tags for
urdfdom_headers
by default and returns 1.1.1 as the newest version but the matches also include a one-offh
match (from thepass_through
tag). Using the standard regex for Git tags like1.2.3
/v1.2.3
(/^v?(\d+(?:\.\d+)+)$/i
) avoids that unwanted tag.