Summary of Suggested Changes

Patch

1. Bump dependency versions to latest. https://github.com/OpenAPITools/jackson-databind-nullable/issues/60 https://github.com/OpenAPITools/jackson-databind-nullable/pull/64 https://github.com/OpenAPITools/jackson-databind-nullable/pull/59 https://github.com/OpenAPITools/jackson-databind-nullable/pull/52
2. Setup Renovate or something similar for long term maintenance. https://github.com/OpenAPITools/jackson-databind-nullable/issues/71#issuecomment-3270770186
3. Update GitHub Actions to use commit sha instead of version numbers (security improvement of workflows).
4. Test on Java 8 and latest Java version to ensure compatibility as versions are released.

Minor

1. Add methods to JsonNullable to make use with streaming APIs easier. https://github.com/OpenAPITools/jackson-databind-nullable/issues/65 https://github.com/OpenAPITools/jackson-databind-nullable/pull/68 https://github.com/OpenAPITools/jackson-databind-nullable/pull/56 https://github.com/OpenAPITools/jackson-databind-nullable/issues/7
2. Improve module-info. (Could be major if the module name needs to change, but I think that could be separate from other module-info improvements.) https://github.com/OpenAPITools/jackson-databind-nullable/pull/62

Major

1. Stop extending jackson-base and use jackson-bom dependency management instead. jackson-base is only meant for projects owned by the Jackson team. This could be done as a minor, but there's a few different parts that could be seen as breaking so major is safer. https://github.com/OpenAPITools/jackson-databind-nullable/pull/98
2. Jackson 3 compat. Unsure if there's a trivial way to support Jackson 2 and 3 at the same time, probably not. Would need either 2 concurrent versions in this repo, or just move on to Jackson 3. Given the infrequency of updates in this repo as-is, moving on to Jackson 3 may not be too problematic. https://github.com/OpenAPITools/jackson-databind-nullable/pull/73
3. Review the requirement for a serialization inclusion of NON_NULL. Requiring users to configure this can be confusing. It would be better to automatically do this for properties that are JsonNullable. Unsure if this is possible. https://github.com/OpenAPITools/jackson-databind-nullable/issues/55
4. Review and possibly change the behavior for deserializing empty strings. It's a bit odd that empty strings are treated as undefined when an empty string is a completely valid value. https://github.com/OpenAPITools/jackson-databind-nullable/issues/46 https://github.com/OpenAPITools/jackson-databind-nullable/issues/26

Start by reviewing the remaining unchecked items in the issue and their linked issues or pull requests. The payload does not identify specific files, tests, or a single entry point; completion would require selecting a focused change, defining its scope, and verifying the associated compatibility or behavior requirements.