Release 2.0.2

RELEASE_HOWTO.md

@@ -40,10 +40,10 @@ cd /path/to/tokenproducer
 ```
 
 5) Use `changes.sh <new-version>` to create a `CHANGES.txt` file with the
-changes from the latest tag. For example if you are releasing `2.0.1`:
+changes from the latest tag. For example if you are releasing `3.0.1`:
 
 ```shell
-./changes.sh 2.0.1
+./changes.sh 3.0.1
 ```
 
 Edit the resulting `CHANGES.txt` as convenient, to use it as the basis for the
@@ -83,7 +83,7 @@ mv /path/to/css4j-dist/build/docs/javadoc/* /path/to/css4j.github.io/api/latest
 ```
 
 If the changes to the `css4j.github.io` repo look correct, commit them with a
-description like "Latest modular Javadocs after tokenproducer 2.0.1" and push.
+description like "Latest modular Javadocs after tokenproducer 3.0.1" and push.
 
 Check whether the ["Examples" CI](https://github.com/css4j/css4j.github.io/actions/workflows/examples.yml)
 triggered by that commit to the `css4j.github.io` repository completed
@@ -94,8 +94,8 @@ for example.
 
 ```shell
 cd /path/to/tokenproducer
-git tag -s v2.0.1 -m "Release 2.0.1"
-git push origin v2.0.1
+git tag -s v3.0.1 -m "Release 3.0.1"
+git push origin v3.0.1
 ```
 
 or `git tag -a` instead of `-s` if you do not plan to sign the tag. But it is

build.gradle

@@ -7,7 +7,7 @@ group = 'io.sf.carte'
 
 description = 'tokenproducer'
 
-version = '2.0.2-SNAPSHOT'
+version = '2.0.2'
 
 dependencies {
 	testImplementation 'org.junit.jupiter:junit-jupiter:5.10.0'