Skip to content

Commit 1cbfecb

Browse files
committed
Release 5.1
1 parent 8978b12 commit 1cbfecb

File tree

3 files changed

+19
-19
lines changed

3 files changed

+19
-19
lines changed

RELEASE_HOWTO.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -26,10 +26,10 @@ For reference, let your copy of the css4j-dom4j release code be at
2626
`/path/to/css4j-dom4j`.
2727

2828
2) Execute `./changes.sh <new-version>` to create a `CHANGES.txt` file with the
29-
changes from the latest tag. For example if you are releasing `4.1`:
29+
changes from the latest tag. For example if you are releasing `5.1.1`:
3030

3131
```shell
32-
./changes.sh 4.1
32+
./changes.sh 5.1.1
3333
```
3434

3535
Edit the resulting `CHANGES.txt` as convenient and use it as the basis to update
@@ -86,7 +86,7 @@ mv /path/to/css4j-dist/build/docs/javadoc/* /path/to/css4j.github.io/api/latest
8686
```
8787

8888
If the changes to the `css4j.github.io` repo look correct, commit them with a
89-
description like "Latest modular Javadocs after css4j-dom4j 4.1" and push.
89+
description like "Latest modular Javadocs after css4j-dom4j 5.1.1" and push.
9090

9191
Check whether the ["Examples" CI](https://github.com/css4j/css4j.github.io/actions/workflows/examples.yml)
9292
triggered by that commit to the `css4j.github.io` repository completed
@@ -97,8 +97,8 @@ for example.
9797

9898
```shell
9999
cd /path/to/css4j-dom4j
100-
git tag -s v4.1 -m "Release 4.1"
101-
git push origin v4.1
100+
git tag -s v5.1.1 -m "Release 5.1.1"
101+
git push origin v5.1.1
102102
```
103103

104104
or `git tag -a` instead of `-s` if you do not plan to sign the tag. But it is

RELEASE_NOTES.md

+13-13
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,28 @@
1-
# css4j-dom4j version 5.0 Release Notes
1+
# css4j-dom4j version 5.1 Release Notes
22

3-
### October 5, 2024
3+
### January 24, 2025
44

55
<br/>
66

77
## Release Highlights
88

9-
### Major version bumped to 5
9+
### Test suite updated for css4j 5.1
1010

11-
To emphasize that it is compatible with css4j 5.0, major version was bumped to 5.
11+
This library is the same as 5.0 except for the test suite, which was modified
12+
for compatibility with the new `attr()` syntax supported by css4j 5.1.
13+
14+
There is no need for upgrading unless you want to run the supplied tests.
1215

1316
<br/>
1417

1518
## Detail of changes
1619

17-
- Override `createElement(String, String)` in `XHTMLDocumentFactory`.
18-
- Tests: add selector matcher tests.
19-
- Upgrade to actions/setup-java v4.
20-
- Default to Linux line endings for source files.
21-
- Set up CodeQL analysis.
22-
- Upgrade JUnit to version 5.11.1.
23-
- Upgrade Gradle wrapper to 8.10.2.
24-
- Upgrade to extra-java-module-info version 1.9.
25-
- Bump copyright year to 2024.
20+
- Upgrade to css4j 5.1, adapt tests accordingly.
21+
- Upgrade to slf4j 2.0.16.
22+
- Upgrade to JUnit 5.11.4.
23+
- Gradle: use the assignment operator in the maven repo section.
24+
- Upgrade Gradle wrapper to 8.12.1.
25+
- Bump year to 2025 in copyright notices.
2626

2727
<br/>
2828

build.gradle

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ plugins {
55
}
66

77
group = 'io.sf.carte'
8-
version = '5.1-SNAPSHOT'
8+
version = '5.1'
99

1010
description = 'css4j-dom4j'
1111

0 commit comments

Comments
 (0)