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

Upgrade to Spring Boot 3.1.0 #3996

Merged

Conversation

JohnNiang
Copy link
Member

What type of PR is this?

/kind cleanup
/area core
/milestone 2.6.x

What this PR does / why we need it:

Upgrade to Spring Boot 3.1.0, please refer to https://github.com/spring-projects/spring-boot/releases/tag/v3.1.0.

Does this PR introduce a user-facing change?

升级 Spring Boot 至 3.1.0

@f2c-ci-robot f2c-ci-robot bot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label May 25, 2023
@f2c-ci-robot f2c-ci-robot bot added this to the 2.6.x milestone May 25, 2023
@f2c-ci-robot f2c-ci-robot bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/core Issues or PRs related to the Halo Core labels May 25, 2023
@f2c-ci-robot f2c-ci-robot bot requested review from lan-yonghui and LIlGG May 25, 2023 12:10
@codecov
Copy link

codecov bot commented May 25, 2023

Codecov Report

Merging #3996 (46abe63) into main (a6c923d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #3996   +/-   ##
=========================================
  Coverage     60.62%   60.62%           
  Complexity     2348     2348           
=========================================
  Files           355      355           
  Lines         12099    12099           
  Branches        873      873           
=========================================
  Hits           7335     7335           
  Misses         4331     4331           
  Partials        433      433           

Copy link
Member

@ruibaby ruibaby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@f2c-ci-robot f2c-ci-robot bot added the lgtm Indicates that a PR is ready to be merged. label May 25, 2023
@f2c-ci-robot
Copy link

f2c-ci-robot bot commented May 25, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ruibaby

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@f2c-ci-robot f2c-ci-robot bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 25, 2023
@f2c-ci-robot f2c-ci-robot bot merged commit 4abe16f into halo-dev:main May 25, 2023
4 checks passed
@ruibaby ruibaby modified the milestones: 2.6.x, 2.6.0 May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/core Issues or PRs related to the Halo Core kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants