From 472414910ee6083a574c31a501ff2e3693fe6321 Mon Sep 17 00:00:00 2001
From: Carlos Amengual <carlosame644+github@gmail.com>
Date: Wed, 12 Apr 2023 21:38:45 +0200
Subject: [PATCH] Release 2.0.1

---
 RELEASE_HOWTO.md | 10 +++++-----
 UPGRADING.md     | 12 +++++++-----
 build.gradle     |  2 +-
 3 files changed, 13 insertions(+), 11 deletions(-)

diff --git a/RELEASE_HOWTO.md b/RELEASE_HOWTO.md
index ac49e37..b0e641f 100644
--- a/RELEASE_HOWTO.md
+++ b/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 `1.2.0`:
+changes from the latest tag. For example if you are releasing `2.0.1`:
 
 ```shell
-./changes.sh 1.2.0
+./changes.sh 2.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 1.2.0" and push.
+description like "Latest modular Javadocs after tokenproducer 2.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 v1.2.0 -m "Release 1.2.0"
-git push origin v1.2.0
+git tag -s v2.0.1 -m "Release 2.0.1"
+git push origin v2.0.1
 ```
 
 or `git tag -a` instead of `-s` if you do not plan to sign the tag. But it is
diff --git a/UPGRADING.md b/UPGRADING.md
index c33572e..749ea1f 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -1,7 +1,9 @@
 # Upgrading from 1.x
 
-Tokenproducer 2.0 replaces the methods `openGroup()` and `closeGroup()` with
-`leftParenthesis()`/`rightParenthesis()` and others. Using the new event methods
-may allow you to write clearer code, although you can also have your old
-`TokenHandler` implementation inherit from the new `LegacyTokenHandler`, which
-is compatible with the 1.x API and provides a simpler upgrade path.
+Tokenproducer 2.0.1 uses a new `TokenHandler2` interface which replaces the methods
+`openGroup()` and `closeGroup()` with `leftParenthesis()`/`rightParenthesis()`
+and others.
+
+Using the new event methods may allow you to write clearer code, although you can
+keep implementing the old 1.x `TokenHandler` interface, which provides a simpler
+upgrade path.
diff --git a/build.gradle b/build.gradle
index 839f9c6..6db4807 100644
--- a/build.gradle
+++ b/build.gradle
@@ -7,7 +7,7 @@ group = 'io.sf.carte'
 
 description = 'tokenproducer'
 
-version = '2.0'
+version = '2.0.1'
 
 dependencies {
 	testImplementation 'org.junit.jupiter:junit-jupiter:5.9.2'