Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump net.bytebuddy:byte-buddy from 1.14.14 to 1.14.15 #414

Merged
merged 1 commit into from
May 8, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 8, 2024

Bumps net.bytebuddy:byte-buddy from 1.14.14 to 1.14.15.

Changelog

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

Byte Buddy release notes

Commits
  • a24599a [maven-release-plugin] prepare release byte-buddy-1.14.15
  • 0e0cbdf [release] Release new version
  • 5b5bcaf Minor code normalizations.
  • 1897879 Add missing forwarding.
  • 156ba85 J9 Allow attachment as root (#1631)
  • 01ed75b Switch from global property to explicit argument.
  • f04d254 Add property to allow disabling user check for J9 which does not seem to be i...
  • 5b7c966 Update internal Byte Buddy.
  • e258ec5 Update checkout plugin.
  • 61209f4 [maven-release-plugin] prepare for next development iteration
  • See full diff in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

@dependabot dependabot bot added the type/dependency-upgrade A dependency upgrade label May 8, 2024
@pderop
Copy link
Contributor

pderop commented May 8, 2024

@dependabot rebase

Bumps [net.bytebuddy:byte-buddy](https://github.com/raphw/byte-buddy) from 1.14.14 to 1.14.15.
- [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.14.14...byte-buddy-1.14.15)

---
updated-dependencies:
- dependency-name: net.bytebuddy:byte-buddy
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/gradle/net.bytebuddy-byte-buddy-1.14.15 branch from 92d9f51 to 81741a7 Compare May 8, 2024 08:51
@pderop pderop assigned pderop and unassigned simonbasle May 8, 2024
@pderop pderop added this to the 1.0.10.RELEASE milestone May 8, 2024
@pderop pderop merged commit 707f44e into master May 8, 2024
2 checks passed
@dependabot dependabot bot deleted the dependabot/gradle/net.bytebuddy-byte-buddy-1.14.15 branch May 8, 2024 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/dependency-upgrade A dependency upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants