Consumers pinned to check-commits.yml@xmllint fail on every PR, regardless of their pom:
/home/runner/work/_temp/....sh: line 1: xmllint: command not found
VERSION=
libxml2-utils was dropped from the ubuntu-latest image. With VERSION empty, !endsWith(env.VERSION, '-SNAPSHOT') is true and the job calls core.setFailed('Version is not SNAPSHOT'). Seen on AppJars/appjars-utils, red on every PR since at least 2026-05-22.
Falling back to @main is not a workaround: its grep -oPm1 takes the parent version, which is #2.
Smallest change that closes both: keep the xpath and install the package.
- run: sudo apt-get install -y libxml2-utils
Then merge xmllint into main and drop the abandoned fix-1 / fix-2 / fix-2-xmllint branches, so consumers can pin to @main instead of tracking a work branch.
Worth noting FlowingCode/action-conventional-commits runs before this step, so commit message validation still works. The cost of leaving it red is that nobody can tell a bad commit message from the missing binary.
Related: #1, #2.
Consumers pinned to
check-commits.yml@xmllintfail on every PR, regardless of their pom:libxml2-utilswas dropped from theubuntu-latestimage. WithVERSIONempty,!endsWith(env.VERSION, '-SNAPSHOT')is true and the job callscore.setFailed('Version is not SNAPSHOT'). Seen on AppJars/appjars-utils, red on every PR since at least 2026-05-22.Falling back to
@mainis not a workaround: itsgrep -oPm1takes the parent version, which is #2.Smallest change that closes both: keep the xpath and install the package.
Then merge
xmllintintomainand drop the abandonedfix-1/fix-2/fix-2-xmllintbranches, so consumers can pin to@maininstead of tracking a work branch.Worth noting
FlowingCode/action-conventional-commitsruns before this step, so commit message validation still works. The cost of leaving it red is that nobody can tell a bad commit message from the missing binary.Related: #1, #2.