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 io.projectreactor:reactor-bom from 2023.0.1 to 2023.0.2 #14430

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 10, 2024

Bumps io.projectreactor:reactor-bom from 2023.0.1 to 2023.0.2.

Release notes

Sourced from io.projectreactor:reactor-bom's releases.

2023.0.2

2023.0.2 release train is made of:

reactor-core 3.6.2 reactor-netty 1.1.15 reactor-pool 1.0.5

These artifacts didn't have any changes:

reactor-kafka 1.3.22 reactor-addons 3.5.1 reactor-kotlin-extensions 1.2.2

Commits
  • bf85fe3 [release] Prepare and release BOM 2023.0.2
  • 9d26929 Merge-ignore 2022.0.15 into 2023.0.2
  • ed957af [release] Back to snapshots, next BOM will be SR 16
  • 2b73b88 [release] Prepare and release BOM 2022.0.15
  • 2f8cb9a Merge-ignore 2020.0.40 into 2023.0.2
  • cd75fb5 Merge-ignore 2020.0.40 into 2022.0.15
  • 25faabe [release] Back to snapshots, next BOM will be SR 41
  • 615229a [release] Prepare and release BOM 2020.0.40
  • 2cf9ded [release] Back to snapshots, next BOM will be SR 2
  • See full diff in compare view

Dependabot compatibility score

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 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)

Bumps [io.projectreactor:reactor-bom](https://github.com/reactor/reactor) from 2023.0.1 to 2023.0.2.
- [Release notes](https://github.com/reactor/reactor/releases)
- [Commits](reactor/reactor@2023.0.1...2023.0.2)

---
updated-dependencies:
- dependency-name: io.projectreactor:reactor-bom
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the type: dependency-upgrade A dependency upgrade label Jan 10, 2024
@dependabot dependabot bot added this to the 6.2.x milestone Jan 10, 2024
@sjohnr sjohnr merged commit 7065f38 into 6.2.x Jan 12, 2024
2 checks passed
@sjohnr sjohnr self-assigned this Jan 12, 2024
@dependabot dependabot bot deleted the dependabot/gradle/6.2.x/io.projectreactor-reactor-bom-2023.0.2 branch January 12, 2024 15:48
@sjohnr sjohnr modified the milestones: 6.2.x, 6.2.2 Jan 12, 2024
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.

1 participant