Observation (at 2022-08-13 20:06):
<flow.version>23.1.4</flow.version>
Releases:
So the release cycles do not seem to be synchronized.
pom.xml: The only place where the vaadin version is set in my pom.xml is here:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-bom</artifactId>
<version>${com.vaadin.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
Question:
This mix works, but would it be better to enforce same versions?
If the difference in versions is intended: why does it exist?
As stated in the discussion, the versions are not exact to maintenance versions. The minor difference here is just an implementation detail. You should always check the release notes for the correctly matching dependencies if you for some reason need to set versions manually instead of using BOM.