[dependabot]

Bumps com.github.therapi:therapi-runtime-javadoc from 0.15.0 to 0.16.0.

Release notes

Sourced from com.github.therapi:therapi-runtime-javadoc's releases.

0.16.0

✨ #83 The annotation processor is now declared as "isolating", so Gradle can process annotations incrementally instead of recompiling everything.

🐛 #73 An empty {@link} tag, like in @return {@link }, no longer causes a NullPointerException.

🐛 #75 Block tags aligned by a code formatter, like @param name description, are now parsed correctly. Previously, such @param tags lost their names (so all but one were discarded), and @see tags with a string or HTML link were ignored.

🐛 #79 Formatting a comment with an empty {@code} or {@literal} tag no longer throws NullPointerException. This also affected Comment.toString(). Other tags without content, like {@inheritDoc}, are no longer rendered as {@inheritDoc null}.

🐛 {@link} and {@value} tags with whitespace before the closing brace, like {@link Foo }, are no longer silently dropped.

🔥 The annotation processor JAR no longer bundles a repackaged copy of JavaPoet. The runtime library now includes minimal-json as source code instead of a repackaged JAR. Its package name is unchanged, so the annotation processor and runtime library from different versions still work together.

Breaking changes

⚠️ #79 InlineTag.getValue() now returns an empty string instead of null when the tag has no content, and the InlineTag constructor throws NullPointerException if the tag name is null.

Build changes

🔧 The project is now built with Maven instead of Gradle. The published POMs are self-contained, without a parent POM. The annotation processor's POM now declares its dependency on the runtime library with compile scope instead of runtime scope.

Changelog

Sourced from com.github.therapi:therapi-runtime-javadoc's changelog.

0.16.0 - October 27, 2026

✨ #83 The annotation processor is now declared as "isolating", so Gradle can process annotations incrementally instead of recompiling everything.

🐛 #73 An empty {@link} tag, like in @return {@link }, no longer causes a NullPointerException.

🐛 #75 Block tags aligned by a code formatter, like @param name description, are now parsed correctly. Previously, such @param tags lost their names (so all but one were discarded), and @see tags with a string or HTML link were ignored.

🐛 #79 Formatting a comment with an empty {@code} or {@literal} tag no longer throws NullPointerException. This also affected Comment.toString(). Other tags without content, like {@inheritDoc}, are no longer rendered as {@inheritDoc null}.

🐛 {@link} and {@value} tags with whitespace before the closing brace, like {@link Foo }, are no longer silently dropped.

🔥 The annotation processor JAR no longer bundles a repackaged copy of JavaPoet. The runtime library now includes minimal-json as source code instead of a repackaged JAR. Its package name is unchanged, so the annotation processor and runtime library from different versions still work together.

Breaking changes

⚠️ #79 InlineTag.getValue() now returns an empty string instead of null when the tag has no content, and the InlineTag constructor throws NullPointerException if the tag name is null.

Build changes

🔧 The project is now built with Maven instead of Gradle. The published POMs are self-contained, without a parent POM. The annotation processor's POM now declares its dependency on the runtime library with compile scope instead of runtime scope.

Commits

• ac7499c Prepare 0.16.0 release
• ccfa79e Fix parsing of block tags aligned by a code formatter
• 9e31e56 Fix NullPointerException when formatting empty inline tags
• b24b64a Upgrade tests to JUnit 5 and compile-testing 0.24.0
• 9df0c72 Snazzy Maven Central batch was pointing to wrong repo
• 7913073 Clean up gradle build scripts stragglers
• 6fe9c64 Fix regression in 93fa733c:
• 93fa733 Only run record tests on platforms that support records
• e59d087 Build with Maven instead of Gradle
• 3f71f56 Add fancy maven central version tag
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)