Vaadin 24.10.8 requires license not required by 24.10.7

Ever since the vaadin 24.10.8 upgrade a couple of our services stopped building in CI/CD.

I can generally reproduce the error by running gradle vaadinBuildFrontend on the repo of an affected service, plusminus ensuring no caching issues.

The error we get is, generally, this one:

Caused by: com.vaadin.pro.licensechecker.LicenseException: Unable to validate the license, please check your internet connection. If you need to work offline then please go to https://vaadin.com/pro/validate-license?getOfflineKey=mid2-… to retrieve an offline key.

For CI/CD build servers, you need to download a server license key, which can work offline to create production builds. You can download a server license key from https://vaadin.com/myaccount/licenses.

For troubleshooting steps, see Vaadin licensing FAQ and troubleshooting.

When I downgrade to 24.10.7 I can build my services again, no license required.

I attempted to check if the catalog of paid components changed between 24.10.7 and 24.10.8 but was not able to find anything to that effect.

I generally expect that minor / patch version changes do not cause changes in licensing, but it wouldn’t be the first breaking change in a minor / patch version I’ve had to deal with.

I’ve suspected, for a while, that vaadin may have just changed the way they check for licenses. And it is true, that 24.10.8 comes with license-checker 3.0.3 whereas 24.10.7 comes with license-checker 3.0.1 (or .2).
But I’ve tested running 24.10.8 with license-checker 3.0.1 and saw no changes. Same for 24.10.7 with license-checker 3.0.3.

So, anyone know what could be going on here?

Free maintenance for 24.x ended in June. So it makes total sense that latest 24.10.8 released in July requires a license.

1 Like

Thank you everyone, that seems like a likely explanation. I guess our Vaadin 25 upgrade plans just got upped in priority!

If you run on Spring (Boot) you should definitely plan an upgrade. Spring Boot 3.5 is also EoL (free support)

2 Likes

It is not just likely, but the explanation.

At Vaadin we continue maintaining legacy versions from Vaadin 7 to Vaadin 24 under commercial license after EOL. To be exact, the major versions under that program are Vaadin 7, 8, 14, 23 and now 24 too.

The commercial releases get security updates, dependency updates, selected bug fixes and minor feature updates based on our customer demand.

Broadcom has similar option available for Spring Boot 2 and 3, but our commercial support extends typically longer.

Checking Vaadin 25 upgrade path is the right natural step for you. We have had quite stable upgrade path with Vaadin versions from 14 to 25. The need for refactoring Vaadin code is usually quite small effort. Our newer major versions however require newer Servlet API, Spring and Java versions. Some difficulty upgrading those is the most common reason to opt-in our commercial plan.

Thank you for the confirmation. We were already planning to upgrade to vaadin 25 in the near future, so that looks like a good way forward for us.