This release is meant to include a fix on the Canton side. Because of (#14888)

how our release process works at the moment, this means we have to
create a new release on this side too, even though there is no code
change.

So it is totally expected at this point that the 2.3.4 line points to
the same commit as the 2.3.3 line, even though it looks a bit strange.

CHANGELOG_BEGIN
CHANGELOG_END
This commit is contained in:
mziolekda 2022-09-01 10:40:04 +02:00 committed by GitHub
parent 4b574ac393
commit 111c2c2645
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

1
LATEST
View File

@ -1,3 +1,4 @@
f529a2a0159e97aa8f74bff7794b07785fdda6c0 2.3.4 SPLIT_RELEASE
f529a2a0159e97aa8f74bff7794b07785fdda6c0 2.3.3 SPLIT_RELEASE
f529a2a0159e97aa8f74bff7794b07785fdda6c0 2.3.2 SPLIT_RELEASE
f529a2a0159e97aa8f74bff7794b07785fdda6c0 2.3.1 SPLIT_RELEASE