Bump byte-buddy.version from 1.18.8-jdk5 to 1.18.14-jdk5

[dependabot]

Bumps byte-buddy.version from 1.18.8-jdk5 to 1.18.14-jdk5.
Updates net.bytebuddy:byte-buddy from 1.18.8-jdk5 to 1.18.14-jdk5

Release notes

Sourced from net.bytebuddy:byte-buddy's releases.

Byte Buddy 1.18.14

• Avoid exposure of the agent argument on the command line of the process that is spawned for an external attachment.
• Avoid the resolution of symbolic links when the Gradle plugin deletes a folder recursively.
• Limit the nesting depth that is accepted when parsing a generic type signature to avoid an exhaustion of the stack for a malformed class file.
• Sign all deployed files using sigstore, in addition to the existing GPG signature.
• Validate entry names when the Android plugin retains a file to avoid the propagation of path traversals.

Byte Buddy 1.18.13

• Actually include the SBOM within the published artifacts.
• Avoid propagation of path traversals that are contained in jar files which are copied without transformation.
• Avoid repeated traversal of previously visited type hierarchies to improve performance.
• Correct Kotlin support of the Gradle plugin to redirect the classes directory of a source set while retaining support for legacy Gradle versions.
• Create Gradle tasks using Gradle's task registration API if available.

Byte Buddy 1.18.12

• Automatically support Kotlin in Gradle plugin.
• Add support for native attach on Windows for ARM64.
• Correct JNA injector which accidentally created on based on Unsafe.

Byte Buddy 1.18.11

• Add SBOM to published artifacts.
• Check for traversable paths injected into class files as a rather hypothetical attack vector.

Byte Buddy 1.18.10

• Delay change of default for unsage use to Java 26 and improve error message.

Byte Buddy 1.18.9

• Disable use of Unsafe by default when Java 25or newer is discovered.
• Check for escape when creating folders in Plugin.Engine.
• Improve OpenJ9 attachment.
• Avoid null pointer on missing annotation types.
• Improve diagnostics for external agent attachment.
• Improve on Gradle context discovery.
• Support Android libraries on AGP9 or newer.
• Update ASM.

Commits

• See full diff in compare view

Updates net.bytebuddy:byte-buddy-agent from 1.18.8-jdk5 to 1.18.14-jdk5

Release notes

Sourced from net.bytebuddy:byte-buddy-agent's releases.

Byte Buddy 1.18.14

• Avoid exposure of the agent argument on the command line of the process that is spawned for an external attachment.
• Avoid the resolution of symbolic links when the Gradle plugin deletes a folder recursively.
• Limit the nesting depth that is accepted when parsing a generic type signature to avoid an exhaustion of the stack for a malformed class file.
• Sign all deployed files using sigstore, in addition to the existing GPG signature.
• Validate entry names when the Android plugin retains a file to avoid the propagation of path traversals.

Byte Buddy 1.18.13

• Actually include the SBOM within the published artifacts.
• Avoid propagation of path traversals that are contained in jar files which are copied without transformation.
• Avoid repeated traversal of previously visited type hierarchies to improve performance.
• Correct Kotlin support of the Gradle plugin to redirect the classes directory of a source set while retaining support for legacy Gradle versions.
• Create Gradle tasks using Gradle's task registration API if available.

Byte Buddy 1.18.12

• Automatically support Kotlin in Gradle plugin.
• Add support for native attach on Windows for ARM64.
• Correct JNA injector which accidentally created on based on Unsafe.

Byte Buddy 1.18.11

• Add SBOM to published artifacts.
• Check for traversable paths injected into class files as a rather hypothetical attack vector.

Byte Buddy 1.18.10

• Delay change of default for unsage use to Java 26 and improve error message.

Byte Buddy 1.18.9

• Disable use of Unsafe by default when Java 25or newer is discovered.
• Check for escape when creating folders in Plugin.Engine.
• Improve OpenJ9 attachment.
• Avoid null pointer on missing annotation types.
• Improve diagnostics for external agent attachment.
• Improve on Gradle context discovery.
• Support Android libraries on AGP9 or newer.
• Update ASM.

Commits

• See full diff 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)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 026a06ee-a3ab-4d77-868b-c0c08174a25c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.