I cannot trust the README as a reliable source for the correct dependency version. The Maven snippet shown to users is hardcoded to 0.1.0, which is far behind the current release — anyone copying it will pull a very old version of the library.
<dependency>
<groupId>org.eolang</groupId>
<artifactId>lints</artifactId>
<version>0.1.0</version>
</dependency>
We need to either add a new CI/CD pipeline step or fix the existing release workflow to automatically inject the correct version into the README snippet on every release, similar to what many other projects do with a simple sed replacement during the release job.
The Maven Central badge already shows the correct version dynamically, so the mismatch makes the README look inconsistent and unreliable.
I cannot trust the README as a reliable source for the correct dependency version. The Maven snippet shown to users is hardcoded to
0.1.0, which is far behind the current release — anyone copying it will pull a very old version of the library.We need to either add a new CI/CD pipeline step or fix the existing release workflow to automatically inject the correct version into the README snippet on every release, similar to what many other projects do with a simple
sedreplacement during the release job.The Maven Central badge already shows the correct version dynamically, so the mismatch makes the README look inconsistent and unreliable.