Custom NotNull annotations stopped working between 2.2.28 and 2.2.29

I'm using springdoc to generate OpenAPI documents for my application. In order to generate improved error messages, I'm using my own @NotNull annotations instead of jakarta.validation.constraints.NotNull. This was working fantastic for me until swagger v2.2.29, when my @NotNull annotations stopped generating the appropriate required fields.

See more details here: https://github.com/springdoc/springdoc-openapi/issues/3004#issuecomment-2955732679.

Ideally I would like the previous behavior reinstated where I can use any annotation with the name NotNull to mark required fields.

If that does not happen, are there any extension points I can use to keep my model generation working? I have hundreds of models annotated with @NotNull, and maintaining this is essential for my api clients to work correctly.

Start by comparing swagger versions 2.2.28 and 2.2.29, then review the linked springdoc issue comment for the changed custom @NotNull behavior. Trace how annotations are recognized during model generation and determine whether prior required-field output can be restored or an extension point can support existing models.