Migration Guide 3.26

Table of Contents

• Legacy config classes support is gone

Note	We highly recommend the use of quarkus update to update to a new version of Quarkus. Items marked below with ⚙️ ✅ are automatically handled by quarkus update.

Legacy config classes support is gone

As announced previously, we retired the legacy config classes support in 3.26.

This change should only affect extension maintainers.

• @ConfigRoot should exclusively be used on interfaces in conjunction with @ConfigMapping - the deprecated attributes have also been removed

• @ConfigItem has been dropped as it was only used for legacy config classes

The extension annotation processor will also complain with an error if it encounters a legacy config class.

The compatibility legacy config classes we kept in 3.19-3.25 are also gone:

• GlobalDevServicesConfig: use DevServicesConfig instead

• HttpConfiguration: use VertxHttpConfig instead

• HttpBuildTimeConfig: use VertxHttpBuildTimeConfig instead

We recommend you base your extensions on 3.20 LTS now, and keep a maintenance branch for 3.15 LTS if you think it’s required for your extension.