chore(deps): Bump bytebuddy-version from 1.18.10 to 1.18.11#24401
Conversation
Bumps `bytebuddy-version` from 1.18.10 to 1.18.11. Updates `net.bytebuddy:byte-buddy` from 1.18.10 to 1.18.11 - [Release notes](https://github.com/raphw/byte-buddy/releases) - [Changelog](https://github.com/raphw/byte-buddy/blob/master/release-notes.md) - [Commits](raphw/byte-buddy@byte-buddy-1.18.10...byte-buddy-1.18.11) Updates `net.bytebuddy:byte-buddy-agent` from 1.18.10 to 1.18.11 - [Release notes](https://github.com/raphw/byte-buddy/releases) - [Changelog](https://github.com/raphw/byte-buddy/blob/master/release-notes.md) - [Commits](raphw/byte-buddy@byte-buddy-1.18.10...byte-buddy-1.18.11) --- updated-dependencies: - dependency-name: net.bytebuddy:byte-buddy dependency-version: 1.18.11 dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: net.bytebuddy:byte-buddy-agent dependency-version: 1.18.11 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
oscerd
left a comment
There was a problem hiding this comment.
Version-only patch bump of bytebuddy-version 1.18.10 → 1.18.11, confined to the single property in parent/pom.xml. Byte Buddy patch increment, low risk. dependency-review and upload are green; the two JDK build jobs were still running at approval time — this approval doesn't bypass the required build checks, so let them go green before merge. LGTM.
Reviewed with Claude Code on behalf of Andrea Cosentino (@oscerd). This review was generated by an AI agent and may contain inaccuracies; please verify all suggestions before applying.
|
🧪 CI tested the following changed modules:
🔬 Scalpel shadow comparison — Scalpel: 476 tested, 0 compile-only — current: 0 all testedMaveniverse Scalpel detected 476 affected modules (current approach: 0).
|
Bumps
bytebuddy-versionfrom 1.18.10 to 1.18.11.Updates
net.bytebuddy:byte-buddyfrom 1.18.10 to 1.18.11Release notes
Sourced from net.bytebuddy:byte-buddy's releases.
Changelog
Sourced from net.bytebuddy:byte-buddy's changelog.
Commits
88dd0a3[publish] Releasing Byte Buddy 1.18.1146fcade[release] Release new version6a68de6Prevent path traversal from crafted type names when writing class files to fo...9ba4ab6Pin ClusterFuzzLite base image and actions by hash.dd4f81eAdd SBOM to build.7dd9a0dUpdate internal Byte Buddy and release notesd6b3e15[publish] Start next development iteration 1.18.11-SNAPSHOTUpdates
net.bytebuddy:byte-buddy-agentfrom 1.18.10 to 1.18.11Release notes
Sourced from net.bytebuddy:byte-buddy-agent's releases.
Changelog
Sourced from net.bytebuddy:byte-buddy-agent's changelog.
Commits
88dd0a3[publish] Releasing Byte Buddy 1.18.1146fcade[release] Release new version6a68de6Prevent path traversal from crafted type names when writing class files to fo...9ba4ab6Pin ClusterFuzzLite base image and actions by hash.dd4f81eAdd SBOM to build.7dd9a0dUpdate internal Byte Buddy and release notesd6b3e15[publish] Start next development iteration 1.18.11-SNAPSHOTDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)