smallrye-graphql: UnauthorizedException is hidden behind DataFetcherException in Quarkus 1.6

We have @Mutation method annotated with @Authenticated and JWT configured in our Quarkus app. In Quarkus 1.5 GraphQL response reported io.quarkus.security.UnauthorizedException if JWT token was missing in request. After update to Quarkus 1.6 it is changed to io.smallrye.graphql.execution.datafetcher.DataFetcherException and error message is “Server Error” and there is not any indication for caller what is really wrong. It makes GraphQL API harder to use I believe, error reporting should be clear in this case, this is definitely not a server error but caller’s problem, so he should know what is wrong to be able to call API correctly.