Skip to content

Commit

Permalink
Release 2.0.1
Browse files Browse the repository at this point in the history
  • Loading branch information
carlosame committed Apr 12, 2023
1 parent fba9a35 commit 4724149
Show file tree
Hide file tree
Showing 3 changed files with 13 additions and 11 deletions.
10 changes: 5 additions & 5 deletions RELEASE_HOWTO.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down
12 changes: 7 additions & 5 deletions UPGRADING.md
Original file line number Diff line number Diff line change
@@ -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.
2 changes: 1 addition & 1 deletion build.gradle
Original file line number Diff line number Diff line change
Expand Up @@ -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'
Expand Down

0 comments on commit 4724149

Please sign in to comment.