Release 3.7

Author: carlosame

RELEASE_HOWTO.md

@@ -40,10 +40,10 @@ cd /path/to/carte-util
 ```
 
 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 `3.6.1`:
+changes from the latest tag. For example if you are releasing `3.7.1`:
 
 ```shell
-./changes.sh 3.6.1
+./changes.sh 3.7.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 carte-util 3.6.1" and push.
+description like "Latest modular Javadocs after carte-util 3.7.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/carte-util
-git tag -s v3.6.1 -m "Release 3.6.1"
-git push origin v3.6.1
+git tag -s v3.7.1 -m "Release 3.7.1"
+git push origin v3.7.1
 ```
 
 or `git tag -a` instead of `-s` if you do not plan to sign the tag. But it is

build.gradle

@@ -1,3 +1,12 @@
+/*
+
+ Copyright (c) 2021-2025, C. Amengual.
+
+ Licensed under a BSD-style License. You can find the license here:
+ https://css4j.github.io/LICENSE.txt
+
+ */
+
 plugins {
 	id 'java-library'
 	id 'maven-publish'
@@ -7,7 +16,7 @@ group = 'io.sf.carte'
 
 description = 'carte-util'
 
-version = '3.6.1-SNAPSHOT'
+version = '3.7'
 
 sourceSets {
 	main {