Remove pending references to Travis

.github/maven-central-deploy.sh

@@ -3,7 +3,7 @@
 # This script takes care of deploying tagged versions to maven central and updating the pom.xml
 # version with next development version.
 #
-# Required environment variables: TRAVIS_TAG, GPG_SECRET_KEYS, GPG_OWNERTRUST, GPG_EXECUTABLE
+# Required environment variables: GPG_SECRET_KEYS, GPG_OWNERTRUST, GPG_EXECUTABLE
 
 set -eo pipefail
 

README.md

@@ -71,4 +71,4 @@ Then just run `mvn clean install` and the library (and standalone version) will
 ## Release
 
 To release the project, define the version to be released by checking included changes since last release and following [semantic versioning](https://semver.org/). 
-Then, create a [release](https://github.com/abstracta/wiresham/releases) (including `v` as prefix of the version, e.g. `v0.1`), this will trigger a Travis build which will publish the jars to maven central repository (and make it general available to be used as maven dependency projects) in around 10 mins and can be found in [maven central search](https://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22us.abstracta%22%20AND%20a%3A%22wiresham%22) after up to 2 hours.
+Then, create a [release](https://github.com/abstracta/wiresham/releases) (including `v` as prefix of the version, e.g. `v0.1`), this will trigger a GitHub Actions workflow which will publish the jars to maven central repository (and make it general available to be used as maven dependency projects) in around 10 mins and can be found in [maven central search](https://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22us.abstracta%22%20AND%20a%3A%22wiresham%22) after up to 2 hours.

pom.xml

@@ -6,7 +6,7 @@
   <groupId>us.abstracta</groupId>
   <artifactId>wiresham</artifactId>
   <!-- This version has no relation to the released version since the release version is extracted
-  from git tag by Travis -->
+  from git tag by github actions workflow -->
   <version>0.1-SNAPSHOT</version>
 
   <name>${project.artifactId}</name>