Following the discussion in https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/thread/..., I've moved the wildfly/wildfly 'main' branch to SE 17 as its baseline. So, going forward standard WildFly will require SE 17 at runtime in new major releases. This means we can now use SE 17 dependencies outside of WildFly Preview, and we can use SE 12-17 language features and SE APIs. As noted in https://www.wildfly.org/news/2024/10/28/WildFly-moves-to-SE-17/, if you're consuming WildFly's nightly builds or building WildFly snapshots in some workflow, you'll need to move that to use SE 17 or later. WildFly 34.x releases (aka 34.0.1) will still support SE 11. Best regards, -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His