Vaadin doesn't show up after upgrade from 23.2.10 to 23.3.1

Intention: I want to switch from Vaadin 23.2.10 to 23.3.1.

What I did: In the pom.xml I changed Vaadin version from 23.2.10 to 23.3.1.

What happened: After that the application (Spring Boot plus Vaadin) starts, but the UI doesn't show up. Instead I see this message:

Question: Is there anything special to migrate between these versions? The guide at https://vaadin.com/blog/vaadin-23.3-kubernetes-cloud-new-ui-components just says "Update the Vaadin version in your pom.xml to 23.3.0 if you are on Vaadin 23.2.x."

What I tried and additional observations:

• Thanks to virtualization I've got the same development environment multiple times. When leaving Vaadin at version 23.2.10 everything works fine. Just after switching to 23.3.1 (or 23.3.0) the UI doesn't show up any more.

• When switching from 23.3.1/23.3.0 back to 23.2.10 then the UI starts but there shows up an error message in the UI: "

   [TypeScript] Cannot find module '@vaadin/tooltip' or its corresponding type declarations.
   /home/[mypath]/frontend/generated/jar-resources/tooltip.ts:1:25
     > 1 | import { Tooltip } from '@vaadin/tooltip';
         |                         ^^^^^^^^^^^^^^^^^
       2 |
       3 | const _window = window as any;
       4 | _window.Vaadin = _window.Vaadin || {};
  

• Deleting the folders .m2/com/vaadin and node_modules and the package.json and package-lock.json does not help: the 404 error behavior still occurs with version 23.3.x.

• In a well working application (with Vaadin 23.2.10 without ever trying to upgrade) there is a message in the console at startup: "Vaadin application has been deployed and started to the context path "/".". This message is missing with the 23.3.x releases.

As noted from the release notes Spring Boot 2.7.x is needed to run the latest Vaadin 23.3.x.

Vaadin 23.3.x can't register its custom Servlet with Spring Boot <= 2.6.x, because it switched to the new / non-deprecated @AutoConfiguration available since Spring Boot 2.7.0 to prepare for Spring Boot 3.0 where the old mechanism is completely removed.