cleanup

Author: lsoares

.github/workflows/publish.yml

@@ -7,8 +7,21 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+
+      - name: Setup JDK
+        uses: actions/setup-java@v3
+        with:
+          distribution: 'temurin'
+          java-version: '21'
+
+      - name: Setup OS
+        run: |
+          sudo apt-get update && sudo apt-get install -y gnupg2 expect
+
       - name: Test
-        uses: ./.github/test
+        run: ./gradlew test
 
       - name: Publish
         env:

.github/workflows/test/action.yml renamed to .github/workflows/test.yml

@@ -10,7 +10,6 @@ I'm a fan of the Testing Library because it encourages "testing as a user":
 > The more your tests resemble the way your software is used,
 > the more confidence they can give you.
 
-
 Pick
 the [library's latest version at Maven Central](https://search.maven.org/artifact/com.luissoares/selenium-testing-library).
 Then, copy the declaration for your build tool. E.g.:
@@ -20,7 +19,6 @@ implementation("com.luissoares:selenium-testing-library:3.7.7")
 ```
 
 ---
-
 These are just a few examples. Check [the tests](/lib/src/test/kotlin/seleniumtestinglib)
 that [illustrate](https://medium.com/codex/towards-self-documenting-code-371364bdccbb)
 all the usages.
@@ -85,5 +83,4 @@ val displayedValue = element.displayValue
 ```
 
 ---
-
 ℹ️ _[Read more](https://medium.com/codex/the-testing-library-meets-selenium-5f74cc712114)._

README.md

@@ -0,0 +1,9 @@
+#!/bin/sh
+
+version="$1"
+#sed -i "s/version = .*/version = ""$version""/g" lib/build.gradle.kts
+#sed -i "s/com\.luissoares:selenium-testing-library:[0-9]\+\.[0-9]\+\.[0-9]\+/com.luissoares:selenium-testing-library:$version/g" README.md
+git tag -l | xargs git tag -d
+git push --delete origin "v$version"
+git tag "v$version" -m "Tag release"
+git push origin "v$version"